We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This issue has been migrated from Redmine: https://dev.icinga.com/issues/13105
Created by mfrosch on 2016-11-09 10:57:39 +00:00
Assignee: (none) Status: Resolved (closed on 2016-12-08 09:45:03 +00:00) Target Version: (none) Last Update: 2016-12-08 09:45:03 +00:00 (in Redmine)
It's currently only summing up critical states, if e.g. the database is not initialized.
But it should actually show a proper state for everything. So the admin see's undeployed changes and other issues like pending schema changes.
Relations:
The text was updated successfully, but these errors were encountered:
Updated by mfrosch on 2016-11-09 10:58:22 +00:00
I think it is even not working at all.
getState() is not triggering hasProblems -> checkHealth -- which sets the internal state in the first place.
Sorry, something went wrong.
Updated by mfrosch on 2016-11-09 10:58:29 +00:00
Updated by tgelf on 2016-11-09 12:13:40 +00:00
Updated by tgelf on 2016-11-09 12:14:32 +00:00
We should IMO fix this in Icinga Web 2, states do not bubble/sum up as expected
Updated by tgelf on 2016-11-09 12:15:01 +00:00
Updated by elippmann on 2016-12-08 09:45:03 +00:00
Applied in changeset b3bc1b6f81c2fe1ec2d23401872826e7499bdc93.
No branches or pull requests
This issue has been migrated from Redmine: https://dev.icinga.com/issues/13105
Created by mfrosch on 2016-11-09 10:57:39 +00:00
Assignee: (none)
Status: Resolved (closed on 2016-12-08 09:45:03 +00:00)
Target Version: (none)
Last Update: 2016-12-08 09:45:03 +00:00 (in Redmine)
It's currently only summing up critical states, if e.g. the database is not initialized.
But it should actually show a proper state for everything. So the admin see's undeployed changes and other issues like pending schema changes.
Relations:
The text was updated successfully, but these errors were encountered: