nagios && rrd

[Dean Bishop]

I believe that this is the aim of the apan project.

You can find it's project page on the nagios downloads section.

I don't know how far along he is now or how he is doing it but it might be
worth investigating.

dean

-----Original Message-----
From: John Sellens [mailto:jsellens at generalconcepts.com] 
Sent: April 15, 2003 10:49 AM
To: jason at cannonfodder.org; nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] nagios && rrd

| From: Jason Burnett <jason at cannonfodder.org>
| Date: Thu, 20 Mar 2003 17:15:55 -0500
| 
| Is anyone else using RRD to process the service-perf data? If so, what
| are you using to parse out the $PERFDATA$ & $OUTPUT$ info? We are
| working on perl to parse it out and put it in RRD for us, but if
| someone has found an easier way to do this please let me know.

My belief, which I haven't implemented yet, is that a good
graphing/trending mechanism is to log the host and service perfdata
from within Nagios, and then use Orca (http://www.orcaware.com/orca/)
to insert the data into RRD files and manage the HTML interface.

I'm reasonably optimistic that this is a good idea.

John
jsellens at generalconcepts.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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