-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
D. Emmanuel Feinsmith schrieb:
> Dear Alessandro,
>
> You are more than likely eating up the cpu and memory with the memcpy's
> executed by each fork of your check_nrpe and check_icmp services. You
> can prove this out to yourself by using top to observe the behaviour of
> the nagios processes. I would also suggest that there is nothing else
> eating up CPU and memory on your nagios server box and keep the box
> dedicated. Running top will show if there is resource contention on your
> monitoring server. Keep in mind that check_nrpe is amongst the slowest
> possible commands nagios can execute because it has to wait for whatever
> timeout period you entered in your client nrpe.cfg for the nrpe daemon
> to respond. This can take seconds in some cases. A much more scalable
> solution is to enable passive checks (using nsca/send_nsca) on some or
> all of your clients)
True words.
@Alessandro:
If you are able to group responsibilities in the mind of nagios
contagroups like:
All Disk checks should be notified to contactgroup ABC and all xy checks
to another group, you could give check_multi a try.
It's a realy nice hack resulting in fewer plugin calls by grouping real
plugins. One plugin to many so far.
Read more:
http://my-plugin.de/wiki/projects/check_multi/start (english)
Regards,
Hendrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkmbGIAACgkQlI0PwfxLQjmCLgCfZMgRRjbiTC7X3WNRgOBLniWb
TKIAn3EzYcpTODqlm6voQWg4cnkAw0DT
=9vsa
-----END PGP SIGNATURE-----
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]