Availabilty reporting issues

[Jonathan Crocombe]

Hello

Has anybody found problems with the results from avail.cgi when you have 
scheduled downtime for services? The totals for OK/WARNING/CRITICAL are 
fine, but under the following circumstances there are errors in the 
scheduled/unscheduled calculations:

- The report must be run with a time period such as 'workhours'. The issue 
does not occur with 24x7. 
- The service must have a scheduled downtime period which lies outside of 
the report time period. 

Having looked through the code, I found that this was due to the critical 
time being calculated based on the rpttimeperiod (e.g. workhours), but the 
calcluation of the scheduled critical time ignoring this and always being 
24x7, i.e. 

        total(during rpttimeperiod) - scheduled(at any time) = unscheduled 


I made a change which got this working, but I've now found that when there 
is a downtime window that overlaps the time period being reported on the 
same issue occurs.

How are others dealing with these issues, or are you not generally using 
scheduled downtime periods? Are there any alternative tools that can be 
used to extract this reporting data from Nagios? I'm willing to spend some 
time trying to fix avail.cgi, but I need to extract these figures as soon 
as possible in the meantime.

Thanks

Jon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20110405/5b6d4e07/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
-------------- next part --------------
_______________________________________________
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