Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-2141

Allow user to customize the metric-denylist for kube-state-metrics

XMLWordPrintable

    • False
    • False

      Prometheus in 4.7 and 4.8 has the following Prometheus kube metrics in the metric deny list making them unable to reach these metrics. As described in this KCS https://access.redhat.com/solutions/6232571

      • --metric-denylist=kube_secret_labels
      • --metric-denylist=
        kube_*_created,
        kube_*_metadata_resource_version,
        kube_replicaset_metadata_generation,
        kube_replicaset_status_observed_generation,
        kube_pod_restart_policy,
        kube_pod_init_container_status_terminated,
        kube_pod_init_container_status_running,
        kube_pod_container_status_terminated,
        kube_pod_container_status_running,
        kube_pod_completion_time,
        kube_pod_status_scheduled

      Customer is unhappy with this as they use many custom metrics. Customer is asking if we can make it so the Cu can pick and choose which metrics they want to add to the deny list.

            rh-ee-rfloren Roger Florén
            rhn-support-cruhm Courtney Ruhm
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: