Application Real-Time Monitoring Service (ARMS) provides the Trace Explorer feature to analyze stored full trace data. This feature allows you to filter and aggregate trace data, providing a simple and flexible analysis solution. This way, the requirements of custom diagnosis in various scenarios can be met.
- Log on to the ARMS console .
- In the left-side navigation pane, choose . In the top navigation bar, select a region. If this is the first time that you enter the Trace Explorer page, you must authorize ARMS to access Log Service. This allows data to be delivered to Log Service for analysis. You are not charged for the authorization.
After you complete authorization, resources are automatically prepared. The process is expected to complete within 2 minutes.Note
- You are not charged for using the Trace Explorer feature.
- If Trace Explorer failed to be activated, try again or contact technical support. For more information, see Technical support.
- In the upper-right corner of the Trace Explorer page, select a time range that you want to query.
- Specify filter conditions.
- In the Saved Filters section, query traces by status, consumed time, application name, span name, or host
The filter conditions that you specify are displayed in the search box.
- In the search box, add or remove filter conditions. Note
- You can click the icon next to the search box to save the current filter conditions.
- You can click Saved View to view the saved filter conditions and click a filter condition to view the corresponding trace data.
- In the search box, enter a query statement. For more information about the supported syntax, see Use Trace Explorer to query traces.
- In the Saved Filters section, query traces by status, consumed time, application name, span name, or host address.
After you specify filter conditions, trace data is displayed on the Trace Explorer page. The trace data includes the column charts of spans and HTTP errors, the time series curve of consumed time, and a span list.
In the span list, you can perform the following operations:
- Click View in the Actions column to view complete trace information. For more information, see Trace details.
- Click the icon in the upper-right corner to add or hide the fields of the list.
- Move the pointer over a span and click the icon to add the current parameter values as a filter condition.
- count: specifies the number of times that the spans are called.
- group by: specifies the group of spans.
- limit to: specifies the top 5, top 10, bottom 5, or bottom 10 spans in the specified group.
Note If the group by parameter is set to no group, you cannot set the limit to parameter.
- Interval: specifies the time interval between two consecutive span analysis processes.
After you specify analysis conditions, you can view the time series charts and detailed statistics of spans.
In the trace details panel, you can view all the spans, start time, errors, total consumed time of the trace, and the consumed time of each span.
- Move the pointer over the name of a span to view the span name, application, IP address, and start time.
- Click the icon next to a span to view the method stacks.
- Click the name of a span to view the additional information and metric details on the right of the panel. For more information about the parameters in the Additional information and Metrics tabs, see Trace Explorer parameters. For information about Java virtual machines and hosts, see JVM monitoring and Host monitoring.
Trace data is stored in Log Service. The project name is proj-xtrace-<encode>-<region-id>. The Logstore name is logstore-tracing. The region-id parameter is the region where you use Trace Explorer, for example, cn-hangzhou. For information about data formats, see Trace Explorer parameters. You can perform custom development on the stored full trace data. You can analyze the stored full trace data based on filter conditions or aggregation dimensions. This way, the requirements of custom diagnostics in various scenarios can be met. For more information, see Identify five common issues by using Trace Explorer.