Loading...

XML

Word

Printable

Type: Story
Resolution: Done
Priority: Major
Fix Version/s: Consoledot CY25Q1
Affects Version/s: None
Component/s: Notifications
Labels:
- platform-integrations

Story Points:
3
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
BZ requires_doc_text:
Unset
Regression:
None
BZ Keywords:
- Unset
Intelligence Requested:
Market:

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

The current kafka_consumergroup_group_lag metrics are being replaced, and need to be updated in the Notifications Grafana dashboards.

Clarification in this Slack thread

is caused by

RHCLOUD-37101 Move from kafka-lag-exporter to AWS MSK lag metrics

Code Review

is cloned by

RHCLOUD-37401 [Cloud-Connector] Replace Kafka lag metrics with AWS MSK metrics in Grafana

Code Review

RHCLOUD-37402 [Playbook Dispatcher] Replace Kafka lag metrics with AWS MSK metrics in Grafana

Code Review

RHCLOUD-37422 [Sources] Replace Kafka lag metrics with AWS MSK metrics in Grafana

Code Review

RHCLOUD-37423 [payload-tracker] Replace Kafka lag metrics with AWS MSK metrics in Grafana

Code Review

mentioned on

Merge request - Add SumOffsetLag metric to CRC CloudWatch exporter

Merge request - Notifications: Upgrading prod

Merge request - Notifications: Upgrading stage

Merge request - Notifications: Upgrading stage

(4 mentioned on)

Assignee:: Jessica Rodriguez

Reporter:: Jessica Rodriguez

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2025/01/17 6:13 PM

Updated:: 2025/01/30 8:28 AM

Resolved:: 2025/01/24 1:54 PM