Hi
I have configured one of my RHEL 5.3 x86_64 bit server as a Nagios monitoring host and the nagios core version installed is 3.5.0.
My environment has OEL 5.3, RHEL 5.3/6, SLES 10 and HPUX 11i V3 servers
Recently i have added check_memory plugin in OEL and in RHEL servers which is working fine. But when it comes to graphs, it is not showing any graphs.
I have checked rrd directory for the relavant rrd files under "each server's" directory but found there is no relavant entry is created.
I did delete all the contents under /var/nagios/rrd directory to check whether it is creating new files for the newly added plugins but failed.
Please let me know how to enable graphs for newly added plugins.
Regards
Kingston S
Nagios Graphs for newly added plugin
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Nagios Graphs for newly added plugin
It is possible the plugin you added doesn't return performance data, and a graph would not be generated.
If you look at the service status detail page, on the advanced tab is there performance data?
If you look at the service status detail page, on the advanced tab is there performance data?
Re: Nagios Graphs for newly added plugin
Hi
Sorry for the delayed reply. The following are the contents i could see from nagios page for the particular service from the specific server.
Sorry for the delayed reply. The following are the contents i could see from nagios page for the particular service from the specific server.
So, as you said, my memory plugin is not sending any performance data to the graph. Could you also please tell me how to check plugins for performance data compatibility?For Load:
Current Status: WARNING (for 4d 15h 57m 51s)
Status Information: WARNING - load average: 12.61, 13.67, 13.82
Performance Data: load1=12.610;15.000;30.000;0; load5=13.670;10.000;25.000;0; load15=13.820;5.000;20.000;0;
Current Attempt: 1/1 (HARD state)
Last Check Time: 03-25-2014 00:48:33
Check Type: ACTIVE
Check Latency / Duration: 0.467 / 5.780 seconds
Next Scheduled Check: 03-25-2014 09:01:33
Last State Change: 03-20-2014 17:10:34
Last Notification: 03-20-2014 17:10:43 (notification 2)
Is This Service Flapping? NO (11.71% state change)
In Scheduled Downtime? NO
Last Update: 03-25-2014 09:08:23 ( 0d 0h 0m 2s ago)
For Memory:
Current Status: OK (for 17d 18h 3m 54s)
Status Information: Memory OK - 35.1% (8394916 kB) used
Performance Data:
Current Attempt: 1/1 (HARD state)
Last Check Time: 03-24-2014 20:25:33
Check Type: ACTIVE
Check Latency / Duration: 0.351 / 7.569 seconds
Next Scheduled Check: 03-25-2014 09:02:33
Last State Change: 03-07-2014 15:07:10
Last Notification: N/A (notification 0)
Is This Service Flapping? NO (0.00% state change)
In Scheduled Downtime? NO
Last Update: 03-25-2014 09:11:03 ( 0d 0h 0m 1s ago)
Current Status: OK (for 17d 18h 3m 54s)
Status Information: Memory OK - 35.1% (8394916 kB) used
Performance Data:
Current Attempt: 1/1 (HARD state)
Last Check Time: 03-24-2014 20:25:33
Check Type: ACTIVE
Check Latency / Duration: 0.351 / 7.569 seconds
Next Scheduled Check: 03-25-2014 09:02:33
Last State Change: 03-07-2014 15:07:10
Last Notification: N/A (notification 0)
Is This Service Flapping? NO (0.00% state change)
In Scheduled Downtime? NO
Last Update: 03-25-2014 09:11:03 ( 0d 0h 0m 1s ago)
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: Nagios Graphs for newly added plugin
Well, this is totally dependent on the author of the plugin, though there are a few key points to look for as are specified here:
http://nagios.sourceforge.net/docs/3_0/perfdata.html
https://nagios-plugins.org/doc/guidelines.html
Specifically looking for direct output pipes contained in an exit string or block would be a heavy indicator of it's presence, that, and looking at the usage output of a plugin, and what it actually returns when ran.
http://nagios.sourceforge.net/docs/3_0/perfdata.html
https://nagios-plugins.org/doc/guidelines.html
Specifically looking for direct output pipes contained in an exit string or block would be a heavy indicator of it's presence, that, and looking at the usage output of a plugin, and what it actually returns when ran.