Loading...

XML

Word

Printable

Type: Task
Resolution: Done
Priority: Undefined
Fix Version/s: None
Affects Version/s: None
Component/s: cluster-monitoring-operator
Labels:
- groomed
- tc-approved

Blocked:
False
Ready:
False
Epic Link:
MON-880
Docs QE Status:
NEW
Feature Link:
OBSDA-3 - Allow non-admin users to configure individual notification settings
QE Status:
NEW
Market:

Sprint:
Monitoring - Sprint 211

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

As described in https://github.com/openshift/enhancements/blob/ba3dc219eecc7799f8216e1d0234fd846522e88f/enhancements/monitoring/multi-tenant-alerting.md#distinction-between-platform-and-user-alerts, cluster admins want to distinguish platform alerts from user alerts. For this purpose, CMO should provision an external label (openshift_io_alert_source="platform") on prometheus-k8s instances.

links to

openshift/cluster-monitoring-operator#1505: jsonnet: Add external labels to platform Prometheus

openshift/cluster-monitoring-operator#1508: WIP: Ensure we can identify the source of alerts from Platform Prometheus

Assignee:: Philip Gough

Reporter:: Simon Pasquier

QA Contact:: Junqi Zhao

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2021/12/01 11:02 AM

Updated:: 2022/03/24 11:29 AM

Resolved:: 2021/12/20 2:16 PM