Recent Discussions
Dependent Alert Mapping - reviewing cleared alerts
I recently had an LM support ticket open for some confusion we had around the Dependent Alert Mapping feature. Wanted to document some areas for improvement here that would make the feature work better. Currently, when an alert clears which was processed by Dependent Alert Mapping, the "Routing State" and "Dependency Role" columns set to blank. This makes it challenging to go back and review alerts after an outage to see what was "Originating" vs "Dependent" Please update the feature so that these columns on the alert table are still populated after an alert clears. This will help us with reviewing and reporting on resolved outages Currently when an alert is suppressed by dependent alert mapping, the alert message contains a lot of useful metadata related to the alert suppression. But if the originating alert clears and the dependent alert is still active, all of that metadata is removed and there is no indication that the alert was ever suppressed by the Dependent Alert Mapping feature This causes confusion when we go back to review past outages. It makes it look like the feature did not work as intended, even if it did. Fixing this along with item #1 would make the feature a lot easier for us to use and understand what it is doing.
Website Monitoring - Improvement Request
In Website monitoring, we are looking for A metric to configure threshold for response time and get alerted (Currently we just have graph for response time). To have historical data saved in LM portal for Total Download Time (Currently we can configure threshold, but unable to view historical data which could help us to determine the generic response time).Cisco Meraki License monitoring - Subscription - Licensing Model
One of our clients is using “Subscription Licensing” model since few months. But we do see Cisco Meraki License Module currently supports only per-device licensing. Hence, raising this Feature request for “Subscription Licensing” model. Meraki Licensing - Cisco Meraki DocumentationData Domain Path Redundancy Monitoring
We want to monitor Path Redundancy on Data Domains. Example for Hardware failure logs from DataDomain. WARNING HardwareFailure Enclosure=<> Path redundancy is lost. Enclosure 2 only has 1 active connection path and the required number is 2. Below seems related article. Data Domain: SAS or MPATH Alerts | Dell PhilippinesAllow websites to clear alerts immediately instead of showing the site as Down even though it's Up.
This has been a thorn in our sides for years and I didn't know why it was doing what it's doing. Then I found out it was designed this way and got the "Working as Designed" from support and told to submit a Feature Request into the black hole.... Reminder; Working As Designed is only a good excuse when the Design is Good. When the Design is Bad, as in this case, Working As Designed is a bad thing. With resources, I have two options for how alerts are handled: Alert Trigger Interval (number of failures before an alert is created) Alert Clear Interval (how many successes before the alert clears) For a website, I have the first option but not the second option. It uses the same setting for both, which is horrible. This means that websites will show as Down/Alert in LM for5-60 minutes After the site is back UP and running just fine. IMHO, this is just dumb. Why would I want a site to show down when it's not? Taken from this page (https://www.logicmonitor.com/support/services/about-services/services-alerts): For example: If you have configured the website to generate an alert after 7 consecutive failed checks, an alert is sent after (7-1) x 10= 60 minutes. So when the checks fail continuously for a minimum of 60 minutes, an alert is generated. Also, when the checks pass for a minimum of 60 minutes, the alert is cleared. Why on earth would anyone want their website to show DOWN for 60 MINUTES after you fixed the problem? If I get paged in the middle of the night to fix a website, I want it to show Up Instantly after I get it to start working again. I don't ever want it to show down for an hour. If I fix it and go back to bed, and then something happens 55 minutes later, I won't get a new alert, because it will still be under the original alert, and I won't know there's a New problem. I don't consider this a feature request. I consider this fixing something that was implemented with a flawed design. But here we are. I was hoping this would be one of those things that was changed in V4, but I don't see the option there either. This is just one of the many ways that Websites were implemented as an afterthought and missing some of the basic settings that resources have. Please fix this.
