How achieve the effect of having a different max_check_attempts values for WARNING and CRITIAL states Nagios

nagios

For example, I want that when service X check results in a WARNING state, it send a notification right away (max_check_attempts=1), but if the check results is CRITICAL (max_check_attempts=3), it check twice time more before send the notification. My requirement come from the fact that I configure different Nagios contacts for CRITICAL and WARNING.

My goal is avoid some kind of Nagios contacts receive a notification so soon (if is a Notif related to a WARNING state), still, I need other contacts get informed about a serious problem (CRITICAL state) asap.

Best Answer

To get the functionality you are looking for you want to use (host/service)escalations.

max_check_attempts

is a function of the service/host check itself, not if it's in a warning or critical state.

Related Solutions

Nagios disk check for windows server using hard values and not percentages

You can set a fixed size in nsclient++ CheckDriveSize command, see http://nsclient.org/nscp/wiki/CheckDriveSize . That said, NTFS suffers from performance problems on partitions that are greater than 80% full so just keep that in mind.

Nagios Monitoring – Recommended Warning and Critical Values for check_load

Linux load is actually simple. Each of the load avg numbers are the summation of all the core's avg load. Ie.

 1 min load avg = load_core_1 + load_core_2 + ... + load_core_n
 5 min load avg = load_core_1 + load_core_2 + ... + load_core_n
15 min load avg = load_core_1 + load_core_2 + ... + load_core_n

where 0 < avg load < infinity.

So if a load is 1 on a 4 core server, then it either means each core is used 25% or one core is 100% under load. A load of 4 means all 4 cores are under 100% load. A load of >4 means the server needs more cores.

check_load now have

 -r, --percpu
    Divide the load averages by the number of CPUs (when possible)

which means that when used, you can think of your server as having just one core and hence write the percent fractions directly without thinking of number of cores. With -r the warning and critical intervals becomes 0 <= load avg <= 1. Ie. you don't have to modify your warning and critical values from server to server.

OP have 5,10,15 for intervals. That is wrong. It is 1,5,15.

Best Answer

Related Solutions

Nagios disk check for windows server using hard values and not percentages

Nagios Monitoring – Recommended Warning and Critical Values for check_load

Related Topic