Changes between Version 14 and Version 15 of doc/usage/nagios/nsca
- Timestamp:
- 07/12/09 20:09:29 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
doc/usage/nagios/nsca
v14 v15 224 224 The configuration is at the end layer quite simple you have a "check" and a "host" and you connect them with a service. Like I show at the bottom line in the diagram above. Whats makes this a tad more complicated is that you can inherit things from a "parent" definition. Which is what I show with arrows (bottom to top) above. The templates with dashed lines are the base templates which all services and hosts inherit. 225 225 226 === 5.2 Template === 226 === 5.2 Passive Checks === 227 The main difference between passive checks and active checks are the following two flags: 228 '''active_checks_enabled''':: 229 Active service checks are enabled 230 '''passive_checks_enabled''':: 231 Passive service checks are enabled/accepted 232 So adding the following will "change" an active check to a passive check. 233 {{{ 234 active_checks_enabled 0 ; Active service checks are enabled 235 passive_checks_enabled 1 ; Passive service checks are enabled/accepted 236 }}} 237 So you say what shall I enter for command for my passive checks? 238 239 There are several options for this depending on what you want I wont (as always) go into the details in this quick guide but the short of it is either you use check_dummy or you use the actual command and setup freshness checks. With freshness checks active it means that if a result is not submitted Nagios will actively go out and seek the information (this is what I would recommend for host checks at least). 240 241 === 5.3 Template === 227 242 First, its best practice to create a new template for each different type of host you'll be monitoring. Let's create a new template for windows servers. 228 243 {{{ … … 246 261 defined in the sample localhost.cfg file that gets installed when you follow the Nagios quickstart installation guide. 247 262 248 === 5. 3Host definition ===263 === 5.4 Host definition === 249 264 Next we need to define a new host for the remote windows server that references the newly created tpl-windows-servers host template. 250 265 {{{ … … 262 277 the sample commands that are defined in the default NSC.ini file which ships with NSClient 0.3.7 or newer. 263 278 264 === 5. 4Service definitions ===279 === 5.5 Service definitions === 265 280 266 281 The following service will monitor the CPU load on the remote host. The "alias_cpu" argument which is passed to the check_nrpe command definition tells NSClient++ to run the "alias_cpu" command as defined in the alias section of the NSC.ini file.








