Problem
A single node failure may cause several independent issues in different subsystems, such as Storage, Board, Scheme Board, and State Storage.
The current root-cause-first UI displays the same failed node for each issue, which looks like duplicated information.
Merging the issues is not a good solution: they may have different impact, details, status, and lifecycle, and combining them would make individual issues less meaningful.
UX question
How should the UI represent multiple independent issues sharing the same root cause?
The solution should:
- show the root cause only once;
- preserve separate issues and their details;
- clearly connect each issue to the shared root cause.
Screenshot
Problem
A single node failure may cause several independent issues in different subsystems, such as Storage, Board, Scheme Board, and State Storage.
The current root-cause-first UI displays the same failed node for each issue, which looks like duplicated information.
Merging the issues is not a good solution: they may have different impact, details, status, and lifecycle, and combining them would make individual issues less meaningful.
UX question
How should the UI represent multiple independent issues sharing the same root cause?
The solution should:
Screenshot