We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This should be fairly straightforward when we implement: #1259 We can generate metrics based on the the test run results and alert based on that.
I'm guessing Teams might want at least Slack notifications if tests start to fail too often.
Another use case I see is after we test this one: #1160 We could auto-magically create alerts if the SLOs start to burn unexpectedly.
No response
The text was updated successfully, but these errors were encountered:
monteiro-renato
No branches or pull requests
Description
This should be fairly straightforward when we implement: #1259
We can generate metrics based on the the test run results and alert based on that.
I'm guessing Teams might want at least Slack notifications if tests start to fail too often.
Another use case I see is after we test this one: #1160
We could auto-magically create alerts if the SLOs start to burn unexpectedly.
Additional Information
No response
The text was updated successfully, but these errors were encountered: