Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-5250

[release-5.8] Loki Operator metrics are scraped more than once

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Hide
      Before this update, the configuration of the ServiceMonitor used by Loki Operator matched multiple Kubernetes services causing the metrics for Loki Operator to be picked up more than once. With this update, the ServiceMonitor's configuration has been changed to only match the dedicated metrics service.
      Show
      Before this update, the configuration of the ServiceMonitor used by Loki Operator matched multiple Kubernetes services causing the metrics for Loki Operator to be picked up more than once. With this update, the ServiceMonitor's configuration has been changed to only match the dedicated metrics service.
    • 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:

      1. Install Loki Operator with monitoring enabled
      2. 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.

            rojacob@redhat.com Robert Jacob
            rojacob@redhat.com Robert Jacob
            Kabir Bharti Kabir Bharti
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: