Merge pull request #94262 from gabriel-rh/OBSDOCS-1974

OBSDOCS-1974 COO 1.2 release

Author: gabriel-rh

modules/coo-incident-detection-using.adoc

@@ -55,5 +55,4 @@ image::coo-incident-alerts-components-expanded.png[Incidents expanded components
 
 * Depending on the order of the timeline bars, the tooltip might overlap and hide the underlying bar. You can still click the bar and select the incident or alert.
 
-* The Silence Alert button in the **Incidents** -> **Component** section does not pre-populate the fields and is not usable. As a workaround, you can use the same menu and the Silence Alert button in the **Alerting** section instead.
 ====

observability/cluster_observability_operator/cluster-observability-operator-release-notes.adoc

@@ -24,6 +24,45 @@ The following table provides information about which features are available depe
 | 1.1+          | 4.18+              | ✔                     | ✔         | ✔                     | ✔          | ✔
 |===
 
+[id="cluster-observability-operator-release-notes-1-2_{context}"]
+== {coo-full} 1.2
+
+// Back fill advisory when it is created by Konflux
+// The following advisory is available for {coo-full} 1.2:
+//
+// * link:https://access.redhat.com/errata/RHSA-2025:????[RHEA-2025:??? {coo-full} 1.2]
+
+[id="cluster-observability-operator-1-2-new-features-enhancements_{context}"]
+=== New features and enhancements
+
+* The logging UI plugin now supports the OTEL format, in addition to the previously supported ViaQ scheme. (link:https://issues.redhat.com/browse/COO-816[*COO-816*])
+
+* Accelerators Perses dashboards are deployed by default when you install the monitoring UI plugin. (link:https://issues.redhat.com/browse/COO-942[*COO-942*]) 
+
+* Multiple results per graph node are now displayed for Korrel8r. (link:https://issues.redhat.com/browse/COO-785[*COO-785*]) 
+
+* Direct navigation to individual incident detail is now supported in the incident detection panel, and this enables the incidents overview functionality in {rh-rhacm-first} 2.14. (link:https://issues.redhat.com/browse/COO-977[*COO-977*], link:https://issues.redhat.com/browse/ACM-18751[*ACM-18751*])
+
+* Advanced filters have been added to the tracing view. (link:https://issues.redhat.com/browse/COO-979[*COO-979*]) 
+
+* The status of the distributed tracing UI plugin is now General Availability (GA), supporting Patternfly 4, 5 and 6. (link:https://issues.redhat.com/browse/COO-873[*COO-873*]) 
+
+[id="cluster-observability-operator-1-2-bug-fixes_{context}"]
+=== Bug fixes
+
+* Previously, LokiStack was a prerequisite for installing the logging UI plugin. With this release, you can install the logging UI plugin without LokiStack. (link:https://issues.redhat.com/browse/COO-760[*COO-760*])
+
+* Previously, the *Silence Alert* button in the **Incidents** -> **Component** section did not pre-populate the fields and was not usable. This release resolves the issue. (link:https://issues.redhat.com/browse/COO-970[*COO-970*])
+
+
+[id="cluster-observability-operator-1-2-known-issues_{context}"]
+=== Known issues
+
+These are the known issues in {coo-full} 1.2.0:
+
+* When upgrading from {coo-short} 1.1.1 to {coo-short} 1.2, the Perses dashboard is not correctly reconciled, and this requires the monitoring UI plugin to be reinstalled. (link:https://issues.redhat.com/browse/COO-978[*COO-978*])
+
+
 [id="cluster-observability-operator-release-notes-1-1-1_{context}"]
 == {coo-full} 1.1.1
 
@@ -60,7 +99,7 @@ The following table provides information about which features are available depe
 
 
 [id="cluster-observability-operator-1-1-known-issues_{context}"]
-== Known issues
+=== Known issues
 
 These are the known issues in {coo-full} 1.1.0:
 

observability/cluster_observability_operator/ui_plugins/distributed-tracing-ui-plugin.adoc

@@ -6,9 +6,6 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-:FeatureName: The {coo-full} distributed tracing UI plugin
-include::snippets/technology-preview.adoc[leveloffset=+2]
-
 The distributed tracing UI plugin adds tracing-related features to the Administrator perspective of the OpenShift web console at **Observe** → **Traces**. You can follow requests through the front end and into the backend of microservices, helping you identify code errors and performance bottlenecks in distributed systems. 
 
 include::modules/coo-distributed-tracing-ui-plugin-install.adoc[leveloffset=+1]