Best way to manage host-specific thresholds?
Cipriani, Robert C
Robert.Cipriani at mybrighthouse.com
Thu Dec 20 15:34:21 CET 2007
Group,
I am trying to wrap my head around the best way to manage things like ping RTA/packet loss, partition free space warn/critical, cpu/memory use, etc. I can set these up using custom object variables for a host template, and reference them via macros in the command definition. If I need a different setting for a particular host, I can override these inherited values in that host's config. check_nrpe throws a bit of a wrench in this - I'd probably need a different command set up for each item I'd like to check via NRPE. Does it sound like I'm on the right track?
Another item I'm struggling with is how to monitor partitions easily. I can check all filesystems by just passing "/" as the argument. This makes it easy since I don't care what the separate partitions are - if there is /var, /usr, and so on these will automatically be checked. One problem is that if any one of these exceeds the threshold, the notification will occur, even if all the others are fine. I am trying to avoid having to set up a service for each partition on each host. Any thoughts on this? I'd rather use Nagios for this rather than something like Vertias Volume Manager's space monitoring.
My generic host template:
define host{
name generic-host ; The name of this host template
notifications_enabled 1 ; Host notifications are enabled
event_handler_enabled 1 ; Host event handler is enabled
flap_detection_enabled 1 ; Flap detection is enabled
failure_prediction_enabled 1 ; Failure prediction is enabled
process_perf_data 1 ; Process performance data
retain_status_information 1 ; Retain status information across program restarts
retain_nonstatus_information 1 ; Retain non-status information across program restarts
notification_period 24x7 ; Send host notifications at any time
register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE!
#Default threshold variables
#check_ping
_PING-RTA-W 50 ;Round Trip Average Warn
_PING-RTA-C 100 ;Round Trip Average Crit
_PING-PL-W 10% ;Packet Loss Warn
_PING-PL-C 20% ;Packet Loss Crit
_PING-PKT 5 ;Packet count
}
My check_ping command:
define command{
command_name check_ping
command_line $USER1$/check_ping -H $HOSTADDRESS$ -w $_HOSTPING-RTA-W$,$_HOSTPING-PL-W$ -c $_HOSTPING-RTA-C$,$_HOSTPING-PL-C$ -p $_HOSTPING-PKT$
}
Robert C. Cipriani
Senior Network Administrator
Tampa Bay Division IT
Bright House Networks
W: (727) 329-2000 x74264
M: (727) 365-1231
Nolite id cogere, cape malleum majorem
________________________________
CONFIDENTIALITY NOTICE: This e-mail may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient of this e-mail, please notify the sender immediately by return e-mail, purge it and do not disseminate or copy it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20071220/85519d74/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
More information about the Users
mailing list