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

Clean-up New Relic related policies in JSM #936

Open

1 of 6 tasks

robrap opened this issue Feb 15, 2025 · 0 comments

Contributor

robrap commented Feb 15, 2025

@jristau1984 found these JSM policies (formerly in OpsGenie).

Here is what is needed:

Add arch-bom tag to all Arch-BOM alerts
- This is not about NR, and should remain in place.
Cap edge priority at P3
- Repurpose this policy to ensure that DD edge alerts can't be P1 or P2.
Make PN Newrelic Alerts Priority N
- Verify that DD alerts are already sent with the correct priority.
- Remove these policies.

robrap added this to Arch-BOM

robrap converted this from a draft issue

robrap moved this to Backlog in Arch-BOM

robrap changed the title ~~Clean-up on-call New Relic config~~ Clean-up New Relic related policies in JSM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment