Kapacitor service log provide little to no information on connection errors

I have two instances:
* One with Chronograf & Kapacitor
* One with InfluxDB

I have configured Kapacitor via Chronograf and from Chronograf's GUI, everything appears to be configured correctly. I can create rules for Kapacitor, even send test messages to Slack via webhook.

However despite this, Kapacitor itself can't connect to InfluxDB and therefore isn't alerting.

The underlying issue could be caused by a myriad of things, however I would expect the Kapacitor log to display some kind of information regarding connections, at least in debug mode. From what I'm seeing, it does not.

With debug mode enabled, all that appears in the Kapacitor logs is this - https://gist.github.com/egee-irl/385760d1815389e6fe7788cbcf7e3ba6 - which is pretty useless when trying to debug a networking issue.

Start by reviewing the Kapacitor logs produced with debug mode enabled and compare them with the connection failure described in the issue and linked gist. Identify where connection errors are currently reported; done means the logs provide useful information for diagnosing why Kapacitor cannot connect to InfluxDB.

Written by the indexing model from the issue text.