Page 2 of 2
Re: monitor cpu utilization
Posted: Mon Mar 18, 2013 2:08 pm
by slansing
Ah, excellent, how is it working out for you now?
Re: monitor cpu utilization
Posted: Mon Mar 18, 2013 3:50 pm
by rahuliq
Guys Thanks for all the help
I have one more query. How can I graph and retain data for the above stats and also any other services being monitored by nagios.
Re: monitor cpu utilization
Posted: Tue Mar 19, 2013 10:01 am
by slansing
In order for Nagios to output graphs there must be performance data returned in a way that Nagios expects it "that follows the developer guidelines." A few solutions for graphing within Nagios Core is Nagios Graph:
http://nagiosgraph.sourceforge.net/
pnp4nagios:
http://www.pnp4nagios.org/
Another would be Cacti:
http://www.cacti.net/
Nagios does supply some graphing from the start, but these tools can be integrated into Nagios to give you more options.
Re: monitor cpu utilization
Posted: Tue Mar 19, 2013 2:49 pm
by rahuliq
I have installed pnp4nagios today and getting mixed results.
cpu utilization, load average is being graphed perfectly
for total_procs the rrd and xml file is not generated at all, which i learned from a friend could be a limitation
Also for localhost the disk space is being monitored perfectly with the graph showing total space, free space. space occupied
while for the remote host on which I'm monitoring disk space with nrpe the graph does not show any of the above fields. For example /home partition has 1.4TB of total space but the graph just shows one field that says about 190mb last, 190mb average, 190mb max nothing like that shown for localhost.
on the nagios console though i'm getting exact results and the result is identical to the localhost
Any suggestions
Re: monitor cpu utilization
Posted: Tue Mar 19, 2013 2:55 pm
by slansing
What is the command you are running for the disk check through NRPE on the remote host? The one that is not graphing? If it is a custom plugin it is possible that it was not built to return performance data for all those metrics, it may even be a different check altogether than is being ran on the localhost.