Forum Discussion
This is something that I miss from Solarwinds so I'd love to see this in LogicMonitor as well.
This would be extremely valuable! If a server is not able to be pinged for instance, if it could be set to suppress all other alerts for the device until it became accessible would greatly reduce alert spam. Serversalive and others as mentioned have this capability. Is their an official feature request form that can be submitted to from customers?
Thanks.
You have no idea how restrictive not having this feature is. How can someone hope to properly monitor their systems when the monitor has no proper hierarchical dependencies?
Also looking for this feature.
I would love to see this feature. As it is now one issue can create dozens of alerts and can make it difficult to troubleshoot.
This would be very welcome
- Annie_DunhamFormer Employee
I'm happy to say this is on our road map. I don't know much - in terms of how we'll configure it, the visuals, user experience, or timeline - but it will be one of the larger projects we focus on this year. Keep the requests coming - especially any specifics in terms of which problems a feature like this may solve!
Agree with Clement. Nmap can help but also checking for CDP neighbours on devices or just set from gui.
A device can also have multiple parents. aka a core switch connected to two firewalls. if one goes down monitoring should not but both down = all hosts below affected.
At a minimum make this feature as a manually configurable feature ASAP with a longer term goal of automating it!
Glad to hear this is on the road map! This is a really important feature for us as well. With the amount of objects we're monitoring it's important we know whether a network device at a location is down, or the gateway/MPLS to the entire location is down and at a glance that's not obvious. Cleaner alerting on this is very important to us.
Would love an update to see if this has moved any closer on the road map since last year.
- Annie_DunhamFormer Employee
There is definitely movement. We opted to solve the problem of drawing network and service maps first, as visualizing these relationships is step one. That is underway, and dependencies are slotted to follow.
Related Content
- 6 years ago
- 6 years ago