The TRACES EXPLORER page typically provides a summary or aggregated view of traces within a system or application. Traces refer to a sequence of recorded events or transactions that occur during the execution of a service.
The TRACES EXPLORER page is designed to offer a high-level perspective on the performance, behavior, and interactions captured in the traces. It may include key metrics such as:
- Latency: The time it takes for a request to be processed from initiation to completion.
- Error Rates: The count of traced transactions that resulted in errors or exceptions.
- Spans Count: The span count refers to the number of individual spans recorded within a trace.
- Service Count: The service count refers to the number of distinct services or that are involved in the processing of a distributed trace.
To view the details:
Navigate to Infrastructure > Traces.The traces page is displayed as shown below:
Select a trace from the list to open the side panel which shows the trace details.
To view detailed information of each span, click the three-dot icon adjacent to a trace.
Click View details.The details page is displayed with hierarchical representation of each span.
The span details page shows information about the type of service the span belongs to, operation details, and other attribute details.
A latency pie chart typically represents the distribution of latency or response time for the operation of a service. The latency pie chart breaks down the total response time into segments corresponding to different operations within the service. Each segment of the pie chart represents the time spent in a specific part of the application.
When analyzing the performance of an application, the trace details often include information about individual operations or components that contribute to the overall latency of a request. The fast calls refer to those parts of the system that have low latency and execute quickly, and their identification is crucial for efficient performance optimization.
To enhance the user experience, any fast calls with negligible latency (less than 0.10% when compared to total trace latency) present in the trace should be minimized when the user clicks on trace details.