Skip to content
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

Indicate the number of affected children by a particular parent #1058

Closed
nilmerg opened this issue Sep 17, 2024 · 0 comments · Fixed by #1062
Closed

Indicate the number of affected children by a particular parent #1058

nilmerg opened this issue Sep 17, 2024 · 0 comments · Fixed by #1062
Assignees
Labels
area/representation Affects the representation of information enhancement New feature or improvement

Comments

@nilmerg
Copy link
Member

nilmerg commented Sep 17, 2024

We want to show the number of affected children in case a parent has a problem.

It should look like this:
image

Notes

The monitoring module had such an indicator for services of a host in the past. It was dropped entirely in recent versions, due to technical limitations.

To bypass these, the actual number will be calculated by Icinga 2 in advance. This makes it a static value, as calculating it to represent the actual affected children is too expensive.

This also excludes the possibility for Icinga DB Web to apply role restrictions on it.

The description for this indicator then can be phrased like this: Up to <n> affected children

But it should only be shown in case there are actually any children affected, host_state.affects_children (column name not final yet) should allow to conditionally show it.

This indication then has the only effect of making the element stand out in lists, so that is visible at first glance and the user can click on it, to then analyze the incident more closely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/representation Affects the representation of information enhancement New feature or improvement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants