2.0b3 availability report has changed ? now outputs down and up log records outside date range ?

[Stanley Hopcroft]

Dear Folks,

I am writing to say that avail.cgi seems to have changed its action in 
that a report for a given service and a nominated interval, outputs 
down and up records __outside__ the interval (although the availability 
computation does seem to consist of the ups and downs in the intervals).

Here's an example (edited somewhat)

tsitc> lynx -dump -nolist -width=160 -auth=foo:bar
'http://tsitc/nagios/cgi-bin/avail.cgi?show_log_entries=&host=intranet&service=Corporate+Intranet+-+business+hours&timeperiod=custom&smon=4&sday=29&syear=2005&shour=0&smin=0&ssec=0&
emon=4&eday=29&eyear=2005&ehour=24&emin=0&esec=0&rpttimeperiod=&assumeinitialstates=yes&assumestateretention=yes&assumestatesduringnotrunning=yes&includesoftstates=no&
initialassumedservicestate=0&backtrack=1' 
| perl -ne 'print substr($_, 0, 80), "\n"'


   Service Availability Report

   Last Updated: Fri Apr 29 15:49:24 EST 2005

   Nagios® - www.nagios.org

   Logged in as foo

  .. snipped ..

                                              Service 'Corporate 
Intranet - busi


   Availability Report



                                                         29-04-2005 
00:00:00 to 


                                                                  
Duration: 0d 1


   First assumed service state:

   [Unspecified.....]          

   Report period:               Backtracked archives:

   [[ Current time range ]]     __

                                Update



                                                      [ Availability 
report comp


                                                                 Service 
State B


                                                                   
Service State


                                             State       Type / Reason         
T
                                          OK           Unscheduled        
0d 15h
                                                       Scheduled          
0d 0h 
                                                       Total              
0d 15h
 

  ..

                                                                    
Service Log 


                                                                 [ View 
full log


   Event Start Time Event End Time Event Duration Event/State Type 
Event/State I
   13-04-2005 17:22:09 13-04-2005 17:46:13 0d 0h 24m 4s SERVICE CRITICAL 
(HARD) 
   response. Unix error number 2 occurred: No such file or directory

   13-04-2005 17:46:13 14-04-2005 08:22:16 0d 14h 36m 3s SERVICE OK 
(HARD) Intra
   14-04-2005 08:22:16 14-04-2005 08:24:19 0d 0h 2m 3s SERVICE CRITICAL 
(HARD) I
   response. Unix error number 2 occurred: No such file or directory

   14-04-2005 08:24:19 14-04-2005 13:52:19 0d 5h 28m 0s SERVICE OK 
(HARD) Intran
   14-04-2005 13:52:19 14-04-2005 13:53:22 0d 0h 1m 3s SERVICE CRITICAL 
(HARD) I
   500 (Internal Server Error) read timeout Content-Type: text/plain 
Client-Date
   read timeout

   .. lots of intervening ups and downs snipped

   22-04-2005 08:04:18 22-04-2005 11:03:06 0d 2h 58m 48s SERVICE OK 
(HARD) Intra
   22-04-2005 11:37:14 22-04-2005 11:41:12 0d 0h 3m 58s SERVICE CRITICAL 
(HARD) 
   response. Unix error number 2 occurred: No such file or directory

   22-04-2005 11:41:12 22-04-2005 11:45:12 0d 0h 4m 0s SERVICE OK (HARD) 
Intrane

 
  .. more downs and ups snipped

   28-04-2005 16:00:40 28-04-2005 16:06:40 0d 0h 6m 0s SERVICE OK (HARD) 
Intrane
   28-04-2005 16:06:40 28-04-2005 16:08:33 0d 0h 1m 53s SERVICE CRITICAL 
(HARD) 
   response. Unix error number 2 occurred: No such file or directory

   28-04-2005 16:08:33 28-04-2005 17:34:48 0d 1h 26m 15s SERVICE OK 
(HARD) Intra
   29-04-2005 10:06:22 29-04-2005 10:08:26 0d 0h 2m 4s SERVICE CRITICAL 
(HARD) I
   response. Unix error number 2 occurred: No such file or directory

   29-04-2005 10:08:26 29-04-2005 14:29:30 0d 4h 21m 4s SERVICE OK 
(HARD) Intran
   29-04-2005 14:29:30 29-04-2005 14:31:29 0d 0h 1m 59s SERVICE CRITICAL 
(HARD) 
   response. Unix error number 2 occurred: No such file or directory

   29-04-2005 14:31:29 29-04-2005 15:49:24 0d 1h 17m 55s+ SERVICE OK 
(HARD) Intr
tsitc> 


IIRC formerly it would only display log messages for the requested 
interval. In this case, I expect only ups and downs for today (Apr 29).

This is no big deal but I have a small application that extracts the log 
entries (since they show up time, down time and interval down or up), 
formats them as CSV and mails them as an attachment (sometimes people 
only like numbers when they are in Excel).

Is this a new behaviour of avail.cgi (or am I imagining the 'former' 
behaviour) ?

If it is (ie it's not a bug), I will start hacking my application (Yes, 
I know its a stupid way of harvesting the data).

Yours sincerely.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: disclaimer.txt
URL: <https://www.monitoring-lists.org/archive/developers/attachments/20050429/b7657c60/attachment.txt>