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.

Sign up for GitHub

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

Jump to bottom

Implement alerts for high failure counts in critical services #17724

Open
melinath opened this issue Mar 28, 2024 · 1 comment
Open

Implement alerts for high failure counts in critical services #17724

melinath opened this issue Mar 28, 2024 · 1 comment
Labels
fixit-technical-debt nightly-teamcity Issues related to nightlies and/or TeamCity in general size/m technical-debt
Milestone
Goals

Comments

@melinath
Copy link
Collaborator

What kind of contribution is this issue about?

Other (specify in details)

Details

In addition to alerting on high overall failures in nightly builds, we may want to alert if there are high failures in specific services that we consider "critical".

References

No response
@melinath melinath added technical-debt nightly-teamcity Issues related to nightlies and/or TeamCity in general fixit-technical-debt labels Mar 28, 2024
@rileykarson
Copy link
Collaborator

I don't think we have a definition of critical services.

@rileykarson rileykarson added this to the Goals milestone Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
fixit-technical-debt nightly-teamcity Issues related to nightlies and/or TeamCity in general size/m technical-debt
Projects
None yet
Milestone
Goals
Development

No branches or pull requests
2 participants
@melinath @rileykarson