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

Allow OpenShift users to configure audit logs for prometheus-adapter

    XMLWordPrintable

Details

    • False
    • False
    • NEW
    • NEW
    • Undefined
    • Monitoring - Sprint 207, Monitoring - Sprint 208, Monitoring - Sprint 209, Monitoring - Sprint 210

    Description

      After investigating a complex Bugzilla involving many applications making queries to prometheus-adapter, we've noticed that we were lacking insights on the requests made to prometheus-adapter. To have such information for an aggregated API, the best would be to have audit logs for prometheus-adapter. This wasn't configurable before, but with https://github.com/kubernetes-sigs/custom-metrics-apiserver/pull/92, upstream users should now be able to configure it.

      Since this would greatly help in investigating prometheus-adapter Bugzilla in the future, it would be great if we allowed OpenShift users to configure the audit logs so that they could provide them to us.

      Note for the assignee: as of the time of the creation of this ticket, the upstream PR hasn't been merged in custom-metrics-apiserver and thus wasn't synced in prometheus-adapter. So we will have to wait a bit before starting looking into this ticket.

       

      DoD:

      • Allow OpenShift users to configure audit logs for prometheus-adapter
      • Integrate with must-gather
      • Document how to configure audit logs in the official OpenShift documentation
      • Upstream jsonnet patch that enables this feature through a configuration

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MON-1907 Add prometheus-adapter audit logs in CI

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is documented by

          Task - A task that needs to be done. RHDEVDOCS-3386 Document how to configure prometheus-adapter audit logs in OpenShift Monitoring

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          relates to

          Task - A task that needs to be done. MON-1787 Allow OpenShift users to configure query log file for Prometheus

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Task - A task that needs to be done. MON-2082 Allow OpenShift users to configure request logging for Thanos Querier query endpoint

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          GitHub openshift/must-gather#266: MON-1786: Enable collection of prometheus-adapter audit logs

          Activity

            People

              sthaha@redhat.com Sunil Thaha
              dgrisonn@redhat.com Damien Grisonnet
              Junqi Zhao Junqi Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: