100% SLA report for when Host or Service did not exist

[jwilliams-shadowsoft]

Describe the bug

Service SLA and Host SLA do not seem to be aware of when the new Service or Host was brought into monitoring. Reports show 100% availability for time before Service or Host existed.

I suspect that if a host was deleted that it may give 100% results after it disappeared as well.

To Reproduce

Steps to reproduce the behavior:

1. Create time frame that starts before a sample Host existed.
2. Create report using that timeframe, either "Host SLA" or "Service SLA" and a filter that limits "host_name" to one host. Set "Breakdown" to Day, Week or Month. Update the report.
3. Run the report and observe the results from before the Host or Service existed.

Expected behavior

Either:

1. the report should omit results from before the Host or Service existed, or
2. the report should output message stating that the Host or Service did not exist before a certain date.

Screenshots

Director shows Host was created 2019-10-14:

Report definition:

Report result:

Your Environment

• Module version: 0.9.1
• Dependent module versions: icingaweb2-module-reporting 0.9.2
• Icinga Web 2 version and modules (System - About): icingaweb2 2.7.1

MODULE         VERSION   STATE     DESCRIPTION
director       1.7.0     enabled   Director - Config tool for Icinga 2
doc            2.7.1     enabled   Documentation module
fileshipper    1.1.0     enabled   Fileshipper for Icinga Director
idoreports     0.9.1     enabled   Reports for IDO
incubator      0.5.0     enabled   Incubator provides bleeding-edge libraries
ipl            v0.3.0    enabled   The Icinga PHP library
monitoring     2.7.1     enabled   Icinga monitoring module
pdfexport      0.9.1     enabled   PDF Export via Google Chrome/Chromium
reactbundle    0.7.0     enabled   ReactPHP-based 3rd party libraries
reporting      0.9.2     enabled   Reporting
vspheredb      1.1.0     enabled   VMware vSphere DB

• Web browser and version: Firefox 76.0.1
• Icinga 2 version used (icinga2 --version): 2.10.5
• MySQL version (mysql --version): MariaDB 5.5.64
• PHP version used (php --version): 7.1.30
• Server operating system and version: CentOS 7

Additional context

Add any other context about the problem here.