Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-2192

Fix exposing metrics of the swatch-metrics

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • 2024-03-06 - API
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      When porting the swatch-metrics from a spring boot service to quarkus service, the metrics path changed from "/metrics" to "/q/metrics" and because of this, the metrics from this service are no longer visible in grafana/prometheus.

      For other Quarkus services, we have a ServiceMonitor resource that configures the path to use for the Quarkus services depending on the presence of the label "prometheus: quarkus".

      We tried to update the swatch metrics prometheus label from "rhsm" to "quarkus" here: https://github.com/RedHatInsights/rhsm-subscriptions/pull/2939, but we had to revert it because the deployment labels are inmutable (this might be an issue with the clowd deployments).

      Therefore, we need to quickly fix this issue since at the moment this service are not contributing to exposing the metrics into grafana.

      For the long term, this will be fixed at the clowder config source side: SWATCH-2091

      Acceptance Criteria

      • We should see the Swatch Metrics metrics into grafana. For example, the following metrics should be available:
      metrics_collection_timer_seconds_count{productTag="rhel-for-x86-els-payg",status="success"} 1.0
      metrics_collection_timer_seconds_sum{productTag="rhel-for-x86-els-payg",status="success"} 0.098850909
      metrics_collection_timer_seconds_max{productTag="rhel-for-x86-els-payg",status="success"} 0.098850909
      

            jcarvaja@redhat.com Jose Carvajal Hilario
            jcarvaja@redhat.com Jose Carvajal Hilario
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: