Trace Explorer¶

Displays all Span data collected within the currently selected time range.

Filters and displays all Spans generated by service entry calls within the currently selected time range.

Filters and displays all top-level entry Spans of trace calls within the currently selected time range.

From the Flame Graph above, you can see that this invocation trace includes two services: CloudCare and Mysql. The trace starts with a POST request initiated by the CloudCare service, then executes ActionResource.executeAction, and finally executes the Mysql statement. Throughout the execution of ActionResource.executeAction, the Mysql statement is executed multiple times. The execution time calculation methods for CloudCare and Mysql are as follows:

• Execution time of CloudCare service = D1+D2+D3+D4+D5+D6+D7+D8+D9+D10+D11
• Execution time of Mysql service = span2+span3+......+span11

Specific statements and execution time details can be referenced from the Span list.

The percentage of service execution time in the Flame Graph refers to the ratio of each service's execution time to the total time for this invocation trace. In the example below, this invocation trace includes two services: CloudCare and Mysql, with execution time percentages of 42.37% and 57.63%, respectively. CloudCare service has 2 Spans, and Mysql service has 10 Spans.

• Mysql service execution time percentage calculation method: Sum of all Span execution times / Total duration of the current invocation trace.

Calculation Method Explanation: There are 10 Spans in the Mysql service in the figure below, and you can click each Span to obtain the execution time of the current Span. As shown in the figure, the execution time of this Span is 5.08ms. Then use the same method to obtain the execution times of the remaining 9 Spans and sum them up.

• CloudCare service execution time percentage calculation method: (Total duration of the current invocation trace - Mysql service execution time) / Total duration of the current invocation trace.

Calculation Method Explanation: The CloudCare service runs throughout the current invocation trace in the figure below. Except for the Mysql service execution time, the remaining time is the CloudCare service execution time (see the red-marked part of the execution time). The execution time percentage can also be directly viewed from the Span list for the execution time and execution time percentage of each Span.

In the Flame Graph, whether the service is synchronous or asynchronous, every detail of the trace performance data can be clearly tracked. For example, through the Flame Graph, you can clearly see which requests are asynchronous, start time, end time, and total time spent.

You can view logs associated with the current trace (correlation field: trace_id) through Logs. You can customize the display columns, and if you need to view more detailed log content, you can click the log content to navigate to the log details page, or click the jump button to open it on the log page.

If you have administrator-level permissions or above, you can customize correlation fields. Click the settings button next to the correlation field, and in the pop-up dialog box, select the fields you want to correlate, supporting manual input, drag-and-drop order operations, etc., confirming completes the configuration.

Note: Customizing correlation fields for logs and customizing correlation fields for service list analysis influence each other. If custom fields are configured in the service list, they will be displayed here synchronously.

When the application uses ddtrace collectors and both APM trace tracking and Profile performance tracking data collection are enabled, Guance provides Span-level correlation viewing analysis. In the trace details page, you can click Code Hotspots below the Flame Graph to view code hotspots related to the current trace, including execution duration, methods, and execution time percentage.

Clicking View Profile Details allows you to navigate to the Profile details page to view more associated code.

In the trace details page, you can view metric and attribute views of related hosts through Hosts (correlation field: host).

• Metric View: Displays the performance metric status of related hosts from 30 minutes before the end of the trace to 30 minutes after the end of the trace, including CPU, memory, and other performance metric views of the related hosts.

• Attribute View: Helps you trace back to the actual state of the host object when the trace was generated, allowing you to view the latest object data produced by the related host within the corresponding time period, including basic host information and integration operation conditions. If cloud host collection is enabled, you can also view cloud provider information.

Note: Guance defaults to saving the historical data of host objects for the last 48 hours. If no host historical data corresponding to the current trace time is found, you will not be able to view the attribute view of the associated host.

In the trace details page, you can view metric and attribute views of related containers through Containers (correlation field: container_name).

• Metric View: Supports viewing the performance metric status of related containers from 30 minutes before the end of the trace to 30 minutes after the end of the trace, including container CPU, memory, and other performance metric views.

• Attribute View: Helps you trace back to the actual state of the container object when the trace was generated, allowing you to view the latest object data produced by the related container within the corresponding time period, including basic container information and property information.

In the trace details page, you can view the attribute and metric views of related Pods through Pods (correlation field: pod_name).

• Metric View: Supports viewing the performance metric status of related Pods from 30 minutes before the end of the trace to 30 minutes after the end of the trace, including container CPU, memory, and other performance metric views.

• Attribute View: Helps you trace back to the actual state of the Pod object when the trace was generated, allowing you to view the latest object data produced by the related Pod within the corresponding time period, including basic container information and property information.

Guance supports you to view multi-dimensional network topology maps and summary data including Host, Pod, Deployment, and Service in Network.

Matching Fields:

To view related networks in the details page, you need to match the corresponding correlation fields, i.e., configure the corresponding field tags during data collection; otherwise, you cannot match and view the correlated network views in the details page.

• Host: Match field host.

• Pod:

Match Field Priority
namespace、pod_name
namespace、pod
pod_name
pod

• Deployment:

Match Field Priority
namespace、deployment_name
namespace、deployment
deployment_name
deployment

• Service:

Match Field Priority
namespace、service_name
namespace、service

Note:

• If correlation fields for Host, Pod, Deployment, and Service are found simultaneously, network data will be displayed in this order upon entering the details page;
• If no correlation fields are found, it will be displayed at the bottom in gray, and clicking will prompt No network view matched.