-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong state views #872
Comments
Hi, this is, I'm afraid, an expected limitation of the database + redis architecture. It's very similar to Icinga/icingadb-web#741. Here, the counts for the statistics are collected based only on database rows. The list entries however, will be affected by redis. So in Web, we cannot do anything (efficient) about this to prevent it. But the real problem for me, is that you experience this limitation to such an extent. Do you have the icingadb check enabled and running? The backlog performance data should be near zero, which it probably isn't in your case. I have no other explanation right now, please have a look if that's correct. |
Which value do you mean?
|
These hosts are VMs. |
This:
All are zero. Which is fine… I'll transfer this to icingadb, maybe the devs there are able to figure this out. |
The state of this host and it's services changed while the icingadb server was rebooting: Icinga2 master didn't reboot and was still running. This is part of
|
|
Log of Icinga2 master while IcingaDB shutdown.
|
I don't know if this a error of icinga2/icingadb or the icingaweb2.
I use a filter
/icingaweb2/icingadb/hosts?host.state.is_problem=y&sort=host.state.last_state_change%20desc&host.state.is_acknowledged=n
.Sometimes there are green hosts in this list.
If i click on this host i get a overview with 12 red services. But in details there are no red services.
Your Environment
Icinga Host:
Icingaweb2 Host:
Icingadb Host:
Execution Details
The text was updated successfully, but these errors were encountered: