Before You Start
This document describes how to use Application Performance Management (APM).
The Applications page displays information such as components, environments, Agent status, and supported operations. | |
APM has built-in CMDB for managing the application structure and related configurations. | |
APM can manage tags and monitor the metric data of JVM, GC, service calls, exceptions, external calls, database access, and middleware, helping you comprehensively monitor application running. Application metrics can be reported to the AOM console through Prometheus instances. | |
Information such as the call status, duration, and API is displayed, helping you further locate fault causes. | |
The call and dependency relationships between applications are displayed, and abnormal instances can be automatically discovered. There are two types of application topologies:
| |
Through URL tracing, you can monitor the call relationships between important APIs and downstream services, and then detect problems more precisely. | |
You can tag resources under your account for classification. | |
You can add tags for different environments and applications for easy management. | |
When an application connected to APM meets a preset alarm condition, an alarm is triggered and reported in a timely manner. In this way, you can quickly learn about service exceptions and rectify faults to prevent loss. | |
Agent Management allows you to check the deployment and running statuses of the Agents that are connected to APM, and to stop, start, or delete them. | |
Configuration Management manages and displays the configurations supported by APM in a centralized manner. It consists of two parts:
| |
System Management manages and displays system configurations in a centralized manner, including:
| |
Enterprise Project Management Service (EPS) is used to control user access to APM resources. | |
Learn more | Create a user and grant permissions. Learn how to connect applications to APM in different scenarios. |