Serverless App Engine (SAE) provides non-intrusive application monitoring and alerting capabilities for multiple languages and frameworks. The Application Overview page displays key metrics of an application to help you understand the overall health of the application. This topic describes how to view the overview metrics of a SAE application monitoring.

Background information

Java and PHP languages

SAE integrates the ARMS application monitoring. Application Real-Time Monitoring Service (ARMS) is an application performance management (APM) service. To monitor an application, you need to only install the ARMS agent. You do not need to modify the code of the application. The ARMS agent helps you identify abnormal or slow API operations, view request parameters, and detect system bottlenecks. This improves the efficiency of online troubleshooting. For more information about empty list protection, see Overview.

Other languages such as Python, Node.js, and Go

Based on the eBPF technology, the SAE application monitoring supports non-intrusion metric collection, monitoring and alerting capabilities for any language and any framework. It provides application and instance-level metric RED (number of requests, number of errors, and response time) and HTTP status code statistics, as well as interface-level call information for services and dependent services. With the built-in visualized dashboard, developers and O&M personnel can evaluate the external service status of the current application in a timely manner and effectively identify problems such as user experience, service interruption, and business exceptions.

SAE application monitoring capabilities have the following core advantages:
  • O&M-free: out-of-the-box, the deployment takes effect immediately. You do not need to run, maintain, monitor, and alert components.
  • Non-intrusive code: You can obtain rich monitoring data without the need to track code or modify dependencies.
  • Multi-language support: The network protocol is parsed at the kernel layer and supports any language and any framework.
  • Multi-protocol coverage: supports monitoring of metrics and links for network protocols such as HTTP, MySQL, Redis, Kafka, and DNS.
  • High performance: obtains metric data with extremely low performance consumption by reducing data copying between the kernel state and the user state.

Entry point

Java and PHP languages

  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, click application monitoring > Application Overview. On the Application Overview page, view the information on the Overview tab.

Other languages such as Python, Node.js, and Go

  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, click application monitoring. On the application monitoring page, view the information.

Category

Java and PHP languages

The Overview tab displays the following key metrics.
  • The total number of requests, average response time, number of instances, number of issues, number of full GCs, and number of slow SQL queries within the selected time period, and the year-on-year increase and decrease rates of these metrics compared with the previous week and the previous day.
  • Application Events: application events, such as availability alerts, application monitoring alerts, and Kubernetes cluster events.
  • Application Support Services: time series curves for the number of requests to the services provided by the application and average response time.
  • Application Dependent Services: time series curves for the number of requests to the dependent services, average response time, number of instances within the application, and HTTP status codes.

Other languages such as Python, Node.js, and Go

The key metrics displayed on the application monitoring page are as follows.
  • Overview tab: the number of application-provided service requests, HTTP-status code statistics, number of application-provided service errors, number of application-dependent service requests, average response time of application-provided services, and average response time of application-dependent services.
  • On the Interface Invocation tab, specify the number of requests, number of errors, and average response time.
  • On the External Calls tab, locate the external calls of the application, such as slow or faulty calls.