New UI Enhancements/ Feature Request
Being able to select several alerts at once and from the Actions menu have disable/enable alerting available, preferable as a cycle alerting option so that it disables and enables automatically, that we can allow anyone to perform. As we often set SDT and need to clear the alerts in CSM, in order to achieve this we select disable then enable on each alert individually when there is over 100 alerts this can be a pain.101Views5likes4CommentsFeature Request - New property to indicate monitoring is disabled
I have a problem where my users will disable alertingon a resource that has been removed from the environment instead of deleting it. Or they may disable alerting and forget to re-enable it. With alerting disabled, my no-data datapoint alerts never trigger. In the case of removed devices, the resources just hang out there forever andnever getremoved because theydon’t show up on my data collection failures dashboard. Devices for which the user intended to re-enable alerting eventually meet the same fate unless they go down and we don’t know about it. Either of these outcomes is bad news. It would be nice if there were a property which would indicate that alerting for aresource has been disabled. As far as I am aware, there is currently no way to do this. Then I couldcreate a dynamic group of devices which have monitoring disabled. As devices are populated in the group, I can investigate them. As it stands now, I have to go manually hunt them down.100Views20likes3CommentsNetflow Alerting Rules
Not only restricting you to visualising the Netflow data on LM Platform. Interestingly, the most recent improvement to LogicMonitor Netflow is the Traffic Alerting Rules. It is possible to set up traffic alert rules for the NetFlow resources to get alerts when a resource's traffic hits a specific threshold, drops off for a specified length of time, etc. Traffic Alerting Rules feature are available and you can create rules at: Traffic Alert Rule at Group Level Traffic Alert Rule at Resource Level Don't missout on the advantages of this feature and refer the below link for more details. https://www.logicmonitor.com/support/traffic-alert-rule99Views18likes0CommentsFeature Request - Alerting Protection Prompt
I would like to submit a recommendation for a feature request please. This would benefit a lot off users I believe. I work for a large managed service provider with many customers in LM. While checking my customers today I noticed the top level resource grouping for one of them had Alerting switched OFF. I asked an LM Admin to check who had set this and when to discover after further investigation an engineer had mistakenly clicked this 5 days ago. Given how easy this click to alter status and the potential impact it has is, I recommend if this is altered a pop-up prompt to confirm you are sure is flagged as well as potentially capturing a note as to a reason.55Views14likes5CommentsDEVIATION 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 sample19Views3likes1CommentCustom 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!17Views3likes1CommentThreshold Duration
Hello, I was wondering if there was a possibility to impose a duration constraint on a threshold in LogicMonitor... I see where you can enable dynamic alters but was not sure if they would look back to the duration of the alert rather than just a floating data point that it would attempt to normalize. Thanks in AdvanceSolved16Views0likes1CommentDisabled 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?10Views6likes1CommentComplex 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.7Views1like1Comment