The Virtues of Monitoring
paperplanes.de
The Virtues of Monitoring
1–7 of 7 posts
Re: The Virtues of Monitoring
#2Monitoring is one of the most important thing.
Rule of thumb: Think of everything you wish you had monitored after a crisis has happened (which might be "everything").
Re: The Virtues of Monitoring
#3Monitoring is one of the most important thing. Rule of thumb: Think of everything you wish you had monitored after a crisis has happened (which might be "everything").
the problem is you will probably think of monitoring the stuff that you wished you had monitored only _after_ the crisis happened, people are built in a way that makes it hard for us to think of what may go wrong.
So another simple rule I learned with time is to trust/understand the defaults,plugins,knobs,metrics that come with well known monitoring systems ("why the hell should I monitor _that_?"). This way you use the experience of other people as a backup for your own.
Re: The Virtues of Monitoring
#4This is a really good introduction to the different levels of infrastructure monitoring and their various pros/cons.
http://librato.com (full disclosure: I hack there) is a startup with a new kind of entry in the process-level monitoring/management space. Would love any feedback the infrastructure-minded part of the community here might have.
Re: The Virtues of Monitoring
#5This is great! Very clear explanation. Have you looked at AppFirst's (http://appfirst.com) solution? (fyi. I work there)
We have a monitoring solution that covers the application, process, and server level as well as integrating with nagios to cover any other level you have scripts for. It would be great to hear what you have to say about us!
Re: The Virtues of Monitoring
#6Monitoring is one of the most important thing. Rule of thumb: Think of everything you wish you had monitored after a crisis has happened (which might be "everything").
the problem is you will probably think of monitoring the stuff that you wished you had monitored only _after_ the crisis happened, people are built in a way that makes it hard for us to think of what may go wrong. So another simple rule I learned with time is to trust/understand the defaults,plugins,knobs,metrics that come with well known monitoring systems ("why the hell should I monitor _that_?"). This way you use…
What I have learned: Take Munin (or your solution of choice) and install all plugins for infrastructure to use. It's hard to monitor too much, only too little.
Re: The Virtues of Monitoring
#7Monitoring is one of the most important thing. Rule of thumb: Think of everything you wish you had monitored after a crisis has happened (which might be "everything").
the problem is you will probably think of monitoring the stuff that you wished you had monitored only _after_ the crisis happened, people are built in a way that makes it hard for us to think of what may go wrong. So another simple rule I learned with time is to trust/understand the defaults,plugins,knobs,metrics that come with well known monitoring systems ("why the hell should I monitor _that_?"). This way you use…
How about starting with the application/business metrics first (as those are presumably easier to articulate). As things fail over time move down the stack (infra/system) to get earlier warnings?