All Products
Search
Document Center

Application Real-Time Monitoring Service:Trace query

Last Updated:Jun 21, 2026

On the Trace Query page, you can find a specific trace by its traceId, filter traces using multiple conditions, or perform aggregate analysis on them.

Query traces

  1. Log on to the ARMS console.

  2. In the left-side navigation pane, choose Application Monitoring > Trace Query. In the top navigation bar, select a region.

  3. On the Trace Query page, select a Parameter Type, enter a value in the Parameter Value field, and then click Add to Query Condition.

    You can use the traceId parameter to perform an exact search.

    Table 1. Parameter types

    Parameter type

    Description

    traceId

    Enter a traceId.

    Operation name

    The operation name for the interface call. Fuzzy search is not supported.

    Client application name

    The name of the client application.

    Server application name

    The name of the server application.

    Duration greater than

    Filters for calls with a duration greater than the specified value in milliseconds.

    Call type

    Select a call type.

    Has exception

    Finds traces that include one or more exceptions.

    Client IP address

    The IP address of the application that initiated the call.

    Server IP address

    The IP address of the application that received the request.

    Business primary key

    The field used to search for business events.

    Response code

    Enter a response code.

  4. Click a traceId in the results to open the Trace page.

    The Trace page displays the following information for each span in the trace:

    • Application name: The name of the application.

    • Log generated at: The time when the log was generated.

    • Status: Red indicates the service call has an exception, and green indicates it was successful.

    • IP address: The IP address of the application.

    • Call type: The type of the call, which matches the option selected in the query conditions.

    • Operation name: The operation name of the service.

    • Timeline: The duration of the service call and its position within the overall trace.

Analyze traces

On the Trace Query page, select the checkboxes of the traces that you want to analyze and click Analyze Selected Traces.

In the Trace Explorer panel, you can view the span name, application name, call type, request count/ratio, exception count/ratio, average self-duration/ratio, and average duration for all selected traces.

  • Hover over a span name to view the traceIds that contain the span.

  • Click an application name to go to the Application Overview page for that application.

  • In the Actions column for a target span, click Statistical Analysis to view its details. This information includes the call type distribution, total duration, operation name, request count, sample recommendations, and a list of all called methods with their name, type, call count, execution time, and percentage of the total time. For example, the Trace Analysis panel might show performance details for the /cart operation: a total duration of 9.4s and 1,000 requests. The pie chart on the left shows the time distribution, with HTTP calls accounting for 26.8% and local methods for 73.2%. The method list on the right shows that the method org.apache.http.protocol.HttpRequestExecutor.execute (Type: HTTP) was called 685 times, had an execution time of 2.5s, and accounted for 26.8% of the total time.