Trace Paths
To provide a real-time view of the state of all traces being collected, Container Observability discovers the common business flows, called Tracepaths, traversed by the collected traces. The Tracepath provides users with an aggregate view of details of request rates, response times, and errors of all traces using that flow.
By auto discovering the Tracepaths and calculating their SLOs and metrics, Container Observability makes traces useful for the Operations and SRE teams. This is a unique feature of Container Observability.
Note
Note:
To view the Trace Map, see Viewing Maps in Container Observability.
Alerts are created when traces represent anomalies. For more information, see Tracepath-based alert.
The Tracepath summary view includes the following tabs:
Highlights:
The Highlights tab summarizes the top Tracepaths by services and operations within the services. Using such summaries, a user can find traces of interest within a specific time interval for a given Tracepath that contains specific services or service/operations and helps users to detect if a trace is showing performance problems down to the service/operation level exhibiting any problems.
You can analyze the following from Highlights:
The number of requests by volume from the root span into the Tracepath.
Response and Request time made per Tracepath and per Service basis.
Errors occur during the request and response time of traffic flow between the services and their operations.
Enables detecting problems or anomalous traces based on high latency or errors.
All Tracepaths: Lists overall paths and services where the traffic follows from all services and their number of operations with its request count, latency, and error details.
All Services: Lists overall services with request count, average or max latency data, and errors if any.
Related topics: