[Nagiosplug-devel] FW: Check_disk long perfdata getting truncated

[Garrett Honeycutt]

On Tue, 2005-09-13 at 07:52 -0700, T. Pascal wrote:
> I am running check_disk (nagios-plugins 1.4.1) 1.57 on RedHat ES3.0
> 
> /usr/lib/nagios/plugins/check_disk -u GB -w 20% -c 10% -p
> /home/oracle/arc_logs -p /home/oracle/u01 -p /home/oracle/u02 -p
> /home/oracle/u03 -p /home/oracle/u04 -p /home/oracle/u06
> DISK OK - free space: /home/oracle/arc_logs 93 GB (71%); /home/oracle/u01 5
> GB (51%); /home/oracle/u02 32 GB (98%); /home/oracle/u03 119 GB (31%);
> /home/oracle/u04 119 GB (31%); /home/oracle/u06 119 GB (31%);|
> /home/oracle/arc_logs=38GB;104;117;0;131 /home/oracle/u01=5GB;7;8;0;9
> /home/oracle/u02=1GB;25;28;0;32 /home/oracle/u03=270GB;311;350;0;389
> /home/oracle/u04=270GB;311;350;0;389 /home/oracle/u06=270GB;311;350;0;389
> 
> Running this via check_nrpe (2.0), the output is truncated so that this is
> reported by Nagios extended output (and in the $NAGIOS_SERVICEPERFDATA
> macro):
> 
> /home/oracle/arc_logs=38GB;104;117;0;131 /home/oracle/u01=5GB;7;8;0;9
> /home/oracle/u02=1GB;25;28;0;32 /home/oracle/u03=270GB;311;350;0;3
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________________
> Nagios Plugin Development Mailing List Nagiosplug-devel at lists.sourceforge.net
> Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel
> ::: Please include plugins version (-v) and OS when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null

Instead of running check_disk on each host and getting back all of the
data, create a command like check_disk_arc-logs and check_disk_u02 in
your nrpe.cfg and check each partition individually. This way the perf
data will not be too long and you can fine tune the warning and critical
levels.

Cheers,
-g

-- 
// Garrett Honeycutt
// Sr. Systems Administrator
// 3GUpload.com, Inc.
// 317.472.4969 Office