-
Notifications
You must be signed in to change notification settings - Fork 81
Add two server failure alert #7120
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
Conversation
|
Merging this PR will trigger the following deployment actions. Support deployments
Staging deployments
Production deployments
|
| makeServerStartupFailureAlert( | ||
| 'Outage alert: Server Startup failed: cluster %s hub:{{ $labels.namespace }}' % [cluster_name], | ||
| 'A server failed to start: cluster %s hub:{{ $labels.namespace }}' % [cluster_name], | ||
| 'same day action needed' |
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.
Let's reduce this to 'same week'?
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.
Makes sense, ty! I'll tackle this as part of #7022 as I feel like the whole priorities structure needs a bit of a cleanup.
Right now this is a P2 and we should document that the expectation for this alert should be: if I can start a server, mark it as resolved.
Fixes #7021