Thanks to visit codestin.com
Credit goes to github.com

Skip to content

health check: severity levels #9754

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

Closed
Tracked by #8971
bpmct opened this issue Sep 18, 2023 · 1 comment · Fixed by #10817
Closed
Tracked by #8971

health check: severity levels #9754

bpmct opened this issue Sep 18, 2023 · 1 comment · Fixed by #10817
Assignees

Comments

@bpmct
Copy link
Member

bpmct commented Sep 18, 2023

There have been several cases where it would be nice to display a UI warning for a misconfiguration, but the severity is not so high that the message shows up on every screen. In this case, it would be great if errors had different severities and ones that cause a degraded deployment (broken SSH, no websockets, no webterminal)

Examples of low-severity things that should not show an undismissible banner warning, or any banner for that matter:

@mtojek
Copy link
Member

mtojek commented Nov 21, 2023

From #8966:

Perhaps we should have a severity level here depending on the number of unhealthy DERP regions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants