Details of Nagios Reporting

Marc Powell marc at ena.com
Wed Jun 22 20:23:18 CEST 2005



> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Mohr James
> Sent: Wednesday, June 22, 2005 1:05 PM
> To: Nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Details of Nagios Reporting
> 
> Hi All!
> 
> As the subject says, I am looking for details of how the nagios
> reporting works (versions 1.2 and 2.0). In particular, I am looking
for
> confirmation that reporting cgi's will automatically go through the
> archived log files to report. Looking through trends.c, I see that the
> number of archived logs to used is based on the 'backtrack_archives'
> variable and the default used is dependant on the frequency the logs
are
> rotated. It *seems* that regardless of what you set "Backtracked
> archives" to, it will automatically pull out the correct number of
> archived logs. Is this correct?

Nagios will automagically figure out what log files it needs to look at
for your reporting period only. The backtracked archives feature is
useful to determine the initial state of the host/service at the
beginning of the reporting period. For example, if you run a report for
this month but don't have any log entries for the host or service in
question until the 20th, nagios will show the first 19 days as
undetermined. If there was a log entry showing the host was OK on May
29th, you can use the backtracked archives feature to include that log
file as well to set the initial state. You can also use the First
assumed state option if you want to assume an initial starting state if
there is no log entry.

 
> I probably could see this better, if the graphics were being displayed
> correctly, but I am getting "Premature end of script headers:
> trends.cgi" (as well as histogram.cgi ), but that is a different
issue.

Check your web server error logs. They'll detail the problem. Typically
the GD libs are not available or not where they were at compile time.
 
> Another issue is the alert history. Is there any way to specify a
> specific date? Is there any way of specifying a range of dates?

No but you could grep the information out of the archived log files if
you needed that.
 
> Also I would be interested in any documentation describing the details
> of other aspects of the reporting.

There isn't much (http://nagios.sourceforge.net/docs/1_0/cgis.html).
Most of the CGI's are pretty standard/self explanatory if you're
familiar with monitoring systems. I haven't really seen any good
end-user documentation. Maybe others have...

--
Marc



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
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





More information about the Users mailing list