LogicMonitor is, as far as I know, the most automated network monitoring system out there. But there is one area we don’t provide much in the way of automation, that we are often asked about – automated scripts in response to alerts. There are few reasons why not, which flow from our experience running critical production datacenters:
In all these cases, use your monitoring to tell you if your recovery mechanisms are working, not to be the recovery mechanisms. Monitor the memory usage of your mongrel processes, and alert only if the memory consumption is higher than you expect, for longer than it should be if monit was doing it’s job, say.
Of course, LogicMonitor can trigger automated script actions in response to alerts – you can set an agent inside your datacenter to pull all the alerts, send them to a script, which can do … whatever you can script. And there are cases where that’s appropriate. But you should have a good think about your architecture and design before you leap to that as a first resort.
Tags: best practices
We got a question internally about why one of our demo servers was slow, and how to use LogicMonitor to help identify the issue. The person asking comes from a VoIP, networking and Windows background, not Linux, so his questions reflect that of the less-experienced sys admin (in this case). I thought it interesting that he documented his thought processes, and I’ll intersperse my interpretation of the same data, and some thoughts on why LogicMonitor alerts as it does… Read more »
Not really monitoring, but I just finished giving a talk at the MySQL conference. (It was gratifyingly packed with people, too.)
Thought I’d post the slides here. The summary is:
Download the presentation here.
Feel free to post questions.
Performance monitoring for all your infrastructure & applications. In minutes, not hours.
Questions? Call Us!
(888) 415-6442 or +1 (805)-617-3884