Trace Details¶
In the trace Explorer, clicking on any trace allows you to view trace details, including relative time, duration, HTTP method, URL, status code, TraceId, flame graph, Span list, service call relationships, and associated logs, hosts, Metrics, and network information. For front-end applications (such as browsers), you can also view request timing distribution, including queue, first packet, and download timing ratios.
Note
- The RUM PV SDK must be version 2.2.10 or higher to display this data; if there are cross-origin situations, header configurations need adjustment.
For more details, refer to Web Application Integration.
- The flame graph/Span list/waterfall chart displays a maximum of 10,000 Spans. You can use the offset setting to view spans that are not displayed:
Flame Graph¶
The flame graph clearly shows the flow and execution time of each Span, with the service list and response times viewable on the right side. Clicking a Span allows you to view JSON content in the trace details, and you can zoom in for specific information using the mouse scroll wheel.
For more details, refer to Smart Use of Flame Graphs to Analyze Trace Performance.
From the flame graph above, this call 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 Mysql statements. During the entire execution of ActionResource.executeAction, Mysql statements are executed multiple times. The execution time calculation methods for CloudCare and Mysql are as follows:
- CloudCare service execution time = D1+D2+D3+D4+D5+D6+D7+D8+D9+D10+D11
- Mysql service execution time = span2+span3+......+span11
Specific executed statements and detailed execution times can be referenced in the Span list.
The service execution time ratio in the flame graph refers to the percentage of total time spent by each service during this call trace. In the example below, this call trace includes two services: CloudCare and Mysql, with execution time ratios of 42.37% and 57.63%, respectively. CloudCare service has 2 Spans, and Mysql service has 10 Spans.
- Mysql service execution time ratio calculation method: Sum of all span execution times / total duration of the current call trace.
Explanation of the calculation method: In the figure below, the Mysql service has a total of 10 Spans. You can click each Span to obtain its execution time. As shown in the figure, the execution time for this Span is 5.08ms. Proceed similarly to obtain the execution times for the remaining 9 Spans and sum them up.
- CloudCare service execution time ratio calculation method: (Total duration of the current call trace - Mysql service execution time) / Total duration of the current call trace.
Explanation of the calculation method: In the figure below, the CloudCare service spans the entire current call trace. Except for the Mysql service's execution time, the remaining time represents the CloudCare service's execution time (see the red-highlighted execution time portion). The execution time ratio can also be directly viewed via the Span list to check the execution time and execution time ratio for each Span.
In the flame graph, whether the service calls are synchronous or asynchronous, it can clearly track the performance data details of each trace. Through the flame graph, you can clearly see which requests were performed asynchronously, their start time, end time, and total time spent.
Span List¶
- Displays all Span resource names, quantities, durations, execution times, and ratios within the trace.
- You can input the resource name or Span ID for search matching.
- Clicking any Span allows you to view JSON content in the trace details and synchronize the display in the flame graph.
- If there is an error, an error message will be displayed.
- Clicking Error Spans, directly displays the filtered results.
Waterfall Chart¶
Displays parent-child relationships between resources.
The waterfall chart shows Span data based on the order of start times. On the left side, Span data is displayed along with the execution time ratio for each resource. On the right side, the waterfall chart is displayed according to the time sequence.
-
Input the corresponding resource name or Span ID for search matching;
-
Click to switch the format of the execution time;
-
Click Error Spans, to directly display the filtered results.
Service Call Relationships¶
Displays the call relationships and counts between services, searchable via service, resource, or Span ID.
The system displays the color of services in correspondence with the error results from the trace details > flame graph. Red indicates the presence of errors.
If you configure service bindings in the user view, such as service:mysql relationships, clicking the service card allows you to quickly view associated views. Clicking will redirect to the detail page.
Quick Actions¶
Action |
Description |
|---|---|
| Full-screen view/restore default size | You can click the full-screen icon in the top-right corner of the trace details to expand horizontally and view the trace flame graph; click the restore default size icon to return to the details page. |
| Locate to Current Span | Click to zoom in on the view and locate the current Span |
| Expand/collapse mini-map | You can click the expand/collapse mini-map icon on the left side of the trace details, allowing you to select intervals, drag, or scroll to quickly view the flame graph. |
| View Global Trace | You can click the view global Trace icon on the left side of the trace details to view the global trace in the flame graph. |
| Double-click Span | Zoom in on the selected Span in the center of the flame graph, allowing you to quickly locate and view context-related Spans. |
| Click Service Name | Highlights the corresponding Span; clicking the service name again restores the default selection of all Spans, allowing you to quickly filter and view Spans related to the service. |
Extended Attributes¶
In the search bar, you can input field names or values for quick search and positioning;
After checking field aliases, you can view them after the field name; you can choose as needed.
On the trace details page, you can view relevant field attributes of the current trace under Extended Attributes:
Field |
Attribute |
|---|---|
| Filter Field Value | Adds this field to the Explorer to view all data related to this field, which can be filtered and viewed in the trace Explorer. See Figure One. |
| Reverse Filter Field Value | Adds this field to the Explorer to view data other than this field. |
| Add to Display Columns | Adds this field to the Explorer list for viewing. |
| Copy | Copies this field to the clipboard. |
Some Fields Do Not Support Filtering Aggregation Logic
Guance Some fields use full-text indexing, and these fields do not support filtering aggregation logic. The range of full-text indexed fields is as follows:
| Category | Field |
|---|---|
| Objects, Resource Catalog | message |
| Logs, Backup Logs | message |
| Security | message / title |
| Network | message |
| Trace | error_message / error_stack |
| Events | message / title / df_message / df_title |
| RUM Errors | error_message / error_stack |
| RUM Long Tasks | long_task_message / long_task_stack |
Figure One
Error Details¶
On the trace details page, if there are error traces, you can view the related error details.
For more analysis of error traces, refer to Error Tracking.
Service Context¶
By obtaining object classifications from the infrastructure resource catalog and selecting the latest object based on create_time, you can quickly view the current service's runtime information, service dependency relationships, and integration information.
Correlation Analysis¶
You can view logs associated with the current trace (associated field: trace_id) through Logs. You can customize the displayed 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 the log page.
If you have administrator-level permissions or higher, you can customize the correlation fields. Click the settings button to the right of the correlation field, and in the pop-up dialog box, select the fields you want to associate, supporting manual input, drag-and-drop ordering, etc., confirming will complete the configuration.
Note: Custom correlation fields for logs and service lists influence each other. If custom fields are configured in the service list, they will be displayed here synchronously.
When the application uses the ddtrace collector and simultaneously enables APM trace tracking and Profile performance tracking data collection, Guance provides Span-level correlated viewing analysis. On the trace details page, you can click Code Hotspots below the flame graph to view code hotspots associated with the current trace, including execution time, methods, and execution time ratios.
Click View Profile Details to navigate to the Profile details page to view more associated code.
On the trace details page, you can view metrics and attribute views of related hosts through Hosts (associated field: host).
- Metrics View: You can view the performance metric status of related hosts from 30 minutes before the trace ends to 30 minutes after the trace ends, including CPU, memory, and other performance metric views of related hosts.
- Attribute View: Helps you trace back to the real state of host objects when the trace was generated, supporting viewing of the latest object data produced by related hosts within the corresponding time period, including basic host information and integration runtime conditions. If cloud host collection is enabled, you can also view cloud vendor information.
Note: Guance defaults to saving the last 48 hours of historical data for host objects. If no historical data for the host corresponding to the current trace time is found, you will be unable to view the attribute view of the associated host.
On the trace details page, you can view metric and attribute views of related containers through Containers (associated field: container_name).
-
Metrics View: Supports viewing the performance metric status of related containers from 30 minutes before the trace ends to 30 minutes after the trace ends, including CPU, memory, and other performance metric views of containers.
-
Attribute View: Helps you trace back to the real state of container objects when the trace was generated, supporting viewing of the latest object data produced by related containers within the corresponding time period, including basic container information and property information.
On the trace details page, you can view attribute and metric views of related Pods through Pods (associated field: pod_name).
-
Metrics View: Supports viewing the performance metric status of related Pod containers from 30 minutes before the trace ends to 30 minutes after the trace ends, including CPU, memory, and other performance metric views of containers.
-
Attribute View: Helps you trace back to the real state of Pod objects when the trace was generated, supporting viewing of the latest object data produced by related Pod containers 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 association fields, i.e., configure corresponding field tags during data collection; otherwise, you won't be able to match and view associated network views in the details page.
-
Host: Match field
host. -
Pod:
| Matching Field Priority |
|---|
| namespace、pod_name |
| namespace、pod |
| pod_name |
| pod |
- Deployment:
| Matching Field Priority |
|---|
| namespace、deployment_name |
| namespace、deployment |
| deployment_name |
| deployment |
- Service:
| Matching Field Priority |
|---|
| namespace、service_name |
| namespace、service |
Note:
- If association fields for Host, Pod, Deployment, and Service are queried simultaneously, network data will be displayed in this order upon entering the details page;
- If no association fields are found, they will be displayed at the bottom in gray, and clicking will prompt No network view matched.