Uploaded image for project: 'OpenShift Storage'
  1. OpenShift Storage
  2. STOR-1289

Techdebt: move vSphere recording rules to storage operators



    • Techdebt: move vSphere recording rules to storage operators
    • 1
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 44
    • 44% 44%
    • XS


      Epic Goal*

      Currently, all vSphere related metrics that we send through telemetry have recording rules in cluster-monitoring-operator. These rules only stripe not interesting labels from existing metrics + calculate per-cluster metric value (instead of e.g. per operator value). They belong somewhere else, ideally to the components that emit them / their operators (vsphere-problem-detector, vmware-vsphere-csi-driver-operator, cluster-storage-operator).

      cluster-monitoring-operator should contain only the real telemetry config, i.e. 0000_50_cluster-monitoring-operator_04-config.yaml

      Why is this important? (mandatory)

      This reduces noise in cluster-monitoring-operator code repository.

      Scenarios (mandatory) 

      A cluster admin upgrades OCP 4.y to OCP 4.y+1 and does not see any difference:

      • The same metrics are collected by Prometheus
      • The same metrics are sent via telemetry

      However, as cluster-monitoring-operator maintainer, I don't see any vSphere Prometheus rules in cluster-monitoring-operator code.

      Dependencies (internal and external) (mandatory)


      Contributing Teams(and contacts) (mandatory) 

      Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

      • Development - 
      • Documentation -
      • QE - 
      • PX - 
      • Others -

      Done - Checklist (mandatory)

      The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

      • CI Testing -  Basic e2e automationTests are merged and completing successfully
      • Documentation - Content development is complete.
      • QE - Test scenarios are written and executed successfully.
      • Technical Enablement - Slides are complete (if requested by PLM)
      • Engineering Stories Merged
      • All associated work items with the Epic are closed
      • Epic status should be "Release Pending" 




            rhn-engineering-jsafrane Jan Safranek
            rhn-engineering-jsafrane Jan Safranek
            Chao Yang Chao Yang
            0 Vote for this issue
            2 Start watching this issue



              Time Tracking

                Original Estimate - 1 day
                Time Not Required
                Not Specified