-
Notifications
You must be signed in to change notification settings - Fork 23
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
Hide unreachable parents in root problems #1073
base: dependencies
Are you sure you want to change the base?
Conversation
61dfa18
to
5626597
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change causes false negatives.
For example, if there is an explicit dependency between two services with same host, and the host is down, then both the services become unreachable but also the dependency fails. And this change would filter out the unreachable parent service, which should not happen.
See the screenshot below for one such case
This seems to apply to any service-to-service dependency. See the screenshot below. So put it simply, if the host of the parent service is down, the parent service becomes unreachable. This in turn results in the dependency being failed. But according to the filter the parent service should be reachable. Hence, it might also be safe to conclude there will be false negatives for service-to-host dependencies as well. |
A node is responsible if: * it's a host which is reachable but has a problem * it's a service which is reachable but has a problem * it's a redundancy group which is reachable but has failed
They can now be unreachable, thus get the same icon as others. The state then isn't about reachability anymore, so it's just critical or ok.
5626597
to
1532fe5
Compare
I fully reworked this. Please have a look at it again. I used the following configuration for tests: (Each check rotates through every valid state, just use "Check Now" to change it. Though, don't forget to run graph TD;
A-->B;
B-->D;
C-->D;
D-->H;
F-->E;
E-->G;
G-->H;
A-.->F;
B-.->E;
B-.->C;
G-.->H;
subgraph GD [ redundancy group ]
G~~~D
end
|
I am aware that the filter may cause services to disappear because their host is unreachable. But this is not a false positive, as implicit dependencies dictate that services of unreachable hosts are in turn as well unreachable. So whether such a service disappears because its host is unreachable or itself is, makes no difference.