Hello Everyone,
I'm currently encountering an issue with icinga-reportings with jasperreports. Actually for any host the status stays at 0% availability if it didn't encounter any state change. By example, for any host without any issue since the reporting is in place, the availability is 0%
If any issue has been encountered, i get the correct availability result after the status restore.
I reproduced successfuly the issue by trying to turning off the NSclient on our main DC (checknt) and afterward, the availability percentage looks correct.
Here's a screen capture. As you can see, the ping didn't stop (it's a totaly different check), but with the NSclient++ shutdown, the check has failed and reported an "unavailability".
![]()
Here are the versions :
Icinga2 : 2.3.8
Icinga-reports : 1.10
Jasperreports : 5.5.0a
OS : Centos 6.5
Do you have any other idea? The first coming into my mind is an "ifdown" to trigger an alarm on all host, but you'll understand it's not really efficient.
Kind regards,
I'm currently encountering an issue with icinga-reportings with jasperreports. Actually for any host the status stays at 0% availability if it didn't encounter any state change. By example, for any host without any issue since the reporting is in place, the availability is 0%
If any issue has been encountered, i get the correct availability result after the status restore.
I reproduced successfuly the issue by trying to turning off the NSclient on our main DC (checknt) and afterward, the availability percentage looks correct.
Here's a screen capture. As you can see, the ping didn't stop (it's a totaly different check), but with the NSclient++ shutdown, the check has failed and reported an "unavailability".
Here are the versions :
Icinga2 : 2.3.8
Icinga-reports : 1.10
Jasperreports : 5.5.0a
OS : Centos 6.5
Do you have any other idea? The first coming into my mind is an "ifdown" to trigger an alarm on all host, but you'll understand it's not really efficient.
Kind regards,