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.

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 optional escalation policy to aws account and cluster #455

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

maorfr
Copy link
Contributor

@maorfr maorfr commented May 30, 2023

with an escalation policy referenced from an aws account or a cluster, we can use dynamically generated per-resource alerts that will alert the tenant instead of AppSRE.

@patjlm
Copy link
Contributor

patjlm commented May 30, 2023

Don't we have escalation policy from namespace->app already? Which scenario would require account/cluster link without namespace?

@maorfr
Copy link
Contributor Author

maorfr commented Aug 15, 2023

the scenario is someone looking for a cluster owner (that is not us) and not for a service owner.

@geoberle
Copy link
Contributor

geoberle commented Oct 4, 2023

i like this a lot, again a nice option to reduce alerts on us and hand them to the owners of clusters and accounts

@rporres
Copy link
Contributor

rporres commented Oct 4, 2023

I see the scenario of defining a cluster/account owner and I like the idea. I honestly don't see how this can be used to route catch-all alerts to tenants since that involve being able to associate alerts labels to apps (which is something I've been wanting to do for a while, but other stuff keeps coming).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants