Describe the bug
I have an SLA report that works so far. However, the Icinga2 Master itself is displayed with an SLA of 0%. Is this a bug that it does not monitor itself or is it an incorrect configuration?
The Icinga2 master is monitored normally and also has a check_command for host alive.
To Reproduce
Steps to reproduce the behavior:
Create a SLA Report with a group filter, that contains normal hosts and the Icinga2 Master.
Expected behavior
A SLA value also for the Icinga2 Master
Screenshots
Your Environment
- Module version: 1.0.5
- Dependent module versions:
- Icinga Web 2 version and modules (System - About): 2.12.4
- Web browser and version: Chrome 138.0.7204.184
- Icinga 2 version used (
icinga2 --version): r2.15.0-1 with IcingaDB 1.4.0
- PHP version used (
php --version): 8.2.28
- Server operating system and version: RHEL9
Describe the bug
I have an SLA report that works so far. However, the Icinga2 Master itself is displayed with an SLA of 0%. Is this a bug that it does not monitor itself or is it an incorrect configuration?
The Icinga2 master is monitored normally and also has a check_command for host alive.
To Reproduce
Steps to reproduce the behavior:
Create a SLA Report with a group filter, that contains normal hosts and the Icinga2 Master.
Expected behavior
A SLA value also for the Icinga2 Master
Screenshots
Your Environment
icinga2 --version): r2.15.0-1 with IcingaDB 1.4.0php --version): 8.2.28