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

Configurable alert routing based on custom rules #153

Open
stehessel opened this issue Nov 22, 2022 · 2 comments
Open

Configurable alert routing based on custom rules #153

stehessel opened this issue Nov 22, 2022 · 2 comments

Comments

@stehessel
Copy link

stehessel commented Nov 22, 2022

Status Quo

The routing of alerts to different receivers is based on hard-coded severity rules. For example, strictly critical alerts are routed to PagerDuty (see https://github.com/redhat-developer/observability-operator/blob/main/controllers/reconcilers/configuration/alertmanager.go#L190). Customized routing rules based on other labels or label values are not supported.

Proposal

Receivers are freely configurable by their Alertmanager route CR. In particular, the receiver matching supports configurable labels and label values.

@stehessel stehessel changed the title Configurable alert routing based on custom labels Configurable alert routing based on custom rules Nov 22, 2022
@vmanley
Copy link
Collaborator

vmanley commented Jan 25, 2023

Hi @stehessel sorry about delay in replying and thanks for raising issue. This does seem like a worthy change for the Operator. However I'm not sure we have scope to include this feature at the moment. I can create a task and see if we can work on this in future sprint

@stehessel
Copy link
Author

Thank you @vmanley I would appreciate it.

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

No branches or pull requests

2 participants