SLA Report does not account for WARNING states

[willfurnell]

Describe the bug

It currently appears that the IcingaDB SLA reporting does not account for WARNING states - even in a HARD state, as a sample report for a service shows as 100% OK even though it's been in WARNING for a number of times over the report period

To Reproduce

Set up a new SLA report on a service that has only ever gone into the WARNING state.

Expected behavior

An option is provided, or it's part of the default functionality, that WARNING states are accounted for in the SLA report, as WARNING still means that there was an issue with the service and that it wasn't running perfectly.

Your Environment

Include as many relevant details about the environment you experienced the problem in

• Icinga DB version: v1.1.1
• Icinga 2 version: r2.14.0-1
• Operating System and version: CentOS 7
• reporting version: 0.10.0

Additional context

I've reported this issue in this repository rather than icingadb-web as this appears to be where the get_sla_ok_percent schema is developed