Check old data from logs

[Carroll, Jim P [Contractor]]

You might want to try an implement APAN for RRDtool-style trending.

jc

> -----Original Message-----
> From: Tong Young [mailto:Tong at keen.com]
> Sent: Tuesday, February 18, 2003 5:28 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Check old data from logs
> 
> 
> Is there a way for me to see what the previous check values were for a
> service check?
> 
> So I have a service check of my memory usage every 15 minutes.  Say I
> want to look back at the last 24 hours and see the value of all the
> checks every 15 minutes.
> 
> If I look at "Availability Report" it will say like 2HRS OK 
> then 4HRS OK
> and give me the initial value but not the values during those 
> 2 hours or
> 4 hours.
> 
> If I look at notification alerts, it will only give me the values that
> were emailed to me on change of status.  I do not want to add more
> emails to myself and have nagios email me every 15 minutes if the
> service is OK.
> 
> Is there another way to do what I want?
> 
> 
> -------------------------------------------------------
> 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: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/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