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

Support for differentiating multiple clusters #20

Open
gorantornqvist opened this issue Nov 4, 2021 · 1 comment
Open

Support for differentiating multiple clusters #20

gorantornqvist opened this issue Nov 4, 2021 · 1 comment
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@gorantornqvist
Copy link

Motivation

It appears to be only possible to specify one channel for alerts but we have 3 different clusters so we would like to send messages to different channels.
Alternatively if only one channel has to be used , there is no way to see from which cluster an alert comes from, example:

Default
Status
:fire: FIRING :fire:

summary	description
Job failed to complete.

Job openshift-logging/curator-1625119680 failed to complete. Removing failed job after investigation should clear this alert.

severity	alertname
warning

KubeJobFailed

condition	container
true

kube-rbac-proxy-main

namespace	prometheus
openshift-logging

openshift-monitoring/k8s

service	endpoint
kube-state-metrics

https-main

job	job_name
kube-state-metrics

curator-1625119680

Start At
2 days 3 hours 31 minutes 33 seconds 61 milliseconds 452 microseconds

Ended At
292 years 24 weeks 3 days 23 hours 47 minutes 16 seconds 854 milliseconds 775 microseconds
@gorantornqvist
Copy link
Author

A quick workaround was to change receiver from Default to ClusterName_Default ...

@cpanato cpanato added bug Something isn't working help wanted Extra attention is needed labels Nov 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants