You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that I already reported a similar issue a while ago - #3545 , which was resolved since.
Relevant telegraf.conf:
[[outputs.wavefront]]
host = "no-such-host"
port = 2878
# Do not convert underscores we have in metrics to dots
convert_paths = false
System info:
$ uname -a
Linux ip-10-0-164-199 3.13.0-149-generic #199-Ubuntu SMP Thu May 17 10:12:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ dpkg -l | grep telegraf
ii telegraf 1.6.2-1 amd64 Plugin-driven server agent for reporting metrics into InfluxDB.
Expected behavior:
$ sudo service telegraf start
Starting the process telegraf [ OK ]
telegraf process was started [ OK ]
should start the daemon which must be trying to connect to the wavefront forever
Actual behavior:
The /var/log/telegraf/telegraf.log shows:
2018-06-28T12:24:11Z E! Failed to connect to output wavefront, retrying in 15s, error was 'Wavefront: TCP address cannot be resolved lookup no-such-host on 10.0.0.2:53: no such host'
2018-06-28T12:24:26Z E! Wavefront: TCP address cannot be resolved lookup no-such-host on 10.0.0.2:53: no such host
and the process terminates
The text was updated successfully, but these errors were encountered:
I worry that retrying indefinitely without explicitly configuring telegraf to do so could create some false sense of it "just working." I think a connection retry config option would satisfy this, if set to <0, it would retry forever, otherwise it could retry for the x number of times. It would also be beneficial if this retry-er had a connection backoff that waited a bit longer each retry (to a point) so it doesn't end up spamming the connection/logs.
Note that I already reported a similar issue a while ago - #3545 , which was resolved since.
Relevant telegraf.conf:
System info:
Expected behavior:
should start the daemon which must be trying to connect to the wavefront forever
Actual behavior:
The
/var/log/telegraf/telegraf.log
shows:and the process terminates
The text was updated successfully, but these errors were encountered: