Changes between Version 1 and Version 2 of OMDconfiguration

Show
Ignore:
Timestamp:
10/04/11 10:51:58 (7 years ago)
Author:
jonmills (IP: 152.54.8.104)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OMDconfiguration

    v1 v2  
    55Use the tarball attached to this page to get an idea of a basic Check_MK configuration suitable for monitoring a Eucalyptus cluster.  (Note that you'll need to change hostnames found in hosts.mk to suit your environment). 
    66 
    7 All of the files described here are complete arbitrary, and were just the logical layout preferred by this author.  If you pleased, you could group all Check_MK declarations into one big main.mk file (just as you can write all Nagios object configuration into one big nagios.cfg -- but who does that?). 
     7All of the files described here are completely arbitrary, and were just the logical layout preferred by this author.  If you pleased, you could group all Check_MK declarations into one big main.mk file (just as you can write all Nagios object configuration into one big nagios.cfg -- but who does that?). 
    88 
    99== main.mk == 
     10I try to define global things here, like: 
    1011 
     12{{{ 
     13define_hostgroups = True 
     14define_servicegroups = True 
     15define_contactgroups = True 
     16nagios_illegal_chars = '`~!$%^&*|\'"<>?,()=' 
     17generate_hostconf = True 
     18perfdata_format = "pnp" 
     19tcp_connect_timeout = 25.0 
     20inventory_max_cachefile_age = 120 # seconds (Default: 120 seconds) 
     21inventory_check_interval = 3 # minutes 
     22inventory_check_severity = 1 
     23always_cleanup_autochecks = True 
     24}}} 
     25 
     26Note that setting the 'inventory_check_interval' means that Check_MK will use the check_mk_agent to run a regularly scheduled inventory of the host that it's monitoring.  So it can tell you when it's not monitoring everything that it could be monitoring.  Setting 'inventory_check_severity' to 1 means that when the service 'Check_MK inventory' discovers a check it knows about, but which it isn't monitoring, it goes into WARNING status (recall that in Nagios lingo, OK is an exit status 0, WARNING is 1, CRITICAL is 2, and UNKNOWN is 3). 
    1127 
    1228== active.mk ==