logging check_* output

[Carroll, Jim P [Contractor]]

This was discussed recently.

Simply write a wrapper script for the check in question
(in your case, check_ping) and have it send the output to a file.

jc


> -----Original Message-----
> From: Rainer Huber [mailto:rainer.huber at gmx.at]
> Sent: Thursday, May 22, 2003 7:13 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] logging check_* output
> 
> 
> Hi!
> 
> Does anybody know if it is possible to log the output of the 
> check_* scripts
> into a logfile (STDOUT output).
> I've tried to put a "| tee logfile" behind the check_ping 
> command in the
> checkcommand definition but it did not work
> 
> Does the "Status Information" row in the "Service Detail" view contain
> exactly the output of the latest invocation of the check scripts?
> 
> The reason why I want to log the return string is that I am 
> getting warnings
> with PING monitoring (check_ping). The WEB interface shows 
> "PING WARNING -
> Packet loss = 0%, RTA = 22.30 ms" and when I invoke check_ping with
> corresponding parameters everything is ok (PING OK - Packet 
> loss = 0%, RTA =
> 1.10 ms). The connection between the hosts is a 10Mbps LAN, 
> so 22ms delay is
> simply too high.
> 
> I've disabled all other checks, so that there was no other 
> traffic on the
> network which could influence the test.
> the ouput of tcpdump shows, that there is no delay of 22.30 ms on the
> network side:
> ((check_ping invocation))
> 13:59:55.076690 192.168.2.99 > 192.168.1.100: icmp: echo request (DF)
> 13:59:55.077258 192.168.1.100 > 192.168.2.99: icmp: echo reply
> 13:59:56.076501 192.168.2.99 > 192.168.1.100: icmp: echo request (DF)
> 13:59:56.077205 192.168.1.100 > 192.168.2.99: icmp: echo reply
> 13:59:57.076448 192.168.2.99 > 192.168.1.100: icmp: echo request (DF)
> 13:59:57.077061 192.168.1.100 > 192.168.2.99: icmp: echo reply
> 13:59:58.076421 192.168.2.99 > 192.168.1.100: icmp: echo request (DF)
> 13:59:58.077073 192.168.1.100 > 192.168.2.99: icmp: echo reply
> 13:59:59.076442 192.168.2.99 > 192.168.1.100: icmp: echo request (DF)
> 13:59:59.077329 192.168.1.100 > 192.168.2.99: icmp: echo reply
> 
> ((triggered by nagios))
> 14:00:17.857437 192.168.2.99 > 192.168.1.100: icmp: echo request (DF)
> 14:00:17.858177 192.168.1.100 > 192.168.2.99: icmp: echo reply
> 14:00:18.848064 192.168.2.99 > 192.168.1.100: icmp: echo request (DF)
> 14:00:18.848796 192.168.1.100 > 192.168.2.99: icmp: echo reply
> 14:00:19.847542 192.168.2.99 > 192.168.1.100: icmp: echo request (DF)
> 14:00:19.848269 192.168.1.100 > 192.168.2.99: icmp: echo reply
> 14:00:20.847046 192.168.2.99 > 192.168.1.100: icmp: echo request (DF)
> 14:00:20.847766 192.168.1.100 > 192.168.2.99: icmp: echo reply
> 14:00:21.846503 192.168.2.99 > 192.168.1.100: icmp: echo request (DF)
> 14:00:21.847217 192.168.1.100 > 192.168.2.99: icmp: echo reply
> 
> Thanks in advance for any ideas/suggestions
> 
> regards
> Rainer
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: ObjectStore.
> If flattening out C++ or Java code to make your application fit in a
> relational database is painful, don't do it! Check out ObjectStore.
> Now part of Progress Software. http://www.objectstore.net/sourceforge
> _______________________________________________
> 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
> 


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
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