A scheduled task can be created to automatically run a program or command on a one-time or recurring basis. You can query the details of a scheduled application monitoring task on the Application Real-Time Monitoring Service (ARMS) console. The details include task overview, analysis of SQL requests and NoSQL requests, exception analysis, error analysis, downstream services, and invocation traces.

Note The ARMS application monitoring feature supports only scheduled tasks of the XXL-JOB and SchedulerX types.

Procedure

  1. Log on to the ARMS console.
  2. In the left-side navigation pane, Select Application monitoring > Applications .
  3. In the top navigation bar of the MNS console, select the region where your cluster is deployed.
  4. Log on to the Applications Page, click the application name.
  5. In the left-side navigation pane, click Scheduled Tasks.
    The scheduled tasks of your application are displayed in the left-side list on the scheduled tasks page.
  6. Click a scheduled task to view its details.
Notice The scheduled task feature supports only ARMS agents of version 2.7.1.3 or later. For more information about how to upgrade an ARMS agent, see Update the ARMS agent for Java applications.

View task overview

On the Overview tab, you can view the detailed call topology of the scheduled task and the time series charts of the number of runs, average running time, the number of exceptions, and scheduling latency.

View SQL and NoSQL analysis

On the SQL Analysis and NoSql Analysis tabs, you can view the SQL and NoSQL requests that are initiated by the selected scheduled task. On these tabs, you can locate slow SQL statements or NoSQL statements that affect the speed of scheduled tasks.

Optional: In the SQL or NoSQL statement list, perform the following operations as needed:
  • Click Invocation Statistics in the Actions column of a SQL or NoSQL statement to view the time series chart of the SQL or NoSQL call statistics.
  • Click Invocation Trace Query in the Actions column of a SQL or NoSQL statement to view its invocation trace. For more information, see View invocation traces.

View exception analysis

On the Exception Analysis tab, you can view the Java exceptions that are thrown from the code of the scheduled task.

Optional: In the exception list, perform the following operations as needed:
  • Click Invocation Statistics in the Actions column of an exception to view its time series chart.
  • Click Invocation Trace Query in the Actions column of an exception to view its invocation trace. For more information, see View invocation traces.

View error analysis

On the Error Analysis tab, you can view the error statistics of the scheduled task.

Optional: In the error list, perform the following operations as needed:
  • Click the trace ID in the TraceId column of an error to view its invocation trace. For more information, see Trace query.
  • Click View Logs in the Actions column of an error to view its logs.

View downstream services

On the Downstream Services tab, you can view the APIs and performance metrics of the downstream services that are called by the application. The performance metrics include the response time, the number of requests, and the number of errors.

On the Downstream Services tab, perform the following operations as needed:

  • Click Collapse/Expand All at the top to show or hide all APIs.
  • Enter a keyword of the application name or the API (span) name in the search box and click the Search icon to search for the APIs whose names contain the keyword.
  • Click the collapsible panel that contains the API information, or click the upward or downward arrow at the end of the row to expand or collapse the performance metric information of the API.

View invocation traces

On the Invocation Trace Query tab, you can view the details of traces and two charts that display the total number and response time of API calls.

  • The Total invocation traces chart, which is marked as 1 in the preceding figure, displays the numbers of normal traces and slow traces over time. The traces for which the response time of API calls exceeds 500 milliseconds are defined as slow traces. The number of slow traces is affected by the value of the Interface Response Time Threshold parameter that you specified in the application configurations. Slow traces do not include the sub-traces that are performed for the asynchronous calls of on-premises APIs.
  • The Trace response time chart, which is marked as 2 in the preceding figure, displays the trends in response time over time. The chart is generated based on the statistics of API call tracing and is affected by the sampling rate that you specified.
  • The trace details table, which is marked as 3 in the preceding figure, displays the detailed trace information. You can click a value in the TraceId column to view the trace information and business information. You can also click View Logs in the Actions column to view the logs of API calls.