Uploaded image for project: 'OpenShift Dev Console'
  1. OpenShift Dev Console
  2. ODC-6473

Per-namespace monitoring dashboards

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Obsolete
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • Per-namespace monitoring dashboards
    • False
    • False
    • To Do
    • 0
    • 0% To Do, 0% In Progress, 100% Done
    • Not Supported

      1. Proposed title of this feature request
      Support custom Grafana dashboards for specific namespaces in Developer perspective of the console

       

      2. What is the nature and description of the request?
      Currently, the console UI supports displaying custom Grafana dashboards within the developer perspective by adding the label 

       console.openshift.io/odc-dashboard: true 

      to the configmap containing the dashboard. However, per my understanding the configmap is currently visible across all namespaces by default, and data displayed is filtered based on which namespace is selected in the drop down. This does not offer a lot of flexibility for grafana dashboards that may be intended to target specific namespaces and workloads within those namespaces. The idea behind this RFE is to support the ability to choose which namespace/set of namespaces a custom dashboard should be displayed under within the developer perspective of the console 

       

      3. Why does the customer need this? (List the business requirements here)
      One of the configuration setups that is common for users of OpenShift GitOps is for cluster admin teams to set up cluster-config Argo CD instances (that work across all namespaces), and for developer teams (without cluster-wide privileges or access to admin perspective of the console) to own certain namespaces on the cluster and operate their own namespace scoped instances of Argo CD to control their workloads within those namespaces. 

      We believe it would be of value for developer teams to be able to view a custom Grafana dashboard (in the developer perspective of the console) that visualizes metrics generated specifically by the argocd instance and workloads within their own namespace if desired. This would allow a certain degree of independence to the dev teams as they would not have to rely on cluster admins as heavily and would be able to monitor their own workioads to diagnose performance issues themselves. 

      Support for allowing custom dashboards to be visible only on specific namespaces would bring 2 significant advantages:
      1) Only teams that wish to view the dashboard would have the option of enabling the dashboard for their namespace, teams that don't, won't be shown the dashboard 
      2) It would provide us with the flexibility to eventually allow individual dev teams to create their own dashboards with metrics relevant to them and view them in their namespaces, rather than having to rely on an opinionated dashboard consisting of the same generic metrics for all teams

       

      4. How would you like to achieve this?
      One potential idea could be the introduction of a new label along the lines of 

      console.openshift.io/dashboard-namespace: <my-namespace> 

      Which would make those dashboards, which are labelled accordingly, visible in "my-namespace" only. 

      Epic Exploration

      Miro board

          1.
          Docs Tracker Sub-task Closed Undefined Unassigned
          2.
          QE Tracker Sub-task Closed Undefined Unassigned
          3.
          TE Tracker Sub-task Closed Undefined Unassigned

              Unassigned Unassigned
              rh-ee-ssadeghi Siamak Sadeghianfar
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: