Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[[inputs.ping]] when a URL does not exists #6808

Closed
mertbakir opened this issue Dec 17, 2019 · 2 comments
Closed

[[inputs.ping]] when a URL does not exists #6808

mertbakir opened this issue Dec 17, 2019 · 2 comments
Labels
area/ping bug unexpected problem or unintended behavior

Comments

@mertbakir
Copy link

Telegraf. 1.13.0

[[inputs.ping]]
  urls = ["server1", "server2", "server3", "server4", "server5"]

When server3 is not a resolved, ping will return "could not find host server3" and in this case inputs.ping doesn't look for server4 and server5. Telegraf keeps working and generating related values for server1 and server2.

I'm not sure if this is a bug but I expect it to log the error about server 3 and move on with server4.

@mertbakir mertbakir changed the title When a URL is does not exists [[inputs.ping]] when a URL does not exists Dec 17, 2019
@danielnelson
Copy link
Contributor

This sounds a lot like #6690, but this should be fixed in 1.13.0.

I am testing with this configuration, and the non-localhost server is not up:

[[inputs.ping]]
   urls = ["localhost", "localhost", "debian-stretch-docker.virt", "localhost", "localhost", "localhost", "localhost"]
2019-12-17T05:19:35Z E! [inputs.ping] Error in plugin: lookup debian-stretch-docker.virt on 127.0.0.1:53: no such host
> ping,url=debian-stretch-docker.virt result_code=1i 1576559975000000000
> ping,url=localhost average_response_ms=0.028,maximum_response_ms=0.028,minimum_response_ms=0.028,packets_received=1i,packets_transmitted=1i,percent_packet_loss=0,result_code=0i,standard_deviation_ms=0,ttl=64i 1576559975000000000
> ping,url=localhost average_response_ms=0.022,maximum_response_ms=0.022,minimum_response_ms=0.022,packets_received=1i,packets_transmitted=1i,percent_packet_loss=0,result_code=0i,standard_deviation_ms=0,ttl=64i 1576559975000000000
> ping,url=localhost average_response_ms=0.021,maximum_response_ms=0.021,minimum_response_ms=0.021,packets_received=1i,packets_transmitted=1i,percent_packet_loss=0,result_code=0i,standard_deviation_ms=0,ttl=64i 1576559975000000000
> ping,url=localhost average_response_ms=0.019,maximum_response_ms=0.019,minimum_response_ms=0.019,packets_received=1i,packets_transmitted=1i,percent_packet_loss=0,result_code=0i,standard_deviation_ms=0,ttl=64i 1576559975000000000
> ping,url=localhost average_response_ms=0.02,maximum_response_ms=0.02,minimum_response_ms=0.02,packets_received=1i,packets_transmitted=1i,percent_packet_loss=0,result_code=0i,standard_deviation_ms=0,ttl=64i 1576559975000000000
> ping,url=localhost average_response_ms=0.016,maximum_response_ms=0.016,minimum_response_ms=0.016,packets_received=1i,packets_transmitted=1i,percent_packet_loss=0,result_code=0i,standard_deviation_ms=0,ttl=64i 1576559975000000000

@danielnelson danielnelson added the bug unexpected problem or unintended behavior label Dec 17, 2019
@sspaink
Copy link
Contributor

sspaink commented Jan 20, 2022

Closing because it seems this was resolved in an older version of Telegraf, please re-open if your still experiencing this issue.

@sspaink sspaink closed this as completed Jan 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ping bug unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

4 participants