z

Commercial Support Clients: Clients with support contracts can get escalated support assistance by visiting Nagios Answer Hub. These forums are for community support services. Although we at Nagios try our best to help out on the forums here, we always give priority support to our support clients.

[Nagios-devel] syslog scanning [Re: Nagios-devel digest, Vol 1 #80 - 1 msg]

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.

[Nagios-devel] syslog scanning [Re: Nagios-devel digest, Vol 1 #80 - 1 msg]

Postby Guest » Tue Jul 02, 2002 4:38 am

Hi Kenneth,

If you want to set an warning/critical status for syslog messages, there
is a way to do it _as the message arrives_ (without scanning log files
on disk).

How? Take a look at syslog-ng (find it through freshmeat.net).
With this syslog daemon, you can have certain log messages fed into the
standard input of a perl script, and you can have this one submit
passive service checks to nagios when the right (or wrong?) message
arrives.

This way is easy to set alert statuses in nagios, but you have to to
think about a way to set the 'normal' status when needed. And that's
another issue... I think this depends a lot on what you want to monitor
with syslog messages.

Regards,
Guy

On Tue, 2002-06-25 at 21:07, nagios-devel-request@lists.sourceforge.net
wrote:
> Send Nagios-devel mailing list submissions to
> nagios-devel@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/nagios-devel
> or, via email, send a message with subject or body 'help' to
> nagios-devel-request@lists.sourceforge.net
>
> You can reach the person managing the list at
> nagios-devel-admin@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Nagios-devel digest..."
>
>
> Today's Topics:
>
> 1. Re: Nagios-devel digest, Vol 1 #79 - 2 msgs (Kenneth Ray)
>
> --__--__--
>
> Message: 1
> Date: Tue, 25 Jun 2002 09:02:30 -0400
> From: "Kenneth Ray"
> To: nagios-devel@lists.sourceforge.net
> Subject: [Nagios-devel] Re: Nagios-devel digest, Vol 1 #79 - 2 msgs
>
>
> --------------C077B2CB75BDC55F4842EA5E
> Content-Type: text/plain;
> charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> >
>
> hi everyone,
> with the new Nagios taking the place of Netsaint, I have a few things that i would like to share with the group if anyone is interested.
> We have been using a highly modified Netsaint_statd to run remote checks and have developed a couple checks that were not in the original. First let me say, im "at best" a novice perl programmer so the code im sure could use some clean up. I went To Nick Rienking's site but couldnt find contact info. so i figured i would post here.
> here is the checks i added
>
> check_messages.pl (client send a request to daemon to look in messages file for WARNING,OFFLINE,Error... daemon looks, parses and sends back either ok or not ok.)
>
> check_metastat.pl (client sends request to daemon to run the Solstice Volume command 'metastat' on local machine and if the volumes report anything other than a Status of "ok" the daemon sends to the client either ok,unknown, or error. Unknown is only returned when the "metastat' program is not in the right place. /usr/sbin)
>
>
>
> the problems with my code.
> It has been programmed by me, a novice Perl programer. It works but im sure someone out there who is more experienced than I, could improve on it. Its OS specific "Solaris 8" , though in some cases it can be easily adapted to work with most OS systems. and rather than attempting to use the OS Hash, i put the actual OS commands in the checks
> themselves.
>
> IF anyone wants to use this code, let me know, ill put it in an email
>
> Sincerly,
> Kenneth Ray
>
> P.S. Also on a side note, im still working on the Solaris Package, testing it on solaris 9 and 8, plan to test it on Solaris 2.6 when it works correctly on the other 2.
>
>
>
> --
> ==========================================================================
>
> This message and any attachments are confidential to the ordinary user
> of the e-mail address to which it was addressed and may also be
> privileged. If you receive this message in error please immediately
> delete it and all copies of it from your system, destroy any hard copies
> of it and notify the sender. You must not, directly or indirectly, use,
> disclose, distribute, print or copy any part of this message if you are
> not the intended recipient. Internet communications cannot be guaranteed
> to be secure or error-free as informa

...[email truncated]...


This post was automatically imported from historical nagios-devel mailing list archives
Original poster: guy.vandenbergh@belnet.be
Guest
 

Return to Open Source Nagios Projects

Who is online

Users browsing this forum: No registered users and 11 guests