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

Feature request: support for dynamically determining responders in opsgenie configuration #1987

Closed
hrancic opened this issue Aug 2, 2019 · 7 comments

Comments

@hrancic
Copy link

hrancic commented Aug 2, 2019

Alertmanager v0.18.0 moved from team field to responders for alert routing in opsgenie.

Having team field was useful for an use case where teams were determined dynamically after the alert fired, but before the alert was sent to opsgenie. If the list of teams responsible for the alert is not know before the alert is created, responders approach is not useful.

Something along the lines of the following solution would be much appreciated:


#names contain comma separated list of teams

responders:
 - names: <tmpl_string>
   type: teams
@hrancic hrancic changed the title Feature request: dynamically determine responders in opsgenie configuration Feature request: support for dynamically determining responders in opsgenie configuration Aug 2, 2019
@iobestar
Copy link

any updates?

@anandsinghkunwar
Copy link

@simonpasquier This seems like a very fair usecase/request and it was possible to do it before the migration. We've been using the previous alertmanager for the same reason, it'd be nice if we could get the same featureset in the newer version as well.

@simonpasquier
Copy link
Member

I agree but I'm not sure yet how it should translate in the configuration file. Splitting unconditionally on commas seems a bit rough.

@MarkoRelic
Copy link

Any updates?

@s3kkt
Copy link

s3kkt commented Mar 22, 2021

We needs this feature too.
It will be good to determine responders list when alert is created.

@MarkoRelic
Copy link

Can we expect this to be implemented?

@multani
Copy link
Contributor

multani commented Jan 6, 2023

Is there anything missing from #2685 that prevents this issue from being closed?

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

No branches or pull requests

7 participants