OBSDOCS-1524 COO must-gather

Author: gabriel-rh

modules/coo-must-gather.adoc

@@ -0,0 +1,19 @@
+// Module included in the following assemblies:
+//
+// * observability/cluster_observability_operator/cluster-observability-operator-overview.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="coo-must-gather_{context}"]
+= Using the must-gather tool
+You can use the must-gather tool to collect information about the Cluster Observability Operator resources.
+
+.Procedure
+. Navigate to the directory where you want to store the must-gather data.
+. Run the following command to collect cluster-wide must-gather resources:
++
+[source,terminal]
+----
+$ oc adm must-gather
+ --image-stream=openshift/must-gather \
+ --image=quay.io/redhat-user-workloads/cluster-observabilit-tenant/cluster-observability-operator-container
+----

modules/gathering-data-specific-features.adoc

@@ -48,6 +48,9 @@ endif::openshift-rosa,openshift-dedicated[]
 |`quay.io/netobserv/must-gather`
 |Data collection for the Network Observability Operator.
 
+|`quay.io/redhat-user-workloads/cluster-observabilit-tenant/cluster-observability-operator-container`
+|Data collection for the Cluster Observability Operator.
+
 ifndef::openshift-rosa,openshift-dedicated[]
 |`registry.redhat.io/openshift4/ose-local-storage-mustgather-rhel9:v<installed_version_LSO>`
 |Data collection for Local Storage Operator.

observability/cluster_observability_operator/cluster-observability-operator-overview.adoc

@@ -22,6 +22,8 @@ Monitoring stacks deployed by the two Operators do not conflict. You can use a {
 
 include::modules/monitoring-understanding-the-cluster-observability-operator.adoc[leveloffset=+1]
 
+include::modules/coo-must-gather.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources