Hi all! I am observing some differences between which I see with MRTG and the output from check_local_mrtgtraf. For example, if I manually execute the command, I obtain the following thing:
# /usr/local/nagios/libexec/check_mrtgtraf -F \
/space/www/htdocs/mrtg.sysadminhaiku.com.ar/192.168.1.1_1.log -a AVG \
-w 1000000,1000000 -c 5000000,5000000 -e 10
Traffic OK - Avg. In = 410,0 B/s, Avg. Out = 797,0
B/s|in=410,000000B/s;1000000,000000;5000000,000000;0,000000
in=797,000000B/s;1000000,000000;5000000,000000;0,000000
The last values registered by MRTG that I see by the web interface are
the following:
`Daily' Graph (5 Minute Average)
Max Average Current
In 40.3 kb/s (0.0%) 3616.0 b/s (0.0%) 3272.0 b/s (0.0%)
Out 1809.5 kb/s (1.8%) 44.6 kb/s (0.0%) 6376.0 b/s (0.0%)
This is the service definition:
define service{
use generic-service ; Inherit values from a template
host_name Router#1
service_description Bandwidth Usage
check_command
check_local_mrtgtraf!/space/www/htdocs/mrtg.sysadminhaiku.com.ar/192.168.1.1_1.log!AVG!1000000,1000000!5000000,5000000!10
}
I do not have left very clear to what that difference can be due or if I
am losing myself in the interpretation of the data of Nagios plugin.
Thanks in advance.
Regards,
Daniel
--
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Squeeze - Linux user #188.598
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________ Nagios-users mailing list [email protected] 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
