Trace Details¶

The flame graph above shows that this trace involves two services: CloudCare and Mysql. The trace starts with a POST request to the CloudCare service, then executes ActionResource.executeAction, and finally executes MySQL statements. During the entire execution of ActionResource.executeAction, MySQL statements are executed multiple times. The execution time calculation for CloudCare and Mysql is as follows:

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

For specific executed statements and execution time details, refer to the Span list.

---

The service execution time percentage in the flame graph indicates the proportion of each service's total time in the trace. Taking the example below, this trace includes two services: CloudCare and Mysql, with execution time percentages of 42.37% and 57.63% respectively. CloudCare has 2 spans and Mysql has 10 spans.

• Mysql service execution time percentage = sum of all span execution times / total trace duration.

Instructions: In the figure below, the Mysql service has 10 spans. Click each span to get its execution time. As shown, the execution time of this span is 5.08ms. Repeat for the remaining 9 spans and sum them.

• CloudCare service execution time percentage = (total trace duration - Mysql execution time) / total trace duration.

In the figure below, the CloudCare service spans the entire trace. Excluding the Mysql execution time, the remaining time is the CloudCare execution time (see the red-highlighted part). The execution time percentage can also be viewed directly in the Span list for each span.

---

In the flame graph, whether calls are synchronous or asynchronous, you can clearly track the performance details of each trace. For example, you can see which requests are asynchronous, their start time, end time, and total duration.

---

You can view log data associated with all services in the entire trace through Logs (correlation field: trace_id). You can customize the display columns. To view more detailed log content, click the log content to go to the log details page, or click the jump button to open the Logs page.

The system matches the log index mapping based on fields such as service, env, and version of the current trace, and automatically selects the corresponding log index. The original index "Match Service" configuration continues to take effect based on the service field mapping.

If you have Admin or higher permissions, you can customize the correlation fields. Click the settings button on the right of the correlation field, select the fields to correlate in the dialog, and support manual input, drag-and-drop ordering, etc. Confirm to complete the configuration.

Note: Custom fields in correlated logs and the service list correlation analysis configuration affect each other. If custom fields are configured in the service list, they are displayed here synchronously.

When the application uses the ddtrace collector with both APM distributed tracing and Profile performance tracing data collection enabled, the system provides span-level correlation to view code hotspots, including execution time, methods, and execution time percentage.

Click View Profile Details to jump to the Profile details page to view more correlated code.

On the trace details page, you can view the metric view and attribute view of the associated host through Hosts (correlation field: host).

• Metric View: View the performance metrics of the associated host from 30 minutes before the trace ends to 30 minutes after the trace ends, including CPU, memory, and other performance metrics.

• Attribute View: Helps you trace back the actual state of the host object at the time the trace was generated. You can view the latest object data generated by the associated host within the corresponding time period, including host basic information and integration running status. If cloud host collection is enabled, cloud provider information is also available.

Note: Guance retains the last 48 hours of host object history data by default. If the host history data corresponding to the current trace time is not found, you will not be able to view the attribute view of the associated host.

On the trace details page, you can view the metric view and attribute view of the associated container through Containers (correlation field: container_name).

• Metric View: View the performance metrics of the associated container from 30 minutes before the trace ends to 30 minutes after the trace ends, including container CPU, memory, and other performance metrics.

• Attribute View: Helps you trace back the actual state of the container object at the time the trace was generated. You can view the latest object data generated by the associated container within the corresponding time period, including container basic information and attributes.

On the trace details page, you can view the metric view and attribute view of the associated Pod through Pods (correlation field: pod_name).

• Metric View: View the performance metrics of the associated Pod from 30 minutes before the trace ends to 30 minutes after the trace ends, including Pod CPU, memory, and other performance metrics.

• Attribute View: Helps you trace back the actual state of the Pod object at the time the trace was generated. You can view the latest object data generated by the associated Pod within the corresponding time period, including Pod basic information and attributes.

Guance supports viewing network topology and overview data for multiple dimensions including Host, Pod, Deployment, and Service under Network.

Matching Fields:

To view the related network on the details page, the corresponding correlation fields must be matched. That is, the corresponding field tags must be configured during data collection; otherwise, the associated network view cannot be matched on 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 all found, the network data is displayed in this order when entering the details page.
• If no correlation fields are found, the item is displayed in gray at the end, and clicking shows No network view matched.