Uploaded image for project: 'OpenShift Monitoring'
  1. OpenShift Monitoring
  2. MON-3377

Support sendExemplars via UWM remote write

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • openshift-4.15
    • None
    • None
    • Store and send exemplars
    • False
    • None
    • False
    • Not Selected
    • NEW
    • To Do
    • MON-3154CMO user customizations
    • NEW
    • 100
    • 100% 100%
    • 0

      1. Proposed title of this feature request
      2. What is the nature and description of the request? 
        • Customers want to use exemplar-storage for openshift-user-workload-monitoring
        • However "PrometheusRestrictedConfig" doesn't support the option in the Prometheus spec, unlike Prometheus API for openshift-monitoring
        • PrometheusRestrictedConfig needs to support the configuration below for enabling sendExemplars
          • .spec.remoteWrite[].sendExemplars
          • .spec.enableFeatures
      3. Why does the customer need this? (List the business requirements here 
        • Customers want to make monitoring for user-defined projects because openshift-monitoring is not flexible to customizing for monitoring the user's namespace services.
        • They need to enable the exemplar-storage function to implement the user-workload-monitoring
      4. List any affected packages or components.
        • openshift-user-workload-monitoring
        • openshift-monitoring
      5. References
        openshift-monitoring prometheusK8s configuration

         .spec.remoteWrite[].sendExemplars

        • Enables sending of exemplars over remote write. Note that exemplar-storage itself must be enabled using the enableFeature option for exemplars to be scraped in the first place. Only valid in Prometheus versions 2.27.0 and newer.

        .spec.enableFeatures

        • Enable access to Prometheus disabled features. By default, no features are enabled. Enabling disabled features is entirely - outside the scope of what the maintainers will support and by doing so, you accept that this behaviour may break at any time without notice. For more information see https://prometheus.io/docs/prometheus/latest/disabled_features/

        [1]Prometheus [monitoring.coreos.com/v1]
        https://docs.openshift.com/container-platform/4.13/rest_api/monitoring_apis/prometheus-monitoring-coreos-com-v1.html

         However "PrometheusRestrictedConfig" doesn't support both options.

        openshift-user-workload-monitoring prometheus configuration

        [2]PrometheusRestrictedConfig

        https://docs.openshift.com/container-platform/4.13/monitoring/config-map-reference-for-the-cluster-monitoring-operator.html#prometheusrestrictedconfig*

            prasriva@redhat.com Pranshu Srivastava
            rhn-support-hyoskim Sophia Hyosun Kim
            Junqi Zhao Junqi Zhao
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: