-
Bug
-
Resolution: Done-Errata
-
Major
-
Logging 5.9.0
-
False
-
None
-
False
-
NEW
-
ON_QA
-
-
Bug Fix
-
-
-
Log Storage - Sprint 250, Log Storage - Sprint 251
-
Moderate
Description of problem:
The ServiceMonitor used for the Loki Operator matches more than one service, which causes Prometheus to get more than one target for the Loki Operator. This results in duplicate metrics from the single operator instance.
Version-Release number of selected component (if applicable):
How reproducible:
Install Loki Operator to a cluster and enable "Operator recommended cluster monitoring on this Namespace" during installation, then look for the number of active targets in the namespace.
Steps to Reproduce:
- Install Loki Operator with monitoring enabled
- Query for targets: up{namespace="openshift-operators-redhat"}
Actual results:
Result should only show the Loki Operator once, but the query returns more than one series
Expected results:
Loki Operator should only show up as a single metrics target.
Additional info:
This has gone unnoticed for a while, but I am considering it a higher priority for the 5.9 release because we have added a new warning alert that will show up in a lot of customer clusters which would be complicated by the alert showing up multiple times.
- is cloned by
-
LOG-5250 [release-5.8] Loki Operator metrics are scraped more than once
- Closed
-
LOG-5251 [release-5.7] Loki Operator metrics are scraped more than once
- Closed
-
LOG-5252 [release-5.6] Loki Operator metrics are scraped more than once
- Closed
- links to
-
RHBA-2024:128809 Logging Subsystem 5.9.0 - Red Hat OpenShift