Nagios各组件简述及nrpe详解
http://www.cnblogs.com/JemBai/archive/2012/04/10/2440075.html
only command[check_total_procs]need to be updated to “-w 200 –c 250”.
No need to update the –w and –c for command[check_procs].
Test procedure:
To make it more clear, I tested it per thefollowing table: (0 stands for using “-w 150 –c 200”, 1 stands for using “-w200 –c 250)
Test index |
command[check_total_procs] |
Command[check_procs] |
Result |
1 |
0 |
0 |
Warning |
2 |
0 |
1 |
Warning |
3 |
1 |
0 |
NO Warning |
4 |
1 |
1 |
NO Warning |
1. Loginto db node(for example,VM001jeguan, but no change to nrpe.cfg onother nodes), update the /etc/nagios/nrpe.cfg per “Test index 1”
2. Ondb node, restart nrpe: systemctl restart nrpe
3. OnOAM node, restart Nagios: /etc/init.d/nagios restart
4. OnNagios GUI check the “Processes” status information
Repeat abovetest for the remaining tests(Test index 2, Test index 3, Text index 4)
Besides, I also checked the “Processes” item andgot the following findings:
1. The“Performance Data” is set by “command[check_total_procs]” instead of “command[check_procs]”
2. Thethreshold for the processes warning is determined by “–w” in command[check_total_procs]
3. Generally,we cannot get the result immediately when the nrpe.cfg is changed. The timeinterval between two checks is about 10m. But we can use “Re-schedule thenext check of this service” to change the “Next Scheduled Check”.