1장. Cluster Observability Operator release notes

The incident detection feature in the Cluster Observability Operator reaches General Availability (GA) status in this release for OpenShift Container Platform versions 4.19+. Incident detection simplifies observability by grouping related alerts into incidents. This helps reduce alert fatigue and allows you to focus on the root cause of a problem. With General Availability (GA) status, the incident detection feature is production-ready and fully supported for enterprise deployments. Users can enable incident detection through the monitoring UIPlugin resource by setting spec.monitoring.incidents.enabled: true.

For more information, see Incident detection

COO-1281

The incidents view in the monitoring UI plugin supports silenced alerts in this release. Silenced alerts display with a state of Silenced in the incident detection UI and appear in a lighter color in the timeline. This helps you to distinguish them from active alerts and to understand the complete state of your cluster observability signals.

COO-1280

The troubleshooting feature in the Cluster Observability Operator reaches General Availability (GA) status in this release for OpenShift Container Platform versions 4.19+ and is not supported in earlier versions. The troubleshooting UI plugin provides observability signal correlation, powered by the open source Korrel8r project. With the troubleshooting panel you can easily correlate metrics, logs, alerts, netflows, and additional observability signals and resources, across different data stores.

For more information, see Troubleshooting UI plugin

Before this update, OpenShift Container Platform 4.19 introduced changes to alert URL formatting where some URLs contained only console-internal numeric IDs without alert names. As a consequence, the korrel8r troubleshooting panel failed to process these URLs correctly and could not correlate alerts with related resources.

With this release, korrel8r correctly handles alert URLs from OpenShift Container Platform 4.19, including URLs that contain only numeric identifiers. As a result, the troubleshooting panel works correctly with all alert types on OpenShift Container Platform 4.19 clusters.

COO-1145

Before this update, when upgrading the Cluster Observability Operator from version 1.2.0 to 1.2.1 or later, the monitoring UIPlugin configuration was removed during the upgrade process. The UIPlugin spec became empty, showing only the plugin type while losing all configuration details such as RHACM integration settings, Perses dashboards, and incident management settings. As a consequence, users could not access monitoring dashboards and features after the upgrade, and the operator logged errors stating monitoring configuration can not be empty for plugin type Monitoring.

With this release, the Cluster Observability Operator correctly preserves monitoring UIPlugin configuration during upgrades. As a result, monitoring dashboards, RHACM integration, and incident management features remain available after operator upgrades without requiring manual reconfiguration.

COO-1051

Before this update, the UIPlugin controller did not update the custom resource status field in all reconciliation scenarios. The controller failed to update the status when reconciliation errors occurred, causing the status to report success even when configuration changes were not applied. As a consequence, users could not accurately determine the state of UIPlugin resources through the status field and had to check the generation field or operator logs to debug issues.

With this release, the Cluster Observability Operator correctly updates UIPlugin status in all reconciliation scenarios, including error conditions. As a result, users can rely on the UIPlugin status field to accurately reflect the current state of the resource and troubleshoot configuration issues more effectively.

COO-1055

Before this update, the distributed tracing UIPlugin in COO 1.2.2 did not properly handle double quotes in TraceQL query expressions. The query parser failed when attribute values contained double quotes, such as regular expression patterns in HTTP route attributes. As a consequence, users could not query traces with attributes containing double quotes, even when these values were selected from dropdown menus in the user interface.

With this release, the Red Hat OpenShift Cluster Observability Operator distributed tracing console plugin correctly processes TraceQL queries containing double quotes in attribute values. As a result, users can query traces with any attribute values, including those containing special characters like double quotes.

COO-1175

Before this update, the logging view plugin in COO 1.2.1 configured the Red Hat OpenShift Cluster Observability Operator console to proxy traffic to the korrel8r service even when the troubleshooting panel UIPlugin was not deployed. The console attempted to connect to a non-existent service, causing permission denied errors. As a consequence, users experienced transient "Missing permissions to get logs" error messages in the logging view, which resolved on their own after 30-60 seconds without user intervention.

With this release, the Cluster Observability Operator only configures the korrel8r proxy in the logging view plugin when the troubleshooting panel UIPlugin is deployed. As a result, users no longer encounter spurious permission errors when viewing logs without the troubleshooting panel.

COO-1253

Before this update, the distributed tracing console plugin search field did not support keyboard-only navigation. When users typed a filter value and pressed Enter to select it, the page reset to the tenant selection screen instead of applying the filter. As a consequence, keyboard-only users could not filter traces by service name or other attributes and were forced to use mouse-based selection.

With this release, the Red Hat OpenShift Cluster Observability Operator distributed tracing console plugin correctly handles the Enter key in search fields. As a result, users can apply trace filters using keyboard-only navigation, improving accessibility.

COO-1017

Before this update, the UIPlugin controller in COO 1.2.1 did not remove pods for disabled features when users updated the configuration. When users set perses.enabled: false or incidents.enabled: false in the UIPlugin specification, the associated pods (perses-0 and health-analyzer) continued to run. As a consequence, users could not disable Perses dashboards or incidents features, and the disabled components continued consuming cluster resources.

With this release, the Cluster Observability Operator correctly removes pods when features are disabled in the UIPlugin configuration. As a result, users can enable or disable Perses and incidents features by updating the UIPlugin specification, and the associated pods are created or removed accordingly.

COO-1054