Traces
Traces provide the familiar Jaeger flame graph view of the distributed trace, showing the performance of the service and its operations being called in sequence. From the Traces view, you can:
View the overall performance of all requests made to the services and their operations.
Click on the service operation (span) to view more details on Tags, Process, and Logs associated with the service.
Visualize whether there is high latency or any problematic errors in the path or services.
Red color highlighted on a service indicates anomalies detected in a service operation.
You can visualize the slow traces caused by problematic operations and services.
Spans and traces
A span represents a single unit of work within a service (e.g., an HTTP route or database query).
A trace connects multiple spans sharing a common trace context across services to represent an entire transaction lifecycle.
Tracepaths
Instead of analyzing millions of individual traces in isolation, CO automatically groups repeated transactions following the same service sequence into a tracepath. A Tracepath is named after the root (entry) service and operation: <cluster>@<namespace>^<root-service>#<HTTP-method> <path>, for example: co-dev-02@checkout^web-server#POST /api/order.
Tracepath anomaly and alert integration
When operations within a tracepath degrade, Container Observability detects the breach dynamically, associates the slow trace IDs (affectedTraceIds), and triggers consolidated Tracepath RCA Alerts rather than flooding individual span alerts. To view the Tracepath RCA alerts report in the Global View, see Tracepath RCA alerts.