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
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.
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 ;-)
Hi - I have configuration similar to this:
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:
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"
The text was updated successfully, but these errors were encountered: