OBSDOCS-2548 COO 1.3 GA Release Notes #101333
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
openshift-ci
bot
added
the
size/M
|
🤖 Mon Nov 10 18:04:39 - Prow CI generated the docs preview: |
gabriel-rh
force-pushed
the
OBSDOCS-2548
branch
5 times, most recently
from
d638bac to
0ec6b8a
Compare
| link:https://issues.redhat.com/browse/COO-1055[COO-1055] | ||
|
|
||
| Distributed tracing `UIPlugin` handles double quotes in TraceQL queries:: | ||
| Before this update, the distributed tracing `UIPlugin` did not properly handle double quotes in TraceQL query expressions. The query parser failed when attribute values contained double quotes, such as regex 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. |
Collaborator
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{DTShortName}' rather than the plain text product term 'distributed tracing', unless your use case is an exception.
| link:https://issues.redhat.com/browse/COO-1055[COO-1055] | ||
|
|
||
| Distributed tracing `UIPlugin` handles double quotes in TraceQL queries:: | ||
| Before this update, the distributed tracing `UIPlugin` did not properly handle double quotes in TraceQL query expressions. The query parser failed when attribute values contained double quotes, such as regex 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. |
Collaborator
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'regular expression' rather than 'regex'. For more information, see RedHat.TermsErrors.
| Distributed tracing `UIPlugin` handles double quotes in TraceQL queries:: | ||
| Before this update, the distributed tracing `UIPlugin` did not properly handle double quotes in TraceQL query expressions. The query parser failed when attribute values contained double quotes, such as regex 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 {product-title} 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. |
Collaborator
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{DTShortName}' rather than the plain text product term 'distributed tracing', unless your use case is an exception.
gabriel-rh
force-pushed
the
OBSDOCS-2548
branch
from
0ec6b8a to
9b012db
Compare
| link:https://issues.redhat.com/browse/COO-1055[COO-1055] | ||
|
|
||
| Distributed tracing `UIPlugin` handles double quotes in TraceQL queries:: | ||
| 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 regex 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. |
Collaborator
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{DTShortName}' rather than the plain text product term 'distributed tracing', unless your use case is an exception.
| link:https://issues.redhat.com/browse/COO-1055[COO-1055] | ||
|
|
||
| Distributed tracing `UIPlugin` handles double quotes in TraceQL queries:: | ||
| 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 regex 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. |
Collaborator
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'regular expression' rather than 'regex'. For more information, see RedHat.TermsErrors.
gabriel-rh
force-pushed
the
OBSDOCS-2548
branch
from
9b012db to
ac3886b
Compare
| link:https://issues.redhat.com/browse/COO-1253[COO-1253] | ||
|
|
||
| Distributed tracing search field supports keyboard navigation:: | ||
| 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. |
Collaborator
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{DTShortName}' rather than the plain text product term 'distributed tracing', unless your use case is an exception.
| Distributed tracing search field supports keyboard navigation:: | ||
| 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 {product-title} 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. |
Collaborator
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{DTShortName}' rather than the plain text product term 'distributed tracing', unless your use case is an exception.
gabriel-rh
force-pushed
the
OBSDOCS-2548
branch
2 times, most recently
from
0d4bb7f to
0cde56e
Compare
openshift-ci
bot
added
size/L
gabriel-rh
force-pushed
the
OBSDOCS-2548
branch
2 times, most recently
from
bd526bc to
a5599e2
Compare
falox
suggested changes
Nov 4, 2025
| === New features and enhancements | ||
|
|
||
| Incident detection feature reaches General Availability:: | ||
| The incident detection feature in the {coo-full} reaches General Availability (GA) status in this release. The incident detection feature automatically analyzes cluster health by correlating metrics, logs, and alerts to identify potential issues before they impact workloads. The health analyzer examines patterns across observability signals to detect anomalies, resource constraints, and configuration problems. 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`. |
There was a problem hiding this comment.
This part is not accurate
The incident detection feature automatically analyzes cluster health by correlating metrics, logs, and alerts to identify potential issues before they impact workloads. The health analyzer examines patterns across observability signals to detect anomalies, resource constraints, and configuration problems.
I would remove it. If you want a short description you can take inspiration from https://docs.redhat.com/en/documentation/red_hat_openshift_cluster_observability_operator/1-latest/html/ui_plugins_for_red_hat_openshift_cluster_observability_operator/monitoring-ui-plugin#coo-incident-detection-using_monitoring-ui-plugin, or these
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.
Incident detection groups related alerts into incidents, helping you identify root causes instead of getting overwhelmed by individual alerts.
| link:https://issues.redhat.com/browse/COO-1281[COO-1281] | ||
|
|
||
|
|
||
| Troubleshooting panel supports silenced alerts:: |
There was a problem hiding this comment.
This is not Troubleshooting panel but Incident detection UI, part of the monitoring plugin.
|
|
||
|
|
||
| Troubleshooting panel supports silenced alerts:: | ||
| The troubleshooting panel in the {coo-full} supports silenced alerts in this release. The korrel8r correlation engine recognizes alerts that have been silenced in Alertmanager and includes them in correlation analysis while indicating their silenced status. Users can view silenced alerts in the troubleshooting panel alongside active alerts, enabling comprehensive incident investigation even during maintenance windows or when alerts are temporarily suppressed. 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 firing alerts and to understand the complete state of your cluster observability signals. |
There was a problem hiding this comment.
It's not Korrel8r but incident detection UI. I would simply remove
The korrel8r correlation engine recognizes alerts that have been silenced in Alertmanager and includes them in correlation analysis while indicating their silenced status. Users can view silenced alerts in the troubleshooting panel alongside active alerts, enabling comprehensive incident investigation even during maintenance windows or when alerts are temporarily suppressed.
a5599e2 to
222da3c
Compare
falox
suggested changes
Nov 4, 2025
| === New features and enhancements | ||
|
|
||
| Incident detection feature reaches General Availability:: | ||
| The incident detection feature in the {coo-full} reaches General Availability (GA) status in this release. 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. Incident detection groups related alerts into incidents, helping you identify root causes instead of getting overwhelmed by individual alerts. 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`. |
There was a problem hiding this comment.
Let's remove the repetition
Suggested change
| The incident detection feature in the {coo-full} reaches General Availability (GA) status in this release. 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. Incident detection groups related alerts into incidents, helping you identify root causes instead of getting overwhelmed by individual alerts. 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`. | |
| The incident detection feature in the {coo-full} reaches General Availability (GA) status in this release. 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`. |
|
|
||
|
|
||
| Incidents view supports silenced alerts:: | ||
| 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 firing alerts and to understand the complete state of your cluster observability signals. |
There was a problem hiding this comment.
Suggested change
| 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 firing alerts and to understand the complete state of your cluster observability signals. | |
| 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. |
gabriel-rh
force-pushed
the
OBSDOCS-2548
branch
4 times, most recently
from
e94fc3c to
cf57bf3
Compare
gabriel-rh
force-pushed
the
OBSDOCS-2548
branch
from
cf57bf3 to
f46bd88
Compare
|
@gabriel-rh: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version(s):
standalone-coo-docs-1-latest
Issue:
OBSDOCS-2548
Link to docs preview:
QE review:
Additional information: