Hide scheduled downtime in Executive Summary not respected

[RelyIT]

Hi,
I need to present Executive Summary Report or Availability Report for system owner.
But it does not work as expected when using "Hide scheduled downtime".
Checking this box does not give expected result.
I have attached file with screen shots.
Best regards,
Niklas

Manually installed Nagios XI 5.8.1 on CentOs 7.9 64bit VM

[benjaminsmith]

Hi,

The event log report only goes back to 2/18, but the Executive Summary report covers the period between 2/1 and 2/23. Can you zip up all the files nagios logs from February and send them to me in a PM and I'll take a look a the services for this host.

You'll find the logs in the following

Code: Select all

/usr/local/nagios/var/archives

The following command will zip up the last 30 files into /tmp/nagios-support.zip

Code: Select all

ls -Lt | head -30 | xargs zip /tmp/nagios-support.zip

Thanks,
Benjamin

[RelyIT]

Hi Benjamin

I have attached ZIP with log files.

I have also run the report with custom dates so it only covers days after check was created. This gives the same, in my opinion, faulty report.
I have attached a screenshot of this.

Thanks for removing my duplicate post, my fault for not reading that it takes some time for a post to be approved.

/Niklas

[benjaminsmith]

Hi @RelyIT,

Thanks for uploading those files. I just want to let you know that I'm reviewing them and will follow up shortly.

[benjaminsmith]

Hi RelyIT,

Frankly, so far I have not been able to locate the issue. I'm going setup a 5.8.1 to test this out, but the logs look right.

Code: Select all

nagios-02-10-2021-00.log:[1612825200] CURRENT SERVICE STATE: ihbsb.relyit.se;_ URL Content;OK;HARD;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.009 second response time
nagios-02-11-2021-00.log:[1612911600] CURRENT SERVICE STATE: ihbsb.relyit.se;_ URL Content;OK;HARD;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.009 second response time
nagios-02-12-2021-00.log:[1612998000] CURRENT SERVICE STATE: ihbsb.relyit.se;_ URL Content;OK;HARD;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.010 second response time
nagios-02-13-2021-00.log:[1613084400] CURRENT SERVICE STATE: ihbsb.relyit.se;_ URL Content;OK;HARD;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.009 second response time
nagios-02-14-2021-00.log:[1613170800] CURRENT SERVICE STATE: ihbsb.relyit.se;_ URL Content;OK;HARD;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.009 second response time
nagios-02-15-2021-00.log:[1613257200] CURRENT SERVICE STATE: ihbsb.relyit.se;_ URL Content;OK;HARD;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.009 second response time
nagios-02-16-2021-00.log:[1613343600] CURRENT SERVICE STATE: ihbsb.relyit.se;_ URL Content;OK;HARD;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.009 second response time
nagios-02-17-2021-00.log:[1613430000] CURRENT SERVICE STATE: ihbsb.relyit.se;_ URL Content;OK;HARD;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.009 second response time
nagios-02-18-2021-00.log:[1613516400] CURRENT SERVICE STATE: ihbsb.relyit.se;_ URL Content;OK;HARD;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.009 second response time
nagios-02-19-2021-00.log:[1613602800] CURRENT SERVICE STATE: ihbsb.relyit.se;_ URL Content;OK;HARD;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.009 second response time
nagios-02-20-2021-00.log:[1613689200] CURRENT SERVICE STATE: ihbsb.relyit.se;_ URL Content;OK;HARD;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.009 second response time
nagios-02-20-2021-00.log:[1613734587] SERVICE DOWNTIME ALERT: ihbsb.relyit.se;_ URL Content;STARTED; Service has entered a period of scheduled downtime
nagios-02-20-2021-00.log:[1613738548] SERVICE ALERT: ihbsb.relyit.se;_ URL Content;CRITICAL;HARD;1;CRITICAL - Socket timeout
nagios-02-20-2021-00.log:[1613738836] SERVICE ALERT: ihbsb.relyit.se;_ URL Content;OK;SOFT;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.126 second response time
nagios-02-20-2021-00.log:[1613746802] SERVICE DOWNTIME ALERT: ihbsb.relyit.se;_ URL Content;STOPPED; Service has exited from a period of scheduled downtime
nagios-02-21-2021-00.log:[1613775600] CURRENT SERVICE STATE: ihbsb.relyit.se;_ URL Content;OK;HARD;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.009 second response time
nagios-02-22-2021-00.log:[1613862000] CURRENT SERVICE STATE: ihbsb.relyit.se;_ URL Content;OK;HARD;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.009 second response time
nagios-02-23-2021-00.log:[1613948400] CURRENT SERVICE STATE: ihbsb.relyit.se;_ URL Content;OK;HARD;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.009 second response time
nagios-02-24-2021-00.log:[1614034800] CURRENT SERVICE STATE: ihbsb.relyit.se;_ URL Content;OK;HARD;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.010 second response time

Can you PM the system profile. I'd like to check the time settings and the logs as well.

Lastly, please run the legacy availability report, Reports > Legacy Reports > Availability, on this service for the same time period and post a screens shot. It will provide a detailed breakdown of scheduled vs unscheduled states.

legacy-availability.png

To send us your system profile.
Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button

Thanks,
Benjamin

[RelyIT]

Hi Benjamin
I have attached requested information.
I have also attached screen shot of Event Log during maintenance period. I have highlighted the Service OK that I believe is not beeing respected.
/Niklas

[benjaminsmith]

Hi,

I'm reaching out to the developer on this one as I believe there may be a bug here and I'm trying to confirm this the expected behavior.

For the Executive Summary report, if you select Assume State Retention: = No, and run the report, do you get the correct results?

--Benjamin

[benjaminsmith]

Hi,

Update. Let me know the results after making the change to the assumed state. I reached out to the developer on this one and he's pretty certain this is not a bug, however, it does make some complex assumptions on assumed state conditions and that is likely the discrepancy.

[RelyIT]

Hi Benjamin

Success! I have found the setting that gives me excpected result.

It is the Include Soft States that needs to be set to yes to give me "correct" result.
For reference, I have included Nagios-report-hard-state.PNG that shows default behaviour and Nagios-report-soft-state.PNG that shows my wanted behaviour.

We have a hard CRITICAL 2021-02-19 13:42:28 SERVICE ALERT: ihbsb.relyit.se;_ URL Content;CRITICAL;HARD;1;CRITICAL - Socket timeout
that is followed by soft OK 2021-02-19 13:47:16 SERVICE ALERT: ihbsb.relyit.se;_ URL Content;OK;SOFT;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.126 second response time

In my opinion this is the behaviour that I expect. There is probably a good explanation to why it is not default setting.

We now have knowledge on how to produce correct report for our customer.
Thanks for all your assistance.

/Niklas

[scottwilkerson]

Hi Benjamin

Success! I have found the setting that gives me excpected result.

It is the Include Soft States that needs to be set to yes to give me "correct" result.
For reference, I have included Nagios-report-hard-state.PNG that shows default behaviour and Nagios-report-soft-state.PNG that shows my wanted behaviour.

We have a hard CRITICAL 2021-02-19 13:42:28 SERVICE ALERT: ihbsb.relyit.se;_ URL Content;CRITICAL;HARD;1;CRITICAL - Socket timeout
that is followed by soft OK 2021-02-19 13:47:16 SERVICE ALERT: ihbsb.relyit.se;_ URL Content;OK;SOFT;1;HTTP OK: HTTP/1.1 200 OK - 3704 bytes in 0.126 second response time

In my opinion this is the behaviour that I expect. There is probably a good explanation to why it is not default setting.

We now have knowledge on how to produce correct report for our customer.
Thanks for all your assistance.

/Niklas

great!

Locking thread