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
Add multiple Alerting Rules in PrometheusRule to always display the same value #9926
Labels
kind/bug
QA/dev-automation
Issues that engineers have written automation around so QA doesn't have look at this
Milestone
Comments
nwmac
added
the
automation-candidate
Candidate for being covered by automated tests
label
Mar 4, 2024
aalves08
added a commit
to aalves08/dashboard
that referenced
this issue
Apr 3, 2024
aalves08
added a commit
to aalves08/dashboard
that referenced
this issue
Apr 4, 2024
aalves08
added
QA/dev-automation
Issues that engineers have written automation around so QA doesn't have look at this
[zube]: QA Review
and removed
[zube]: To Triage
QA/manual-test
Indicates issue requires manually testing
automation-candidate
Candidate for being covered by automated tests
labels
Apr 10, 2024
github-actions
bot
added
[zube]: To Test
QA/manual-test
Indicates issue requires manually testing
automation-candidate
Candidate for being covered by automated tests
and removed
QA/dev-automation
Issues that engineers have written automation around so QA doesn't have look at this
[zube]: QA Review
labels
Apr 10, 2024
aalves08
removed
the
automation-candidate
Candidate for being covered by automated tests
label
Apr 10, 2024
nwmac
added
QA/dev-automation
Issues that engineers have written automation around so QA doesn't have look at this
and removed
[zube]: To Test
QA/manual-test
Indicates issue requires manually testing
labels
Apr 10, 2024
automated e2e tests added with this PR: #10745 |
e2e test seems sufficient to me. Moving this to Done cc: @izaac |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
QA/dev-automation
Issues that engineers have written automation around so QA doesn't have look at this
Setup
Describe the bug
When adding a second or more
Alerting Rules
to aPrometheusRule
, the newly addedAlerting Rules
are the same as the first oneTo Reproduce
PrometheusRule
and add multipleAlerting Rules
Result
All
Alerting Rules
are the same, and if you modify one of theAlerting Rules
, the other forms will also take effect.Screenshots
Additional context
The text was updated successfully, but these errors were encountered: