"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?Solved200Views6likes2Comments
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.Solved122Views18likes3CommentsProgrammatic Ping Alert
We currently lack the ability to white list domain names on our firewall, so I have to do everything via IP. Recently I’ve come across an issue where a company won’t give me their external IP’s because they can change, or so they say. For several weeks I’ve pinged the IP’s and it has always been 1 of 4 IPs. Has anyone created some kind of ping alert that does something like “ping easypost.com and api.easypost.com if the IP’s returned are not in 169.62.110.130-169.62.110.133, alert me” I’m not much of a programmer myself so I’d need something pretty “plug and play”. TIA!Solved99Views7likes4CommentsPing only devices
We are a network MSP. We have several customers with a large number of ping only devices. LMs terms don't charge per device for ping only. However, there's a caveat to that. The ping function for a device must be nested under another device such as a Collector. Apparently the billing system doesn't have the ability to distinguish between an SNMP/WMI device and a ping only device. The problem with nesting under another device is that ping device is hidden several layers down making it difficult for a customer to find them. These ping only devices don't work well with the NOC widget. I wound up having to create a second NOC widget for just ping only devices to get visibility. What I'm proposing is the LM modify their billing device detection such that Ping only devices are input just like any other device and that the billing system scans device to determine if it's Ping only or not54Views0likes3CommentsWidget for ping monitoring
Hi Everyone! I'm trying to figure out how to create a widget, that will show the top ten servers that have a ping of above 100ms. I can make the standard ping widget, but I don't see a way to limit the graph to those servers that have a high ping. Do I need to use the virtual datapoint? Or, maybe I need clarification on what it means when I select top 10 on an average, or maxrtt datapoint. Thanks!32Views1like6Comments
Custom Ping Intervals
Currently, LM has hard-coded the Ping dataSource to use 250ms ICMP Ping intervals. We need the flexibility to adjust the Ping interval (ms)in the DataSource (Either static or system property value). Background: We've seen at least one company "Mimosa" that has changed it's newest firmware to block ICMP messages if they are sent "too quickly". For Mimosa wireless gear, this is represented in LM as an 80% packetloss (2 pings permitted, 8 are then rejected). Mimosa does not want their hardware resources depleted by multiple, quick, Ping requests. The workaround currently is to alter the thresholds in LM to compensate for an 80% packetloss reading. By having the ability to adjust Ping Interval for these hosts in LM, we can have better visibility into network issues.19Views0likes4Comments
Web Service Ping and Trace Route
Wherethere isonly one checkpoint defined for a web service check, in particular for internal web service checks, please make it so that an overall failure alert also includes the ping and tracerouteinfo in the tooltip, see attached. Currently this tool tip info is only available for individual checkpointalerts. If there is only one checkpoint location, then the ping and traceroute infoshould be included in the overall alert too.This would be very useful in reducing alerts. At the moment where I have one checkpoint (because that is all that is needed) I have to generate two alerts for the same incident, one with the useful ping and traceroute and the overall one (which is redundant in a single checkpoint scenario).16Views0likes1CommentWidget that allows multiple customer services (ping)
Hi, I was wondering if a feature could be created that would allow me to monitor Response Time/Latency of multiple pingservices that I have set up. At this moment in time, I can monitor one customer per widget; I would like to monitor more customers on the same widget showing the same datapoints. For example, in the uploaded image, this is showing the response time of an IP address from all of the checkpoints (Washington, Dublin etc). I would like to monitor the response time of all the customers I have, rather than checking multiple widgets. At the moment, there is a widget called "Service Status" which lets you monitor the overall status of services. I would like the same thing to be done but only for the ping service; so that on one widget I can see the latency of each customers IP address from Dublin. (excluding the others - added ability of choosing which checkpoint to use) Hopethis makes sense; if not, I am an email away.4Views0likes0Comments