Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-11478

Investigate Monitoring integration with Cluster Observability Operator (COO)

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Sail Operator
    • None

      This Spike is about the monitoring integration using the Cluster Observability Operator (COO). Need to follow OpenShift documentation and have an understanding of the differences between  the Cluster Monitoring Operator (CMO) and the Cluster Observability Operator (COO)

      https://docs.redhat.com/en/documentation/red_hat_openshift_cluster_observability_operator/1-latest/html/about_red_hat_openshift_cluster_observability_operator/cluster-observability-operator-overview-1#coo-versus-default-ocp-monitoring_cluster_observability_operator_overview

      Evaluate the use case(s) of using COO with Service Mesh 3. Try the ServiceMonitor and PodMonitor custom resources with COO and check if there is anything missing for that integration.

       

              Unassigned Unassigned
              yuaxu@redhat.com Yuanlin Xu
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: