Disabled Alerts Notes
When there is a legitimate reason for disabling alerts for a device, it would be very useful to be able to leave a note as towhy(and by whom). This would prevent confusion with teams, where the case of "why would this be disabled" would come up frequently. For example, there is a known bug with a certain version combination of ESXi and HPE servers that triggers a false-positive hardware alert internally, so we disable alerts for that instance on servers that meet the criteria as we encounter them. Or, some QNAPs will give false-positive alerts that their disk is full when in fact it is "full" due to a RAIN configured as a LUN (we thus rely on the server alerting when the iSCSI volume is actuallyfull).However, another technician may log in and flip alerting for these instancesback on, assuming it was a mistake or something, and then we would get flooded with these false-positive alerts, prompting technicians to look into them; as you can see, this causes a loop of wasted time. Simply putting a note associated with the "Alerting Off / On" switch and tagging it with the user invoking it would easily solve issues like this. Something like what is shown for Acknowledgements would be adequate. Perhaps even an admin option torequirea note or not?11Views6likes1Comment
Cluster Alert Routing
It would be immensely helpful if I could see and test alert routing from the Cluster Alerts page at the device group level similar to the existingAlert Routing button on the Alert Tuning tab. As we begin to more heavily utilize this functionality, it's critical that we can verify that alerts are routed correctly wherever we set it up.4Views1like0CommentsComplex Datapoints between Datasources
It would be great to create alerts from multiple data-points from multiple data-sources. For example if CPU is above 30% and SQL database lock timeouts is above 1000. I can see many uses cases to be able to alert on different datapoints that relate to other datapoints in other data-sources.8Views1like1CommentDEVIATION FROM ROLLING AVERAGE
I see a need in the design to alert on deviation from rolling average: example 1: Temperature in hardware is based on fixed baseline (default or manual adjusted) or based on fixed Delta. In real world application it would Make a LOT more sense to alert on Deviation from a 5 day or 30 day rolling average Temp of the box. Reason is, units alarm on the weekends because the office shuts off the AC during the summer. or they alert During the week 9-5 because in the winter the offices crank the heat. All of these ignore nuance of RANGE and Average expectation for the location...The alerting should just be how FAR outside the average Range for the site is. My Nashville facility hovers from 56 to 59 all week. I have it set on 57 so I get alerts at least once a weekend. I could move it to 59...but that's a band-aid. The REAL solution would be to have the software TRACK the last 30 days, and alert when we're outside the NORM for that location. furthermore....with hardware it is not the specific temps that kill the hardware....its the RATE at which the temp changes. so, the alerts SHOULD be based on the average range the system has seen in the last 30 days, and alert ONLY when the rate of change accelerates...but I imagine THAT request would be more challenging to reduce to an algorithm. Example 2: PING times.....I have sites where the Latency range is EXTREME (Mumbai, Johannesburg, Taipei etc...) I'd wished the PING would track the 30 day range and common deviation from norm and alert when the sites see latency that is way outside the expected fluctuation range. 30ms typical 90% of the time + 200-500ms spikes 10% of the time. when Ping times hit 300 ms for more then 10% of the last hour of sampling....then notify warning to inform of change in TREND....not fixed threshold in immediate sample20Views3likes1Comment
Custom Alerts for ConfigSources
Hey LM team, There are a number of options to customize what is in a service alert as well as a data source alert, but config source? Nope, can't modify what gets sent. All it says is thata change was made and gives you a link to the device. A couple things I think would be beneficial as a new feature, 1. Being able to put what lines were added or removed right in the alert. For simple configs you can then tell right away if you need to take action or not. 2. Have the link in the alert actually bring you to the diff view of the current and last config state. While having to click through the multiple links and then slide the diff view slider is fairly painless, at 3am on my phone it can add to the sleepy frustration level. Basically just bringing some of the flexibility that alert templates have for data sources and services to the config sources. Thanks!18Views3likes1Comment
Enable/disable alerting without Manage rights
We think there needs to be another level of privileges between Acknowledge and Manage. We would like to be able to give our operators the ability to toggle the Alerting On/Off slider option without giving them Manage rights. Also, we'd like to give them the ability to perform Poll Now without giving them Manage rights.0Views0likes0CommentsAbility to customize web service alert emails
With DataSources and EventSources it is possible to tailor the alert message and content of the alert emails. However, with web services there is only the one template. We need to be able to tailor the email content on a web service by web service basis. Please make it possible to configure the alert email content per service check. Ideally it should be possible to define as many message templates as we like, and then choose which template to apply at a service group level, so that the service check objects inherit the template from the parent service group.4Views0likes2CommentsAlert escalation and acknowledgement combined
We completed a new integration and after a lot of effort we discovered that the escalation "NEXT" performed the create but subsequently every n minutes a new ticket was created - the ACK also still needs to be performed. Ideally, we would want the escalation to create the ticket and acknowledge the alert. Perhaps the escalation then has a null destination until it clears (active alert) or some other method to avoid repetitive case creation? I had a thread with Desh on support - no suggestions on a workaround.5Views0likes1Comment
Services - Make ##SERVICERESPONSE## available to Overall alerts
I would love it if we could reference ##SERVICESRESPONSE## on an overall alert. We don't deliver alerts for singular test location failures, since our mandate to only notify on systemic issues across all test locations. So the question will probably, which response to include in the event there are differing responses? Why not include all of them! Or only include the first one in the test location array for that service. Or pick a random one. Or arbitrarily decide certain failure reasons have a "higher" priority than others and choose the "highest" one.1View2likes3Comments
