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

Targets - last element not checked? #125

Closed
replay111 opened this issue Dec 6, 2024 · 2 comments
Closed

Targets - last element not checked? #125

replay111 opened this issue Dec 6, 2024 · 2 comments

Comments

@replay111
Copy link

Hi - I have configuration similar to this:

targets:
  - 10.0.0.1
  - 10.0.0.2
  - 10.0.0.3

I was playing with grafana and alerts and I have noticed that if I block last adres (10.0.0.3 in this case) - from docker container pings are blocked, but ping_exporter shows ping_loss_ratio as 0 (zero), so according to ping_exporter IP address is available.

But when I add some additional addres like this:

targets:
  - 10.0.0.1
  - 10.0.0.2
  - 10.0.0.3
  - 10.0.0.4

ping_exporter now works fine with .3 address but is totally ignoring .4 address...

Does anyone have/had some similar behavior?
I am using:
VERSION="1.1.3"
PLATFORM="linux"
ARCH="amd64"

@gogglespisano
Copy link

Do you have a newline after the last entry? Maybe it's ignored if a newline is missing.

@replay111
Copy link
Author

I will close this one - as I suspect that my firewall was tricking me. I think the connection estabilished and another rule was allowing for passing. I will take a closer look on that, as I am not sure if this is a problem of ping_exporter or my lack of knowledge with firewalls ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants