7 years ago
Ad-hoc script running
Often when an alert pops up, I find myself running some very common troubleshooting/helpful tools to quickly gather more info. It would be nice to get that info quickly and easily without having t...
In my opinion, an Ops Note (set specifically for that device) or a Note on the alert itself would be great. One thing I do like about the Ops note is that it becomes visible on all of the graphs for the device which should coincide with the alert trigger time. The one thing I like about putting a note on the alert is it would capture at the time the alert is generated and in the context of that alert.
I don't really like the idea of creating a separate data/config/properysource for this - if you're datasource has to be configured separately (ie for thresholds) from the one generating the alert then you're not capturing the point in time when the alert or alerting condition was triggered. How do you handle custom thresholds? Would you be putting in an Ops Note in for as long as the condition exists as often as the datasource runs?
There are ways to accomplish this in a customized way, but it would be so much more easy and helpful if LogicMonitor could automatically trigger a "post alert action" or something. There could be 'canned' actions (like get processes/users/memory for high cpu alerts) and ones that are customized via groovy/powershell integrations.
Just my 2¢