On Mon, 13 Jan 2014, Kelvin Ku wrote:
You can eliminate a lot of active checks if you watch the logs for normal
activity (you can even setup your alerts so instead of just calling a
person, it first does a monitoring probe in case the traffic had just
dropped off)
One thing to remember, your load balancer's test is not testing to see if
the product works, just that the webserver works. you need other tests to
make sure that all the web hits you are getting aren't just generating a
'database error, try again later' response ;-)
David Lang
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
What does everyone here use for (host) hardware monitoring? At $work we use
a combination of host-side scripts that periodically run and parse the
output of vendor-specific binaries and send alerts to our monitoring
servers and we also run the vendor hardware agents which send snmp traps.
There are shortcomings in both approaches and I'm currently splitting my
time trying to improve both of them.
I like to run the scripts on the server and have them write to the logs, then
have the monitoring done on a central log box.
I much prefer push monitoring to having one box doing polling, and having these
data points archived (especially if they are utilization numbers, not just
up/down booleans) can be very useful.
David Lang
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
