Nagios Graph not displaying correct values

[James Osbourn]

I tried adding this map but it did not remove the orginal values from the graph and I could not find where they are stored.  I do not think that the problem is related to 100 vs 1024 as some manual calculations do not match again the value that I am seeing on the graph.

It has been a while since I have played with RRD and I would of expected a standard check command from Nagios to graph correctly.  It just seems to be the RRD interpolation of the performance data as the check command is outputting the correct performance data values.

James

From: Claudio Kuenzler [mailto:ck at claudiokuenzler.com]
Sent: 13 December 2011 15:43
To: Nagios Users List
Subject: Re: [Nagios-users] Nagios Graph not displaying correct values

Some of the default Nagiosgraph map entries are strange and behave not as expected.
I basically replaced all the existing entries by own ones.

If you like you can use the following one:

# Service Type: check_disk
# Nagiosgraph regex by Claudio Kuenzler
# Check: /usr/lib/nagios/plugins/check_disk -w 20% -c 10% -p /
# Output: DISK OK - free space: / 235120 MB (66% inode=95%):
# Perfdata: /=119211MB;298635;335964;0;373294
/perfdata:(.*)=(\d+)MB;(\d+);(\d+);(\d+);(\d+).*/
#/perfdata:(\W)=(\d+)MB;(\d+);(\d+);(\d+);(\d+).*/ # only / partition
and push @s, [diskusage,
        ['used', GAUGE, $2*1000**2 ],
        ['total', GAUGE, $6*1000**2 ] ];

Note that this is a very basic graph which shows the total and current partition usage. Feel free to modify it :-)
On Tue, Dec 13, 2011 at 11:41 AM, James Osbourn <james.osbourn at citrix.com<mailto:james.osbourn at citrix.com>> wrote:
I have a weird situation where the Nagios Graph values are not the actual values for a filesystem

Eg I have a filesystem and if I run a df I get

$ df -h .
Filesystem            Size  Used Avail Use% Mounted on
filer01:/vol/data1    443G  400G   44G  91% /mnt/filer01_data1

If I run the Nagios check_disk command I get the correct values

# ../libexec/check_disk -w 10% -c 5% -p /usr/groups/sources
DISK WARNING - free space: /usr/groups/sources 44073 MB (9% inode=48%);| /usr/groups/sources=409354MB;408084;430755;0;453427

But when you look at the graph the figures are all wrong


Has anyone else seen this?  I was going to look at the usage to try and forecast usage but it will now be very hard.  I have just installed Nagios Graph based on the default installation and using the default check_disk plugin.

Thanks

James



------------------------------------------------------------------------------
Systems Optimization Self Assessment
Improve efficiency and utilization of IT resources. Drive out cost and
improve service delivery. Take 5 minutes to use this Systems Optimization
Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net<mailto:Nagios-users at lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20111214/cccf4437/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Cloud Computing - Latest Buzzword or a Glimpse of the Future?
This paper surveys cloud computing today: What are the benefits? 
Why are businesses embracing it? What are its payoffs and pitfalls?
http://www.accelacomm.com/jaw/sdnl/114/51425149/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null