You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* The troubleshooting UI panel has been improved so you can now select and focus on a specific starting signal.
47
+
* There is more visibility into Korrel8r queries, with the option of selecting the depth.
48
+
* Users of {product-title} version 4.17+ can access the troubleshooting UI panel from the Application Launcher {launch}. Alternatively, on versions 4.16+, you can access it in the web console by clicking on **Observe** -> **Alerting**.
49
+
50
+
//
51
+
// For more information, see xref :../../observability/cluster_observability_operator/ui_plugins/troubleshooting-ui-plugin.adoc#troubleshooting-ui-plugin[troubleshooting UI plugin]
52
+
53
+
// COO-263
54
+
==== Distributed tracing UI plugin
55
+
56
+
* The distributed tracing UI plugin has been enhanced, with a Gantt chart now available for exploring traces.
57
+
//
58
+
// For more information, see xref :../../observability/cluster_observability_operator/ui_plugins/distributed-tracing-ui-plugin.adoc#distributed-tracing-ui-plugin[distributed tracing UI plugin]
* Previously, metrics were not available to normal users when accessed in the Developer perspective of the web console, by clicking on **Observe** -> **Logs**.
64
+
This release resolves the issue. (link:https://issues.redhat.com/browse/COO-288[*COO-288*])
65
+
66
+
* Previously, the troubleshooting UI plugin used the wrong filter for network observability.
67
+
This release resolves the issue. (link:https://issues.redhat.com/browse/COO-299[*COO-299*])
68
+
69
+
* Previously, the troubleshooting UI plugin generated an incorrect URL for pod label searches.
70
+
This release resolves the issue. (link:https://issues.redhat.com/browse/COO-298[*COO-298*])
71
+
72
+
* Previously, there was an authorization vulnerability in the Distributed tracing UI plugin.
73
+
This release resolves the issue and the Distributed tracing UI plugin has been hardened by using only multi-tenant `TempoStack` and `TempoMonolithic` instances going forward.
0 commit comments