Historical Reports

[Samuel Kidman]

I use pnp4nagios for this.

http://docs.pnp4nagios.org/pnp-0.6/start

pnp4nagios saves the data in .rrd (Round Robin Database) format. I think
you could turn these into .csv format if you wanted to. Pnp4nagios works
by recording the perfdata from Nagios plugins, so you would need to make
sure your plugins are outputting performance data first (see here
http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN201). The
graphs are presented through a web interface.

The only gripe I have with it is the graphs are rarely ever up-to-date
when you get them- you're always about 5-10 minutes behind. It would be
nice if there was a way of triggering the  databases to be updated and
graphs to be drawn in their most up-to-date form as soon as they are
requested.



-----Original Message-----
From: Lingan Vairavamoorthy [mailto:lingan at avantiagroup.co.uk] 
Sent: Monday, 19 September 2011 8:43 PM
To: Andreas Ericsson; Nagios Users List
Subject: Re: [Nagios-users] Historical Reports

Andreas,

Thanks for that.

I was just looking at RRD Tool and N2RRD are they the more traditional
ways of logging and analysing historical data?

It's just a little vague on the Nagios documentation - as I'm really
looking at the following.

1. Proving Nagios is doing the checks
2. Looking at trends in the performance (even if things are working - as
working doesn't necessarily mean working well).
3. CSV raw data and graphing of the data.


Lingan

-----Original Message-----
From: Andreas Ericsson [mailto:ae at op5.se]
Sent: 19 September 2011 12:43
To: Nagios Users List
Cc: Lingan Vairavamoorthy
Subject: Re: [Nagios-users] Historical Reports

On 09/19/2011 12:43 PM, Lingan Vairavamoorthy wrote:
> I've looked through the posts and haven't seen anything on full 
> logging information.
> 
> What we are looking for is the ability to view all the checks that 
> have occurred on a host/service regardless if there was a change of 
> state.
> 
> This will enable us to do graphing on performance data and look at 
> trends when states would not have changed.
> 
> i.e. We are checking a response to a web page and we only warn on 
> large delays - but we would like to actually record all the timings it

> takes to visit that web page regardless if the state changed from OK 
> to WARN. So that we would have a entry in the historical logs for 
> every check. Is that feasible?
> 

Look up 'stalking' in the nagios docs. I think that does what you want.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war on
peace.

------------------------------------------------------------------------
------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA Learn
about the latest advances in developing for the BlackBerry® mobile
platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry® DevCon
today!
http://p.sf.net/sfu/rim-devcon-copy1
_______________________________________________
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

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
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