Traces Page Overview

Last updated on 13 June, 2023

The Traces page displays the traces and operations of the trace data from your instrumented applications. You can also view information like the application topology map of your services, error rate, average latency, and request rate of your services. With one click, you can filter the data based on either latency or time period. For more information, see Traces Page Filtering Operations. You can either access the Traces page from the navigation sidebar or from a service in Resources. By default, the Traces page displays information about the selected namespace in different widgets. 

Traces dashboard

The Traces page is structured into Topology, RED metric, and Services sections which comprise of the following: 

  • APM Topology Widget
  • Error Rate
  • Request Rate
  • Average Latency 
  • Services

APM Topology Widget

The APM topology widget enables you to visualize your complex application services and navigate based on topology relationships. Double-clicking each service redirects you to the Resources page. For more information, refer to Application Topology Overview.  

APM topology widget

Error Rate

This widget displays a graphical representation of the error span’s percentage within the total number of spans instrumented for a given time. For example, the error percentage was 0.274 at 12:28 hours. 

Error rate widget

Request Rate

This widget displays a graphical representation of the number of request counts received with respect to time. For example, the request count was 35.61 at 17:58 hours. 

Request rate widget

Average Latency

This widget displays a graphical representation of the average span duration (average latency of spans) in milliseconds (ms) within the total number of spans instrumented for a given time. For example, the average latency was 437.36 ms at 18:03 hours.

Average Latency


This widget displays detailed information on the services such as the health of the service, error rate, request volume, average latency and active alerts. You can select the services based on Top 5, Top 10, Top 15, Top 20, and Top 25 entries.

Services table

The services table displays the following details:

Field Description
Health Displays the health state of the service. The different health states are as follows:
  • Cleared
  • Critical
  • Warning
  • Error
Service Displays the name of the service.
Error Rate(%) Displays a graph of the total number of errors detected for the individual service.
Request Volume Displays a sparkline of the total number of requests generated for the individual service.
Average Latency (ms) Displays a sparkline of the total duration of the operation in milliseconds.
Active Alerts Displays the total number of alerts generated for the individual operation.

In addition to the specific operations of a trace, the traces table also provides the following features:

  • New_window—opens the end-to-end trace view for the selected operation, along with other operations in the trace in a new tab.
  • topology_map—opens a topology map that describes conceptual information about the application. For more information, see Application Topology Overview.

Comparing Multiple Services Data

You can select services from the Topology widget and view the impact analysis of services on the overall application under the RED metrics widgets. For example, if you have emailservice, cartservice, and frontendservice services running and want to compare the impact of each service on the application. You can visually compare them on the Traces page. 

Some of the benefits of using this feature are:

  • Allows you to see the impact of an individual or multiple services on the application.
  • Visually compare the multiple services data for a given time range.

Do the following:

  1. In the APM Topology Widget, select the required service.
  2. Right-click on the service and select Add to Application Analysis
    The overlay graphs display the details of the multiple services for that time range.
    Note:  You can add a maximum of four services to the application analysis. 
In This Article