Feature request - Add suppression type to the alert list widget
I had a case with Logicmonitor support where I asked if it was possible to filter away alerts that fall under a cluster alert. Here I got the suggestion to use routing state but this does not give anyvalue on a cluster alert. The support engineer looked further into it. "I have tested this further and unfortunately using the routingstate filter is not going to work here as this relates to suppressed by Root Cause Analysis. I'm afraid I'm not seeing an alternative way to removed suppressed alerts from the alerts dashboard widget” So my suggestion is to add suppression type to the filter of the alert list widget.46Views19likes0CommentsAlert Thresholds - Changing units Free Space datapoint on Volume Capacity
Hi All, I wanted to put a question to you all to see if you have any recommendations. We have several drives that we are monitoring where it doesn’t make sense to track the % used datapoint due to the very large (or in a couple of cases, very small) total capacity of the drive. As such, we configured the Free Space datapoint for alerts instead. This is working well, however because the Free Space datapoint tracks “available storage capacity of the volume in bytes” it is difficult to quickly understand the potential impact of the alert when it triggers and error for < 268435456000 bytes remaining. Is there any way to change this datapoint so that it reports in a larger unit? GB would be preferred, but even MB would be helpful.Solved84Views8likes4CommentsDisable alert clear calls (but keep clear emails)
After receiving a call about an alert, and ack it, I do not need a call to tell me once it is resolved. This is particularly true when 20 things go down, I get 20 calls, I solve the issue and then I get 20 calls the issue is cleared. Please add the ability to disable cleared calls5Views0likes8CommentsAutomatic discovery of recipients/groups
We have begun implementing a tagging standard in our cloud accounts to better control discovered resources and route alerts accordingly. I would like to be able to route alerts by default based on the value of a tag. I'm aware that I can already set up specific users and then achieve exactly what I'm requesting, but I would much prefer to have a blanket rule that uses the tag's value as the recipient email address(es) directly. Some examples below: system.aws.tag.MonitorAlertEmail=ThisIsAnExample@PleaseOfferThisFeature.com system.aws.tag.SendAlertsHere=AnotherExcellentExample@WeWillPayExtraForThisFunctionality.gov AnotherEmailAddress@OkayNotReally.net See the screenshots below for a visual example of how I'd like to structure this automation.0Views0likes1Comment