Uploaded image for project: 'Observability Documentation'
  1. Observability Documentation
  2. OBSDOCS-1504

Explictiltly point out that COO objects use a different API

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • COO 0.4.0
    • COO
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      The docs curerntly state: 

       
      The COO components function independently of the default in-cluster monitoring stack, which is deployed and managed by the Cluster Monitoring Operator (CMO). Monitoring stacks deployed by the two Operators do not conflict.
      

      how is this achived? 
      how can I reuse objects such as serviceMonitors and PrometheusRule objects previously configured against the core or user workload instances?

      • by changing the API from `servicemonitors.monitoring.coreos` -> `servicemonitors.monitoring.rhobs` 

              rhn-support-gmcgoldr Gabriel McGoldrick
              rhn-support-nigsmith Nigel Smith
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: