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

Allow user to customize the KSM metric-denylist

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • None
    • None
    • Customize KSM metric-denylist
    • False
    • None
    • False
    • Not Selected
    • NEW
    • To Do
    • MON-3154CMO user customizations
    • NEW
    • 0% To Do, 0% In Progress, 100% Done

      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.

      Acceptance criteria:

      • A solution that enables users to override the already existing (default) denylist.

              prasriva@redhat.com Pranshu Srivastava
              rh-ee-rfloren Roger Florén
              Tai Gao Tai Gao
              Votes:
              2 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: