SLA report not taking active downtimes into account

[andrpp]

Describe the bug

I noticed that the SLA reports do not take into account active downtime periods for calculating proper host sla

To Reproduce

Steps to reproduce the behavior:

1. create an 4 hour SLA report
2. schedule a fixed downtime period for a server
3. poweroff the server
4. check SLA report

Expected behavior

active downtime periods should be taken into accounts when calculating SLA.

Screenshots

SLA report while host is in downtime period and powered on:

SLA report after the host has been powered off(couple minutes later):

Even though the host has been powered back on, the SLA is still affected:

As soon as the downtime expired, the SLA is back to 100%

Your Environment

• Module version: 0.9.0
• Dependent module versions:
• Icinga Web 2 version and modules (System - About): 2.6.3
• Web browser and version: google chrome 73.0.3683.103
• Icinga 2 version used (icinga2 --version): r2.10.4-1
• MySQL version (mysql --version): mysql Ver 15.1 Distrib 10.3.14-MariaDB
• PHP version used (php --version): PHP 7.0.33-0+deb9u3
• Server operating system and version: Debian GNU/Linux 9.9 (stretch)

Additional context

this is my first issue, so please bear with me, let me know if I missed to add relevant and required

[lippserd]

Hi,

Thanks for the report. You're right that active downtimes are not considered for the SLA. We may introduce this in one of our next releases.

Best, Eric

[danielboydston]

It would be great to have this fixed. Running into the same issue.

[izzy]

Same here and this is a total dealbreaker. It's imho not even really an SLA report if it doesn't take downtimes into account.