DocsICP FilingConsole
Documentation
Home Page Application Real-Time Monitoring Service Application Monitoring User Guide Applications View monitoring details Application details Error analysis

Error analysis

Updated at:
Copy as MD
Product
My Favorites

This topic describes how to use error analysis to understand errors in your application.

What is an error

In ARMS error analysis, an error is an API call that returns an explicit error response. This includes the following cases:

  • For an HTTP request, the returned HTTP status code is greater than 400.

    You can also set filtering rules for specific HTTP status codes on the Custom Configurations page of your application. The error analysis feature of ARMS then ignores these HTTP status codes.

  • The requester can also detect other explicit error responses, which are typically caused by uncaught exceptions.

Prerequisites

Connect your application to Application Monitoring

Procedure

  1. Log on to the ARMS console. In the left-side navigation pane, choose Application Monitoring > Application List.

  2. On the Application List page, select the region in the top navigation bar and then click the name of the application.

    Note

    Icons in the Language column have the following meanings:

    • Java icon: a Java application connected to Application Monitoring.

    • image: a Golang application connected to Application Monitoring.

    • image: a Python application connected to Application Monitoring.

    • -: an application connected to Managed Service for OpenTelemetry.

  3. In the left-side navigation pane, click Application Details.

  4. On the Application Details page, select an application instance, specify a time range, and then click the Error Analysis tab.

    The Error Analysis tab displays two trend charts, Errors / min and HTTP - Status Code, and a list of errors. The list includes the Time, API Name, Application, Time Consumed, Status, and TraceId columns, and a View Logs link in the Actions column.

Error count

The Errors section charts the number of application errors over the specified time period.

Optional: In the Errors section, you can perform the following operations:

  • Move the pointer over a chart and view the statistics.

  • Drag the bars horizontally to view the statistics of specified time periods.

  • Click the chart icon to view metric statistics during a selected time period or compare performance within the same period across different days.

  • Click the code icon to view the API details of the metric.

HTTP status code

The HTTP Status Codes section charts the HTTP status codes for the application over the specified time period.

Optional: In the HTTP Status Codes section, you can perform the following operations:

  • Move the pointer over a chart and view the statistics.

  • Drag the bars horizontally to view the statistics of specified time periods.

  • Click the legend to hide or show the data.

  • Click the chart icon to view metric statistics during a selected time period or compare performance within the same period across different days.

  • Click the code icon to view the API details of the metric.

Error list

The error list displays all application errors during the specified time period.

Optional: In the error list, you can perform the following operations:

  • In the TraceId column, click a TraceId to view the call chain for that error. For more information, see Trace query.

  • In the Actions column, click View Logs to view the logs associated with the error.

    Note

    You must associate trace IDs with the business logs of an application. This way, when an error occurs in the application, you can access the business logs that are associated with trace IDs to troubleshoot the error. For more information, see Associate trace IDs with Java business logs.

Previous：Upstream applicationsNext：Query traces