How does Host Status idleInterval treat Ping Multi instances
@LogicMonitor Team: By reverse engineering I discovered the following behavior: If a Ping Multi instance ip address is also listed in the device property system.ips, the ICMP replies are also considered for Host Status idleInterval If a Ping Multi instance ip address is not listed in the device property system.ips, the ICMP replies are not considered for Host Status idleInterval It basically means that the Host Status may show a host unreachable even if a Ping Multi instance is still responding. This behavior was also confirmed by a support engineer (by reverse engineering). Can you confirm this observed behavior? Please update the online documentationaccordingly, since it already contains a note for scripted DataSources, but not for Ping Multi.Solved182Views18likes3Comments
"Virtual" device monitoring
I am preparing a set of datasources to monitor several aspects of a cloud provided service. I can connect to that service using an URL and specific port, but cannot ping this service as it is blocked. When defining a new device for this, I assigned the “NoPing”, “NoHTTP”, “NoHTTPs” system categories but I still get the dead device icon. My datasources alerts are notgenerated because of this dead status. It looks like the device address is checked using ping anyway and is marked as dead. Is there anyway to avoid this behaviour?Solved242Views6likes2Comments