All Products
Search
Document Center

Serverless App Engine:API monitoring

Last Updated:Sep 03, 2024

The API monitoring feature is used to monitor the details of API calls of an application. API calls can be issued to perform SQL analysis, NoSQL analysis, exception analysis, and error analysis, transmit upstream and downstream data, and query traces. This topic describes how to view the details of API calls of a Serverless App Engine (SAE) application.

Procedure

  1. Log on to the SAE console.

  2. In the left-side navigation pane, click Applications. In the top navigation bar, select a region and click the name of an application.
  3. In the left-side navigation pane, choose Application Monitoring > API Operation Calls.

    In the left-side pane of the API Operation Calls page, you can view all API calls that are automatically detected by monitoring agents. You can sort the API calls by the response time (RT), number of requests, number of errors, or number of exceptions.

    Note The metrics vary based on the programming language. You can view the application monitoring metrics of a programming language based on your business requirements.

Supported frameworks

This feature can automatically detect and monitor the interfaces provided in the following web frameworks and remote procedure call (RPC) frameworks:

  • Tomcat 7+

  • Jetty 8+

  • Resin 3.0+

  • Undertow 1.3+

  • WebLogic 11.0+

  • SpringBoot 1.3.0+

  • HSF 2.0+

  • Dubbo 2.5+

Metric categories

Overview

On the Overview tab, you can view the detailed call topology of an interface and the time sequence curves about the number of requests, number of errors, response time, and HTTP status codes.

SQL and NoSQL analysis

On the SQL Analysis and NoSql Analysis tabs, you can view the SQL and NoSQL requests that are initiated within the code of the selected API operation in the left-side pane of the API Operation Calls page. On these tabs, you can find the SQL statements or NoSQL statements that cause slow responses of an API. You can also click Trace Query in the Actions column of an SQL or NoSQL statement to view the complete trace where the SQL or NoSQL execution logic resides.

Exception analysis

The Exception Analysis tab shows the Java exceptions that are thrown from the code of the selected interface in the left-side pane. You can also click Interface Snapshot in the Actions column to view the complete trace where the exception stack resides. For more information, see View traces.

Upstream services and downstream services

On the Upstream Services and Downstream Services tabs, you can view the interfaces and performance metrics of the upstream services that call the application and downstream services that are called by the application. The performance metrics include the response time, number of requests, and number of errors.

On the Upstream Traces and Downstream Traces tabs, you can perform the following operations based on your business requirements:

  • Click Expand/Collapse All in the upper part of the tab to show or hide all interfaces.

  • Enter a keyword of the application name or the interface name in the search box and click the Search icon to search for the interfaces whose names contain the keyword.

  • If you want to show or hide the information about the performance metrics of an interface, find the interface and click the collapse panel or click the upward arrow or downward arrow at the end of the row.

Error analysis

On the Error Analysis tab, you can view the errors and HTTP status codes of the application. You can also click a value in the TraceId column to view the trace information on a new page. For more information, see View traces.

Trace query

On the Interface Snapshot tab, you can view the parameters of the selected interface and two charts that are generated based on the parameters. The charts show the statistics on the total number of interface calls and the RT of interface calls.

  • The Total Traces chart shows the total number of interface calls and the number of slow interface calls. If the RT of an interface call exceeds 500 milliseconds, the interface call is defined as a slow interface call. The threshold can be configured in the application settings. The number of slow interface calls does not include local interface calls that are generated in asynchronous scenarios.

  • The interface response time chart shows the RT trend over time. The chart is generated based on the statistics on interface calls and is affected by the sampling rate that you specify.

  • The trace details table shows the detailed trace information. You can click a value in the TraceId column to view the trace information. For more information, see Trace details.

  • You can also click View Logs in the Actions column to view the logs of interface calls.

    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 business logs.