Availability report shows large amount of Undetermined Time
Posted: Wed Apr 01, 2020 10:44 am
Hi,
Today I tried to generate an availability report, but the numbers presented seemed off (100 % percent uptime? I know that's not the case). Also, some of the reports seemed to be highly sensitive to the the "First Assumed Service State" option - e.g. going from 100 % "Ok" to 100 % "Warning".
I tried to generate a legacy availability report instead, which turned out quite interesting. Reports from the last few days look all right but older reports shows a lot of "Undetermined". A report covering the first three months of this year shows 97 % "undecidable" for every single service.
I am not quite sure how to troubleshoot this issue. What do you think is the cause of this behaviour?
I suspect this could be some kind of database issue.
Could it be the case, that for a long period of time Nagios hasn't been able to write availability information correctly? Where does Nagios expect to find this information? We can access state history without problems.
If this is indeed a case of availability-data missing from the database, is it possible to regenerate this data based on the state history?
Our system is running NagiosXI 5.6.5 on CentOS 7, 64-bit, manual install.
Edit: While investigating this issue I upgraded XI to version 5.6.12. The behaviour described above remains unchanged.
Today I tried to generate an availability report, but the numbers presented seemed off (100 % percent uptime? I know that's not the case). Also, some of the reports seemed to be highly sensitive to the the "First Assumed Service State" option - e.g. going from 100 % "Ok" to 100 % "Warning".
I tried to generate a legacy availability report instead, which turned out quite interesting. Reports from the last few days look all right but older reports shows a lot of "Undetermined". A report covering the first three months of this year shows 97 % "undecidable" for every single service.
I am not quite sure how to troubleshoot this issue. What do you think is the cause of this behaviour?
I suspect this could be some kind of database issue.
Could it be the case, that for a long period of time Nagios hasn't been able to write availability information correctly? Where does Nagios expect to find this information? We can access state history without problems.
If this is indeed a case of availability-data missing from the database, is it possible to regenerate this data based on the state history?
Our system is running NagiosXI 5.6.5 on CentOS 7, 64-bit, manual install.
Edit: While investigating this issue I upgraded XI to version 5.6.12. The behaviour described above remains unchanged.