-
Task
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
The project that we use for our Kafka lag metrics has been archived and is currently unmaintained. On the plus side, AWS/MSK/Cloudwatch now has full lag metrics included. With this we can move our lag metrics over to the Cloudwatch Monitor and shut down the kafka-lag-monitor deployment.
This will need to be done with app-team coordination as it will affect many of the different app's alerts that rely on lag. Currently these alerts will be targeting crcs/crcp prometheus, and we'll need to move them over to appsres/appsrep prometheus and enable the lag metrics for our MSK cluster.
- causes
-
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
-
RHCLOUD-37376 [Notifications] Replace Kafka lag metrics with AWS MSK metrics in Grafana
- Release Pending
- mentioned on