Performance metric data
+Data Type
|
-JVM data, exceptions, databases, SQL statements, and middleware call data
+ | Collected Data
|
-WebSocket Secure (WSS)
+ | Transmission Mode
|
-Tenant-based isolated storage on the server
+ | Storage Mode
|
-Metric query and display at the frontend
+ | Function
|
-7 days for the basic edition and 30 days for the enterprise edition. The data will be permanently deleted upon expiration.
+ | Storage Period
|
-Tracing data
+ | Performance metric data
|
-Trace event data, including middleware invocation data
+ | JVM data, exceptions, databases, SQL statements, and middleware call data
|
-WSS
+ | WebSocket Secure (WSS)
|
-Tenant-based isolated storage on the server
+ | Tenant-based isolated storage on the server
|
-Query and display at the tracing frontend
+ | Metric query and display at the frontend
|
-7 days for the basic edition and 30 days for the enterprise edition. The data will be permanently deleted upon expiration.
+ | 7 days for the basic edition and 30 days for the enterprise edition. The data will be permanently deleted upon expiration.
|
-Resource information
+ | Tracing data
|
-Service type, service name, creation time, deletion time, node address, and service release API
+ | Trace event data, including middleware invocation data
|
-WSS
+ | WSS
|
-Tenant-based isolated storage on the server
+ | Tenant-based isolated storage on the server
|
-Query and display at the resource library frontend
+ | Query and display at the tracing frontend
|
-7 days for the basic edition and 30 days for the enterprise edition. The data will be permanently deleted upon expiration.
+ | 7 days for the basic edition and 30 days for the enterprise edition. The data will be permanently deleted upon expiration.
|
-Resource attributes
+ | Resource information
|
-System type, system startup event, number of CPUs, service executor, service process ID, service pod ID, CPU label, system version, web framework, JVM version, time zone, system name, collector version, and LastMail URL
+ | Service type, service name, creation time, deletion time, node address, and service release API
|
-WSS
+ | WSS
|
-Tenant-based isolated storage on the server
+ | Tenant-based isolated storage on the server
|
-Query and display at the resource library frontend
+ | Query and display at the resource library frontend
|
-7 days for the basic edition and 30 days for the enterprise edition. The data will be permanently deleted upon expiration.
+ | 7 days for the basic edition and 30 days for the enterprise edition. The data will be permanently deleted upon expiration.
+ |
+
+Resource attributes
+ |
+System type, system startup event, number of CPUs, service executor, service process ID, service pod ID, CPU label, system version, web framework, JVM version, time zone, system name, collector version, and LastMail URL
+ |
+WSS
+ |
+Tenant-based isolated storage on the server
+ |
+Query and display at the resource library frontend
+ |
+7 days for the basic edition and 30 days for the enterprise edition. The data will be permanently deleted upon expiration.
|
diff --git a/docs/apm/umn/apm_01_0013.html b/docs/apm/umn/apm_01_0013.html
index 657fc101..b0327645 100644
--- a/docs/apm/umn/apm_01_0013.html
+++ b/docs/apm/umn/apm_01_0013.html
@@ -1,12 +1,11 @@
Metric Overview
-A metric describes resource performance data or status. It consists of the metric type, name, and description, data type, and default aggregation mode.
-  For the default aggregation mode, LAST indicates the value of the latest metric collected. SUM indicates the sum of collected metrics. MAX indicates the maximum value of collected metrics. AVG indicates the average value of collected metrics.
-
-
+- Metric Overview
+
- Exception
- Basic Monitoring
diff --git a/docs/apm/umn/apm_01_0016.html b/docs/apm/umn/apm_01_0016.html
index b3ef5887..ec45353c 100644
--- a/docs/apm/umn/apm_01_0016.html
+++ b/docs/apm/umn/apm_01_0016.html
@@ -1,8 +1,7 @@
Basic Monitoring
-APM collects basic metrics, covering GC, JavaMethod, JVM, JVMInfo, Netty memory, and threads. This section describes the types, names, and meanings of basic metrics collected by APM.
-
- GC Monitoring
diff --git a/docs/apm/umn/apm_01_0017.html b/docs/apm/umn/apm_01_0017.html
index 86878efc..55fd7b52 100644
--- a/docs/apm/umn/apm_01_0017.html
+++ b/docs/apm/umn/apm_01_0017.html
@@ -1,8 +1,7 @@
Databases
-APM collects metrics from the C3P0 connection pool, Cassandra, ClickHouse database, DBCP connection pool, Druid connection pool, EsRestClient, GaussDB database, HBase, Hikari connection pool, Jetcd, and MongoDB, MySQL database, ObsClient, Oracle database, and Postgresql database. This section describes the types, names, and meanings of database metrics collected by APM.
-
- C3P0 Connection Pool Monitoring
diff --git a/docs/apm/umn/apm_01_0018.html b/docs/apm/umn/apm_01_0018.html
index 530e675e..6a934d0c 100644
--- a/docs/apm/umn/apm_01_0018.html
+++ b/docs/apm/umn/apm_01_0018.html
@@ -1,8 +1,7 @@
URLs
-APM collects URL call statistics, covering CSEProvider cluster, Dubbo server, FunctionGraph, and URL monitoring. This section describes the types, names, and meanings of URL metrics collected by APM.
-
- CSEProvider Cluster Monitoring
diff --git a/docs/apm/umn/apm_01_0019.html b/docs/apm/umn/apm_01_0019.html
index 009ea783..6dcb3a74 100644
--- a/docs/apm/umn/apm_01_0019.html
+++ b/docs/apm/umn/apm_01_0019.html
@@ -1,8 +1,7 @@
External Calls
-APM collects external call metrics, covering ApacheHttpAsyncClient connection pool, ApacheHttpClient connection pool, CSEConsumer cluster, Dubbo client, and HttpClient. This section describes the types, names, and meanings of external call metrics collected by APM.
-
- ApacheHttpAsyncClient Connection Pool
diff --git a/docs/apm/umn/apm_01_0020.html b/docs/apm/umn/apm_01_0020.html
index 278a1cbe..71292be0 100644
--- a/docs/apm/umn/apm_01_0020.html
+++ b/docs/apm/umn/apm_01_0020.html
@@ -1,8 +1,7 @@
Cache
-APM collects cache metrics, covering Redis method call, Jedis monitoring, and Lettuce client. This section describes the types, names, and meanings of cache metrics collected by APM.
-
- Redis Method Call
diff --git a/docs/apm/umn/apm_01_0023.html b/docs/apm/umn/apm_01_0023.html
index af12cfa1..1aa1af4a 100644
--- a/docs/apm/umn/apm_01_0023.html
+++ b/docs/apm/umn/apm_01_0023.html
@@ -1,8 +1,7 @@
Message Queues
-APM collects message queue metrics, covering KafkaConsumer, KafkaProducer, RabbitMqCommon, RabbitMqConsumer, RabbitMqProducer, RocketMqConsumer, and RocketMqProducer. This section describes the types, names, and meanings of message queue metrics collected by APM.
-
- KafkaConsumer Monitoring
diff --git a/docs/apm/umn/apm_01_0024.html b/docs/apm/umn/apm_01_0024.html
index a6d42280..737f26cc 100644
--- a/docs/apm/umn/apm_01_0024.html
+++ b/docs/apm/umn/apm_01_0024.html
@@ -1,8 +1,7 @@
RPC
-APM collects remote procedure calls (RPCs) metrics, covering gRPCClient and gRPCServer monitoring. This section describes the types, names, and meanings of RPC metrics collected by APM.
-
- GRPCClient Monitoring
diff --git a/docs/apm/umn/apm_01_0025.html b/docs/apm/umn/apm_01_0025.html
index 260be6f4..91193d7f 100644
--- a/docs/apm/umn/apm_01_0025.html
+++ b/docs/apm/umn/apm_01_0025.html
@@ -1,8 +1,7 @@
IoT
-APM collects IoT metrics, including CoapClient, CoapServer, MoquetteBroker, PahoPublisher, PahoSubscriber, and Paho. This section describes the types, names, and meanings of IoT metrics collected by APM.
-
- CoapClient Monitoring
diff --git a/docs/apm/umn/apm_01_0052.html b/docs/apm/umn/apm_01_0052.html
index c0fdaca6..02a69c9c 100644
--- a/docs/apm/umn/apm_01_0052.html
+++ b/docs/apm/umn/apm_01_0052.html
@@ -219,7 +219,7 @@
-Summary (total: URL call statistics summary)
+ | Summary (total: URL call statistics summary)
|
errorCount
|
@@ -286,7 +286,7 @@
SUM
|
-Status code (statuscode: APM counts URL call statistics based on the status code returned.)
+ | Status code (statuscode: APM counts URL call statistics based on the status code returned.)
|
code
|
@@ -327,7 +327,7 @@
LAST
|
-URL monitoring (url: APM counts URL call statistics by URL.)
+ | URL monitoring (url: APM counts URL call statistics by URL.)
|
url
|
@@ -576,7 +576,7 @@
SUM
|
-Cluster call (user: APM counts URL call statistics based on the cluster ID of the caller.)
+ | Cluster call (user: APM counts URL call statistics based on the cluster ID of the caller.)
|
clusterId
|
diff --git a/docs/apm/umn/apm_01_0056.html b/docs/apm/umn/apm_01_0056.html
index fbb79267..f9714100 100644
--- a/docs/apm/umn/apm_01_0056.html
+++ b/docs/apm/umn/apm_01_0056.html
@@ -759,7 +759,7 @@
taskCount
|
-taskCount
+ | taskCount
|
Number of tasks
|
diff --git a/docs/apm/umn/apm_01_0093.html b/docs/apm/umn/apm_01_0093.html
new file mode 100644
index 00000000..7962856d
--- /dev/null
+++ b/docs/apm/umn/apm_01_0093.html
@@ -0,0 +1,47 @@
+
+
+JavaAgent Updates
+
+ Table 1 JavaAgent updatesVersion
+ |
+Description
+ |
+
|---|
+
+2.4.8-jdk17
+ |
+1. Supported Redisson 3.17.x.
+2. Supported top percentile (TP) on the URL page.
+ |
+
+2.3.15
+ |
+1. Added support for Dubbo 2.8.x.
+2. Supported JDK HTTP subclasses.
+ |
+
+
+
+
+
+ Table 2 Latest JavaAgent versions on CCEVersion
+ |
+Actual Version
+ |
+
|---|
+
+latest
+ |
+2.4.8-jdk17; compatible with x86 and Arm architectures
+ |
+
+
+
+
+ Metric Overview
+A metric describes resource performance data or status. It consists of the metric type, name, and description, data type, and default aggregation mode.
+ For the default aggregation mode, LAST indicates the value of the latest metric collected. SUM indicates the sum of collected metrics. MAX indicates the maximum value of collected metrics. AVG indicates the average value of collected metrics.
+
+ Enabling APM
- Enable APM.
- Log in to the APM console.
If you log in to the APM console for the first time, you can choose the free or enterprise edition. For details, see Edition Differences.
- - Click
 on the left and choose Management & Deployment > Application Performance Management.
+ - Click on the left and choose Application > Application Performance Management.
- Obtain the access key that is automatically created.
APM uses AK/SK for signature verification. Only authorized accounts can report data.
- Log in to the APM console.
- In the navigation pane, choose System Management > Access Keys.
- On the Access Keys page, view the access key that has been automatically created.
diff --git a/docs/apm/umn/apm_02_0003.html b/docs/apm/umn/apm_02_0003.html
index ccc7581b..53ac9aec 100644
--- a/docs/apm/umn/apm_02_0003.html
+++ b/docs/apm/umn/apm_02_0003.html
@@ -2,12 +2,14 @@
Connecting Agents
PrerequisitesThe network between your host and APM is normal.
- You can run the Telnet command to check the network.
+ You can run the Telnet command to check the network.
+  Java supports enhanced Agents.
+
- Procedure- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Applications.
- On the displayed page, click Access Application.
Figure 1 Accessing an application
+Procedure- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Applications.
- On the displayed page, click Connect Application.
Figure 1 Connecting an application
- Select a region and application.
Figure 2 Basic information
- - For Backend language, select Java.
Figure 3 Access mode
- - For Code Source, select Enhanced probe.
- Select an access mode based on the application type, and access data by following the instructions.
Figure 4 Data access
+ - Select Java for Backend Language.
Figure 3 Access mode
+ - Select Enhanced Agent for Code Source.
- Select an access mode based on the application type and access data by following the instructions.
Figure 4 Data access
Table 1 Parameter descriptionParameter
|
@@ -17,16 +19,26 @@
|---|
-pwd
+ | APM_AK
+APM_SK
|
-Path where the apm-javaagent.jar package is located.
+ | AK and SK for installing JavaAgent.
+ CAUTION: When you copy the command to install JavaAgent, delete {} when setting APM_AK and APM_SK.
+
|
-Yes
+ | Yes
+ |
+
+Probe Installation Path
+ |
+Path for installing the Agent.
+ |
+Yes
|
appName
|
-Component name, which must start with a character. A component can contain multiple environments. The names of components under an application must be unique. If there are duplicate names, use instanceName to distinguish them.
+ | Component name, which must start with a letter. A component can contain multiple environments. The names of components under an application must be unique. If there are duplicate names, use instanceName to distinguish them.
|
Yes
|
@@ -59,11 +71,11 @@
No
|
-instanceName
+ | User Application
|
-Name of an instance, which is left blank by default. If an application has multiple instances deployed on a host, use this parameter to distinguish them. Generally, Java instances deployed on a host belong to different applications. An application rarely has identical instances.
+ | Name of a user application.
|
-No
+ | Yes
|
diff --git a/docs/apm/umn/apm_02_0004.html b/docs/apm/umn/apm_02_0004.html
index 5ddf7c12..ee14c103 100644
--- a/docs/apm/umn/apm_02_0004.html
+++ b/docs/apm/umn/apm_02_0004.html
@@ -2,7 +2,7 @@
Manually Installing Agents for Java Applications
Prerequisites- The network between your host and APM is normal.
You can run the Telnet command to check the network.
-
+If the network is not connected, use a proxy instead.
- The AK/SK required for accessing JavaAgents have been obtained. To obtain them, log in to the APM console and choose System Management > Access Keys in the navigation pane.
Figure 1 Obtaining an AK/SK
@@ -11,7 +11,7 @@
curl -O https://xxx/apm-javaagent-x.x.x.tar
- Run the tar command to decompress the JavaAgent package.
Example command:
tar -xvf apm-javaagent-x.x.x.tar
-
- Modify the apm.config file in the JavaAgent package. Configure master.address by referring to Access Address (master.address), and add the AK/SK to the configuration file, as shown in the following figure.
Figure 2 Adding the AK/SK
+
- Modify the apm.config file in the JavaAgent package. Configure master.address by referring to Access Addresses, and add the AK/SK to the configuration file, as shown in the following figure.
Figure 2 Adding the AK/SK
- Modify the startup script of the Java process.
Add the path of the apm-javaagent.jar package and the component name of the Java process to the end of the Java command in the service startup script.
Example of adding -javaagent parameters:
java -javaagent:/xxx/apm-javaagent/apm-javaagent.jar=appName={appName}
diff --git a/docs/apm/umn/apm_02_0005.html b/docs/apm/umn/apm_02_0005.html
new file mode 100644
index 00000000..ad9cd46f
--- /dev/null
+++ b/docs/apm/umn/apm_02_0005.html
@@ -0,0 +1,72 @@
+
+
+Installing Agents for the Java Applications Deployed in CCE Containers
+ - You are advised to install self-developed Agents for the Java applications deployed in CCE containers.
+
+ Prerequisites
+ - For details, see Regions and Endpoints.
- The AK/SK required for accessing JavaAgents have been obtained. To obtain them, log in to the APM console and choose System Management > Access Keys in the navigation pane.
+
+
+ Usage InstructionAPM only supports Java applications deployed on CCE. Table 1 describes the parameters.
+
+ Table 1 Parameters for configuring performance managementName
+ |
+Description
+ |
+
|---|
+
+Probe
+ |
+Select a target probe. Options: Disable/APM probe.
+ |
+
+Probe Version
+ |
+Version of the probe. You are advised to select a probe type based on the CPU architecture of the node where the workload is located.
+ |
+
+Probe Upgrade Policy
+ |
+Policy for the probe upgrade. The default value is Auto upgrade upon restart.
+- Automatic upgrade upon restart: The system downloads the probe image each time the pod is restarted.
- Manual upgrade: If a local image is available, it will be used. If no local image is available, the system downloads the probe image.
+ |
+
+APM Environment
+ |
+Enter an APM environment name. This parameter is optional.
+ |
+
+APM App
+ |
+Select an existing APM application.
+ |
+
+Sub-app
+ |
+Enter an APM sub-application. This parameter is optional.
+ |
+
+Access Key
+ |
+The system automatically obtains the APM key. For details, see Prerequisites.
+ |
+
+
+
+
+
+ Procedure- Log in to the CCE console. In the navigation pane, choose Workloads > Deployments or StatefulSets, and click Create Deployment or Create StatefulSet.
- In the APM Settings area on the Configure Advanced Settings page, select Java probe. The APM service will be enabled and a probe will be installed on the node.
Probes provide traces, topologies, SQL analysis, and stack tracing for Java workloads. A small number of resources will be consumed when you run probes.
+
+ - Set probe-related parameters.
- Monitoring Group: Enter a monitoring group name, for example, testapp. Select a group from the drop-down list if there are any.
- Probe Version: Select a probe version.
- Probe Upgrade Policy: By default, Automatic upgrade upon restart is selected.
- Automatic upgrade upon restart: The system downloads the probe image each time the pod is restarted.
- Manual upgrade: If a local image is available, it will be used. If no local image is available, the system downloads the probe image.
+
+ - After the application is started, wait for about 3 minutes. Then, the application data is displayed on the APM console. You can log in to the APM console and optimize the application performance through topology and tracing.
+
+ Latest Version
|
-Earlier Version
+ | Earlier Versions
|
diff --git a/docs/apm/umn/apm_02_0008.html b/docs/apm/umn/apm_02_0008.html
index 4125281d..cd6aee2c 100644
--- a/docs/apm/umn/apm_02_0008.html
+++ b/docs/apm/umn/apm_02_0008.html
@@ -1,16 +1,16 @@
-Access Address (master.address)
+Access Addresses
- Region
+Table 1 Access addresses of Enhanced AgentsRegion
|
-Access Address (master.address)
+ | Access Address
|
|---|
-eu-de
+ | eu-de
|
-https://100.125.40.55:41333
+ | https://100.125.40.55:41333
|
diff --git a/docs/apm/umn/apm_02_1002.html b/docs/apm/umn/apm_02_1002.html
index d5e3fd97..b5c17d41 100644
--- a/docs/apm/umn/apm_02_1002.html
+++ b/docs/apm/umn/apm_02_1002.html
@@ -10,7 +10,7 @@
- JavaAgent Download Addresses
-- Access Address (master.address)
+ - Access Addresses
diff --git a/docs/apm/umn/apm_07_0001.html b/docs/apm/umn/apm_07_0001.html
index db505050..340e507a 100644
--- a/docs/apm/umn/apm_07_0001.html
+++ b/docs/apm/umn/apm_07_0001.html
@@ -42,7 +42,7 @@
Agent Management
|
-Agent Management allows you to view the deployment and running statuses of the Agents that are connected to APM, and to stop, start, or delete them.
+ | 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
diff --git a/docs/apm/umn/apm_07_0002.html b/docs/apm/umn/apm_07_0002.html
index e9853415..899b281c 100644
--- a/docs/apm/umn/apm_07_0002.html
+++ b/docs/apm/umn/apm_07_0002.html
@@ -2,7 +2,7 @@
Application List
Application ListThe Applications page displays information such as components, environments, Agent status, and supported operations.
- - Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane on the left, choose Application Monitoring > Applications.
Figure 1 Application list
+- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane on the left, choose Application Monitoring > Applications.
Figure 1 Application list
Component|Environment: name of a component or environment. You can click the text in blue to go to the corresponding to component or environment page.
Agent Status: number of Agents in different statuses.
The following table describes the Agent statuses.
diff --git a/docs/apm/umn/apm_07_0004.html b/docs/apm/umn/apm_07_0004.html
index f4a41077..403c3652 100644
--- a/docs/apm/umn/apm_07_0004.html
+++ b/docs/apm/umn/apm_07_0004.html
@@ -7,8 +7,10 @@
- Collection period: A monitoring item has the same period attribute as a data collector. The default data collection period is 1 minute and cannot be changed.
- Monitoring item status: A monitoring item is enabled by default. You can disable it so that an Agent does not intercept or report the metric data. For details, see Enabling or Disabling a Monitoring Item.
- Collection status: Each collection instance or monitoring item has a collection status. If a collection error occurs, you can view it on the Collection Status tab page. A common error is that there are too many primary keys. As a result, data aggregation on the client is abnormal.
Monitoring Item TypesAgents automatically discover collection plug-ins and instantiate collectors to form monitoring items. Monitoring items are instantiated in an environment.
There are many types of collectors, which are hard to distinguish. The system backend groups collectors for easy data query.
+ The Metrics page displays only the involved monitoring item metrics of connected applications.
+
Based on collector functions, monitoring items can be classified into:
- - URL: Monitors the external services that call the current application.
- JVM: Monitors basic system performance metrics.
- Exception: Monitors application exceptions.
- Call: Monitors the external services called by the current application.
- SQL: Monitors database access.
- Cache: Monitors cache systems such as Redis and collects instruction-level metric data.
- Web Container: Monitors web containers such as Tomcat. Generally, the total number of threads, number of busy threads, and number of connections are collected to measure the overall system capacity.
- Message Queue: Monitors message systems such as Kafka and RabbitMQ, including the sender and receiver. The processing function at the receive end can generate trace information.
- Communication Protocol: Monitors communication protocols such as WebSocket.
+ - Topology: Displays the call relationships between services within a period. The statistics can be collected from the caller or the callee. You can also check the trend.
- URL: Monitors the external services that call the current application.
- JVM: Monitors basic system performance metrics.
- Exception: Monitors application exceptions.
- Call: Monitors the external services called by the current application.
- SQL: Monitors database access.
- Web Container: Monitors web containers such as Tomcat. Generally, the total number of threads, number of busy threads, and number of connections are collected to measure the overall system capacity.
Monitoring Item ConfigurationCollectors corresponding to monitoring items define collection parameters. You can modify collection parameters on the page as required. These parameters will be delivered to Agents with heartbeat parameters to change collection behaviors. By default, Redis instruction content is not collected for security purposes. If necessary, modify collection parameters to collect specific instruction data. Collection parameters can also be defined on environment tags. Collectors automatically inherit collection parameter attributes of corresponding environment tags. In this way, configuration is automated.
Application Monitoring Details
- The Metrics page displays only the involved monitoring item metrics of connected applications.
-
-
- Topology
diff --git a/docs/apm/umn/apm_07_0006.html b/docs/apm/umn/apm_07_0006.html
index 66ed9c51..724fd15e 100644
--- a/docs/apm/umn/apm_07_0006.html
+++ b/docs/apm/umn/apm_07_0006.html
@@ -3,11 +3,11 @@
URL
This function monitors the calls of the current application by external services. It includes URL, Dubbo server, CSE server, CSEProvider cluster, and FunctionGraph monitoring. This type of monitoring item demonstrates the actual external status of the entire service. For example, if the average response time of a URL is long, it means that external users take a long time to query the corresponding data.
This section focuses on URL monitoring.
- Going to the URL Page- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. On the URL tab page that is displayed, view URL monitoring information of all instances.Figure 1 Going to the URL page
+Going to the URL Page- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. On the URL tab page that is displayed, check URL monitoring information of all instances.Figure 1 Going to the URL page
- On the displayed URL tab page, select a target instance and monitoring item to view the monitoring data in different metric sets.
Figure 2 Selecting an instance and monitoring item
- Select a time range. Default: Last 20 minutes.
Options: Last 20 minutes, Last hour, Last 3 hours, Last 6 hours, Last day, Today, Yesterday, Last week, Last month, or Custom.
Figure 3 Selecting a time range
- - Click
 in the upper right corner of the list and select the metric data you want to view.
+ - Click in the upper right corner of the list and select the metric data you want to view.
Viewing URL Monitoring DataURL summary
For common URL calls, the system collects the metrics of each URL. For details about the metrics, see Table 1.
@@ -25,37 +25,37 @@
|
url
|
-URL
+ | URL.
|
method
|
-Request HTTP method
+ | Request HTTP method.
|
Calls
|
-Number of times that the URL is called
+ | Number of times that the URL is called.
|
Avg RT (ms)
|
-Average response time of the URL in a collection period
+ | Average response time of the URL in a collection period.
|
Errors
|
-Number of call errors of the URL
+ | Number of call errors of the URL.
|
Max Concurrency
|
-Maximum concurrency of the URL
+ | Maximum concurrency of the URL.
|
Max RT (ms)
|
-Maximum response time of the URL in a collection period
+ | Maximum response time of the URL in a collection period.
|
Apdex
@@ -65,32 +65,32 @@
|
0 ms–10 ms
|
-Number of requests with 0 ms–10 ms response time
+ | Number of requests with 0 ms–10 ms response time.
|
10 ms–100 ms
|
-Number of requests with 10 ms–100 ms response time
+ | Number of requests with 10 ms–100 ms response time.
|
100 ms–500 ms
|
-Number of requests with 100 ms–500 ms response time
+ | Number of requests with 100 ms–500 ms response time.
|
500 ms–1s
|
-Number of requests with 500 ms–1s response time
+ | Number of requests with 500 ms–1s response time.
|
1s–10s
|
-Number of requests with 1s–10s response time
+ | Number of requests with 1s–10s response time.
|
10s–n
|
-Number of requests with response time longer than 10s
+ | Number of requests with response time longer than 10s.
|
@@ -113,17 +113,17 @@
code
|
-Status code
+ | Status code.
|
Count
|
-Number of times that the status code has occurred
+ | Number of times that the status code occurred.
|
Latest URL
|
-Sample URL which returns the status code in a collection period
+ | Sample URL which returns the status code in a collection period.
|
@@ -146,22 +146,22 @@
Cluster ID
|
-Cluster ID of the caller
+ | Cluster ID of the caller.
|
Calls
|
-Number of times the cluster is called
+ | Number of times the cluster is called.
|
Avg RT (ms)
|
-Average response time in a collection period
+ | Average response time in a collection period.
|
Errors
|
-Number of times that the cluster fails to be called
+ | Number of times that the cluster fails to be called.
|
@@ -169,7 +169,7 @@
Click a number in blue (such as those in the Calls or Avg RT (ms) column) to view more details.
Overview
-View the metric trend of the selected instance on the Overview tab page. For details about the metrics, see Table 4.
+View the metric trend of the selected instance on the Overview tab page. For details about the metrics, see Table 4.
Figure 7 Overview under URL monitoring
Table 4 Overview metricsMetric Set
@@ -184,22 +184,22 @@
| Total Requests
|
-Total number of URL requests
+ | Total number of URL requests.
|
|---|
Avg RT (ms)
|
-Average response time of the URL
+ | Average response time of the URL.
|
Errors
|
-Total number of URL errors
+ | Total number of URL errors.
|
Apdex
|
-Users' satisfaction towards the URL
+ | Users' satisfaction with the URL.
|
diff --git a/docs/apm/umn/apm_07_0007.html b/docs/apm/umn/apm_07_0007.html
index 34d13f12..86987a02 100644
--- a/docs/apm/umn/apm_07_0007.html
+++ b/docs/apm/umn/apm_07_0007.html
@@ -2,7 +2,7 @@
JVM
This function monitors JVMInfo, JVMMonitor, GC, thread, and JavaMethod.
- Going to the JVM Page- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. - Click the JVM tab. By default, the JVMMonitor information of all instances is displayed.
Figure 1 Going to the JVM page
+Going to the JVM Page- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. - Click the JVM tab. By default, the JVMMonitor information of all instances is displayed.
Figure 1 Going to the JVM page
- On the displayed JVM tab page, select a target instance and monitoring item to view the monitoring data in different metric sets.
Figure 2 Selecting an instance and monitoring item
- Select a time range. Default: Last 20 minutes.
Options: Last 20 minutes, Last hour, Last 3 hours, Last 6 hours, Last day, Today, Yesterday, Last week, Last month, or Custom.
Figure 3 Selecting a time range
@@ -23,57 +23,57 @@
JavaAgent Version
|
-Java Agent version
+ | Java Agent version.
|
Started
|
-JVM startup time
+ | JVM startup time.
|
Startup Parameter
|
-JVM startup parameter
+ | JVM startup parameter.
|
Java Class Library Path
|
-Java class library path
+ | Java class library path.
|
Java Version
|
-Java version
+ | Java version.
|
Java Specification Version
|
-Java specification version
+ | Java specification version.
|
OS
|
-OS name
+ | OS name.
|
OS Version
|
-OS version
+ | OS version.
|
arch
|
-CPU architecture
+ | CPU architecture.
|
Processors
|
-Number of processors
+ | Number of processors.
|
SDK Version
|
-SDK version
+ | SDK version.
|
@@ -81,141 +81,142 @@
Viewing JVM Monitoring DataAPM monitors JVM metrics. For details about the metrics, see Table 2. JVM monitoring metrics are displayed in graphs, so that you can view and analyze JVM monitoring data more easily.
+
Figure 5 Viewing JVM monitoring data
- Table 2 JVM monitoring metricsMetric Set
+Table 2 JVM monitoring metricsMetric Set
|
-Metric
+ | Metric
|
-Description
+ | Description
|
|---|
-Thread
+ | Thread
|
-Current Threads
+ | Current Threads
|
-Number of current threads
+ | Number of current threads.
|
-Deadlock Threads
+ | Deadlock Threads
|
-Number of deadlock threads
+ | Number of deadlock threads.
|
-Daemon Threads
+ | Daemon Threads
|
-Number of daemon threads
+ | Number of daemon threads.
|
-Started Threads
+ | Started Threads
|
-Number of started threads
+ | Number of started threads.
|
-Peak Threads
+ | Peak Threads
|
-Peak number of threads
+ | Peak number of threads.
|
-Thread Status
+ | Thread Status
|
-Waiting Threads
+ | Waiting Threads
|
-Number of waiting threads
+ | Number of waiting threads.
|
-Terminated Threads
+ | Terminated Threads
|
-Number of threads in the terminated state
+ | Number of threads in the terminated state.
|
-Runnable Threads
+ | Runnable Threads
|
-Number of runnable threads
+ | Number of runnable threads.
|
-Blocked Threads
+ | Blocked Threads
|
-Number of blocked threads
+ | Number of blocked threads.
|
-New Threads
+ | New Threads
|
-Number of new threads
+ | Number of new threads.
|
-Timed Waiting Threads
+ | Timed Waiting Threads
|
-Number of threads that timed out
+ | Number of threads that timed out.
|
-Memory
+ | Memory
|
-Used Non-Heap Memory
+ | Used Non-Heap Memory
|
-Size of the used non-heap memory
+ | Size of the used non-heap memory.
|
-Used Heap Memory
+ | Used Heap Memory
|
-Size of the used heap memory
+ | Size of the used heap memory.
|
-Used Direct Memory
+ | Used Direct Memory
|
-Size of the used direct memory
+ | Size of the used direct memory.
|
-Class loading
+ | Class loading
|
-Current Classes
+ | Current Classes
|
-Number of current classes
+ | Number of current classes.
|
-Total Loaded Classes
+ | Total Loaded Classes
|
-Total number of loaded classes
+ | Total number of loaded classes.
|
-Unloaded Classes
+ | Unloaded Classes
|
-Number of unloaded classes
+ | Number of unloaded classes.
|
-Memory pool
+ | Memory pool
|
-committed(M)
+ | committed(M)
|
-Size of available memory
+ | Size of available memory.
|
-init(M)
+ | init(M)
|
-Size of the initialized memory
+ | Size of the initialized memory.
|
-max(M)
+ | max(M)
|
-Size of the maximum memory
+ | Size of the maximum memory.
|
-name
+ | name
|
-Memory pool name
+ | Memory pool name.
|
-used(M)
+ | used(M)
|
-Size of the used memory
+ | Size of the used memory.
|
-CPU
+ | CPU
|
-CPU Usage
+ | CPU Usage
|
-CPU usage of the Java process
+ | CPU usage of the Java process.
|
@@ -237,59 +238,59 @@
Full GC (times)
|
-Number of full GC times in a collection period
+ | Number of full GC times in a collection period.
|
Full GC Duration (ms)
|
-Full GC duration in a collection period
+ | Full GC duration in a collection period.
|
Young GC (times)
|
-Number of young GC times in a collection period
+ | Number of young GC times in a collection period.
|
Young GC Duration (ms)
|
-Young GC duration in a collection period
+ | Young GC duration in a collection period.
|
GC Details
|
GC Type
|
-GC type, which can be major or minor
+ | GC type, which can be major or minor.
|
GC Cause
|
-GC cause
+ | GC cause.
|
Count
|
-Number of times that GC has occurred
+ | Number of times that GC has occurred.
|
Total GC Duration (ms)
|
-GC duration
+ | GC duration.
|
Max GC Duration (ms)
|
-Time consumed by the slowest GC
+ | Time consumed by the slowest GC.
|
GC Recycler
|
-GC recycler name
+ | GC recycler name.
|
Slowest GC Details
|
-Details about the slowest GC
+ | Details about the slowest GC.
|
@@ -312,27 +313,27 @@
Thread Name
|
-Thread name
+ | Thread name.
|
Threads
|
-Number of threads
+ | Number of threads.
|
CPU Time (ms)
|
-Thread CPU time
+ | Thread CPU time.
|
Memory (MB)
|
-Memory (MB)
+ | Memory (MB).
|
Thread Stack
|
-Thread stack
+ | Thread stack.
|
@@ -355,67 +356,67 @@
Class
|
-Class
+ | Class of a Java method.
|
Method
|
-Method
+ | Method.
|
Calls
|
-Number of times that the method is called
+ | Number of times that the method is called.
|
Avg RT (ms)
|
-Average response time
+ | Average response time.
|
Errors
|
-Number of times that the method fails to be called
+ | Number of times that the method fails to be called.
|
Max Concurrency
|
-Maximum concurrency of the method
+ | Maximum concurrency of the method.
|
Max RT (ms)
|
-Maximum response time of the method
+ | Maximum response time of the method.
|
0 ms–10 ms
|
-Number of requests with 0 ms–10 ms response time
+ | Number of requests with 0 ms–10 ms response time.
|
10 ms–100 ms
|
-Number of requests with 10 ms–100 ms response time
+ | Number of requests with 10 ms–100 ms response time.
|
100 ms–500 ms
|
-Number of requests with 100 ms–500 ms response time
+ | Number of requests with 100 ms–500 ms response time.
|
500 ms–1s
|
-Number of requests with 500 ms–1s response time
+ | Number of requests with 500 ms–1s response time.
|
1s–10s
|
-Number of requests with 1s–10s response time
+ | Number of requests with 1s–10s response time.
|
10s–n
|
-Number of requests with response time longer than 10s
+ | Number of requests with response time longer than 10s.
|
diff --git a/docs/apm/umn/apm_07_0008.html b/docs/apm/umn/apm_07_0008.html
index 989fe2d5..83a3e1f4 100644
--- a/docs/apm/umn/apm_07_0008.html
+++ b/docs/apm/umn/apm_07_0008.html
@@ -2,7 +2,7 @@
Exception
This function monitors application exception logs. Take the monitoring of Java exception logs as an example. Once you use the log system to print logs, they will be collected by APM. The exception collection type varies according to the collector type.
- Viewing Exception Logs- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. - Click the Exception tab. By default, exception logs of all instances are displayed. For details about the metrics, see Table 1.
Figure 1 Exception monitoring data
+Viewing Exception Logs- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. - Click the Exception tab. By default, exception logs of all instances are displayed. For details about the metrics, see Table 1.
Figure 1 Exception monitoring data
Table 1 Exception and log parametersMetric Set
|
@@ -36,7 +36,7 @@
|---|
Message
|
-Message returned when the exception has occurred
+ | Message returned when the exception occurred
|
Error Stack
@@ -59,13 +59,13 @@
|
- Click a number in blue in the Total Exceptions column to view the trend of the total exceptions in a specified period.
- Click the blue text in the Message column to view the message time and content.
- Click Detail in the Error Stack column to view exception details.
- Click History in the Error Stack column to view the historical error stack list.
+ - Click a number in blue in the Total Exceptions column to view the trend of the total exceptions in a specified period.
- Click the blue text in the Message column to view the message time and content.
- Click Detail in the Error Stack column to view exception details.
- Click History in the Error Stack column to view the historical error stack list.
- - Click the blue text in the Version column to view details.
+ - Click the blue text in the Version column to view details.
- On the Exception tab page, select a target instance and then select Exception to view the exception monitoring data.
Figure 2 Selecting a target instance and exception
- Select a time range. Default: Last 20 minutes.
Options: Last 20 minutes, Last hour, Last 3 hours, Last 6 hours, Last day, Today, Yesterday, Last week, Last month, or Custom.
Figure 3 Selecting a time range
- - Click
 in the upper right corner of the list and select the metric data you want to view.
+ - Click
 in the upper right corner of the list and select the metric data you want to view.
diff --git a/docs/apm/umn/apm_07_0009.html b/docs/apm/umn/apm_07_0009.html
index d6eb0258..b33906c9 100644
--- a/docs/apm/umn/apm_07_0009.html
+++ b/docs/apm/umn/apm_07_0009.html
@@ -3,15 +3,15 @@
Call
This function monitors the calls of external services by the current application. It covers CSEConsumer, ApacheHttpClient, ApacheHttpAsyncClient, DubboConsumer, and HttpClient monitoring.
This section focuses on HttpClient monitoring.
- Going to the Call Page- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. - Click the Call tab. By default, the HttpClient monitoring information of all instances is displayed.
+
Going to the Call Page- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. - Click the Call tab. By default, the HttpClient monitoring information of all instances is displayed.
Figure 1 External call data
- On the displayed Call tab page, select a target instance and monitoring item to view the monitoring data in different metric sets.
Figure 2 Selecting an instance and monitoring item
- Select a time range. Default: Last 20 minutes.
Options: Last 20 minutes, Last hour, Last 3 hours, Last 6 hours, Last day, Today, Yesterday, Last week, Last month, or Custom.
Figure 3 Selecting a time range
- - Click
 in the upper right corner of the list and select the metric data you want to view.
+ - Click
 in the upper right corner of the list and select the metric data you want to view.
Viewing HttpClient Monitoring DataURL summary
- The HttpClient monitoring system collects the metrics of each URL. For details about the metrics, see Table 1. Click  in the upper right corner of the list and select the metric data you want to view.
+ The HttpClient monitoring system collects the metrics of each URL. For details about the metrics, see Table 1. Click  in the upper right corner of the list and select the metric data you want to view.
Figure 4 URL summary under HttpClient monitoring
Table 1 Parameters of URL summary under HttpClient monitoringMetric Set
@@ -26,77 +26,77 @@
| url
|
-Called URL
+ | Called URL.
|
|---|
method
|
-HTTP method of the URL
+ | HTTP method of the URL.
|
Calls
|
-Number of times that the URL is called
+ | Number of times that the URL is called.
|
Avg RT (ms)
|
-Average response time of the called URL
+ | Average response time of the called URL.
|
Errors
|
-Number of call errors of the URL
+ | Number of call errors of the URL.
|
Max Concurrency
|
-Maximum concurrency of the URL
+ | Maximum concurrency of the URL.
|
Max RT (ms)
|
-Maximum response time of the called URL
+ | Maximum response time of the called URL.
|
0 ms–10 ms
|
-Number of requests with 0 ms–10 ms response time
+ | Number of requests with 0 ms–10 ms response time.
|
10 ms–100 ms
|
-Number of requests with 10 ms–100 ms response time
+ | Number of requests with 10 ms–100 ms response time.
|
100 ms–500 ms
|
-Number of requests with 100 ms–500 ms response time
+ | Number of requests with 100 ms–500 ms response time.
|
500 ms–1s
|
-Number of requests with 500 ms–1s response time
+ | Number of requests with 500 ms–1s response time.
|
1s–10s
|
-Number of requests with 1s–10s response time
+ | Number of requests with 1s–10s response time.
|
10s–n
|
-Number of requests with response time longer than 10s
+ | Number of requests with response time longer than 10s.
|
Error Trace
|
-ID of the trace that encounters an error in a collection period
+ | ID of the trace that encounters an error in a collection period.
|
Slowest Trace
|
-ID of the slowest trace in a collection period
+ | ID of the slowest trace in a collection period.
|
@@ -119,62 +119,62 @@
envId
|
-Cluster ID of the called party
+ | Cluster ID of the called party.
|
-Calls
+ | hostUri
|
-Number of times that the cluster URL is called
+ | Host URL
|
-Avg RT (ms)
+ | Calls
|
-Average response time for calling the cluster URL
+ | Number of times that the cluster URL is called.
|
-Errors
+ | Avg RT (ms)
|
-Number of call errors of the URL
+ | Average response time for calling the cluster URL.
|
-Max RT (ms)
+ | Errors
|
-Maximum response time for calling the cluster URL
+ | Number of call errors of the URL.
|
-hostUri
+ | Max RT (ms)
|
-URI of the host
+ | Maximum response time for calling the cluster URL.
|
0 ms–10 ms
|
-Number of requests with 0 ms–10 ms response time
+ | Number of requests with 0 ms–10 ms response time.
|
10 ms–100 ms
|
-Number of requests with 10 ms–100 ms response time
+ | Number of requests with 10 ms–100 ms response time.
|
100 ms–500 ms
|
-Number of requests with 100 ms–500 ms response time
+ | Number of requests with 100 ms–500 ms response time.
|
500 ms–1s
|
-Number of requests with 500 ms–1s response time
+ | Number of requests with 500 ms–1s response time.
|
1s–10s
|
-Number of requests with 1s–10s response time
+ | Number of requests with 1s–10s response time.
|
10s–n
|
-Number of requests with response time longer than 10s
+ | Number of requests with response time longer than 10s.
|
@@ -197,17 +197,17 @@
code
|
-Status code
+ | Status code.
|
Count
|
-Number of times that the status code has occurred
+ | Number of times that the status code occurred.
|
Latest URL
|
-URL that returns the status code
+ | URL that returns the status code.
|
@@ -230,27 +230,27 @@
causeType
|
-Exception class
+ | Exception class.
|
exceptionType
|
-Exception type
+ | Exception type.
|
Count
|
-Number of times the exception has occurred
+ | Number of times the exception occurred.
|
Error Message
|
-Message returned when the exception has occurred
+ | Message returned when the exception occurred.
|
Error Stack
|
-Exception stack information
+ | Exception stack information.
|
@@ -274,7 +274,7 @@
Calls
|
-Total number of calls
+ | Total number of calls.
|
Avg RT (ms)
@@ -284,7 +284,7 @@
|
Errors
|
-Total number of errors
+ | Total number of errors.
|
diff --git a/docs/apm/umn/apm_07_0010.html b/docs/apm/umn/apm_07_0010.html
index c5d7dd27..6975b4d2 100644
--- a/docs/apm/umn/apm_07_0010.html
+++ b/docs/apm/umn/apm_07_0010.html
@@ -3,11 +3,11 @@
SQL
This function monitors database access. The databases that can be monitored include the C3P0, Cassandra, ClickHouse, DBCP, Druid, EsRestClient, GaussDB, Hikari, Jetcd, ObsClient, MySQL, PostgreSQL, Oracle, HBase, and MongoDB. APM collects details about executed statements to help you locate performance problems in code.
This section focuses on MySQL database monitoring.
- Going to the SQL Page- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. - Click the SQL tab. By default, the MySQL database information of all instances is displayed.
Figure 1 Going to the SQL page
+Going to the SQL Page- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. - Click the SQL tab. By default, the MySQL database information of all instances is displayed.
Figure 1 Going to the SQL page
- On the displayed SQL tab page, select a target instance and monitoring item to view the monitoring data in different metric sets.
Figure 2 Selecting an instance and monitoring item
- Select a time range. Default: Last 20 minutes.
Options: Last 20 minutes, Last hour, Last 3 hours, Last 6 hours, Last day, Today, Yesterday, Last week, Last month, or Custom.
Figure 3 Selecting a time range
- - Click
 in the upper right corner of the list and select the metric data you want to view.
+ - Click
 in the upper right corner of the list and select the metric data you want to view.
Viewing MySQL Database Monitoring DataSQL summary
APM can monitor MySQL databases by SQL. For details about the metrics, see Table 1. Click  in the upper right corner of the list and select the metric data you want to view.
@@ -25,87 +25,87 @@
sql
|
- Unique ID of the SQL statement, which is used for alarm configuration
+ | Unique ID of the SQL statement, which is used for alarm configuration.
|
SQL Statement
|
-SQL statement
+ | SQL statement.
|
Calls
|
-Number of times that the SQL statement is called
+ | Number of times that the SQL statement is called.
|
Avg RT (ms)
|
-Average response time (ms)
+ | Average response time (ms).
|
Errors
|
-Number of errors that the SQL statement encounters
+ | Number of errors that the SQL statement encounters.
|
Rows Read
|
-Number of read rows of the SQL statement
+ | Number of read rows of the SQL statement.
|
Rows Updated
|
-Number of updated rows of the SQL statement
+ | Number of updated rows of the SQL statement.
|
Max Concurrency
|
-Maximum concurrency of the SQL statement
+ | Maximum concurrency of the SQL statement.
|
Max RT (ms)
|
-Maximum response time of the SQL statement
+ | Maximum response time of the SQL statement.
|
0 ms–10 ms
|
-Number of requests with 0 ms–10 ms response time
+ | Number of requests with 0 ms–10 ms response time.
|
10 ms–100 ms
|
-Number of requests with 10 ms–100 ms response time
+ | Number of requests with 10 ms–100 ms response time.
|
100 ms–200 ms
|
-Number of requests with 100 ms–200 ms response time
+ | Number of requests with 100 ms–200 ms response time.
|
200 ms–1s
|
-Number of requests with 200 ms–1s response time
+ | Number of requests with 200 ms–1s response time.
|
1s–10s
|
-Number of requests with 1s–10s response time
+ | Number of requests with 1s–10s response time.
|
10s–n
|
-Number of requests with response time longer than 10s
+ | Number of requests with response time longer than 10s.
|
Slowest Trace
|
-ID of the slowest trace in a collection period
+ | ID of the slowest trace in a collection period.
|
Error Trace
|
-ID of the trace that encounters an error in a collection period
+ | ID of the trace that encounters an error in a collection period.
|
@@ -128,77 +128,77 @@
db
|
- Database name
+ | Database name.
|
Connections Created
|
-Number of connections created by the database
+ | Number of connections created by the database.
|
Connections Destroyed
|
-Number of the database's connections that have been destroyed
+ | Number of the database's connections that have been destroyed.
|
Avg RT (ms)
|
-Average response time (ms)
+ | Average response time (ms).
|
Calls
|
-Number of times that the database is called
+ | Number of times that the database is called.
|
Errors
|
-Number of errors that the database encounters
+ | Number of errors that the database encounters.
|
Rows Read
|
-Number of rows read from the database
+ | Number of rows read from the database.
|
Rows Updated
|
-Number of rows updated in the database
+ | Number of rows updated in the database.
|
Max RT (ms)
|
-Maximum response time of the database
+ | Maximum response time of the database.
|
0 ms–10 ms
|
-Number of requests with 0 ms–10 ms response time
+ | Number of requests with 0 ms–10 ms response time.
|
10 ms–100 ms
|
-Number of requests with 10 ms–100 ms response time
+ | Number of requests with 10 ms–100 ms response time.
|
100 ms–200 ms
|
-Number of requests with 100 ms–200 ms response time
+ | Number of requests with 100 ms–200 ms response time.
|
200 ms–1s
|
-Number of requests with 200 ms–1s response time
+ | Number of requests with 200 ms–1s response time.
|
1s–10s
|
-Number of requests with 1s–10s response time
+ | Number of requests with 1s–10s response time.
|
10s–n
|
-Number of requests with response time longer than 10s
+ | Number of requests with response time longer than 10s.
|
@@ -222,32 +222,32 @@
causeType
|
- Exception class
+ | Exception class.
|
exceptionType
|
-Exception type
+ | Exception type.
|
Count
|
-Number of exceptions
+ | Number of exceptions.
|
SQL
|
-SQL statement that encounters an exception
+ | SQL statement that encounters an exception.
|
Error Stack
|
-Exception stack information
+ | Exception stack information.
|
Message
|
-Error message
+ | Error message.
|
@@ -269,27 +269,27 @@
Calls
|
- Total number of calls
+ | Total number of calls.
|
Rows Read
|
-Total number of read rows
+ | Total number of read rows.
|
Avg RT (ms)
|
-Average response time (ms)
+ | Average response time (ms).
|
Errors
|
-Total number of errors
+ | Total number of errors.
|
Rows Updated
|
-Number of rows updated in the database
+ | Number of rows updated in the database.
|
@@ -313,161 +313,161 @@
Connection Address
|
- Connection address
+ | Connection address.
|
Driver
|
-Driver name
+ | Driver name.
|
Initialized Connections
|
-Number of initialized connections
+ | Number of initialized connections.
|
Min Idle Connections in Pool
|
-Minimum of idle connections in a pool
+ | Minimum of idle connections in a pool.
|
Max Idle Connections in Pool
|
-Maximum number of idle connections in a pool
+ | Maximum number of idle connections in a pool.
|
Max Connections in Pool
|
-Maximum number of connections in a pool
+ | Maximum number of connections in a pool.
|
Idle Connections
|
-Number of idle connections
+ | Number of idle connections.
|
Max Idle Connections
|
-Maximum number of idle connections
+ | Maximum number of idle connections.
|
Active Connections
|
-Number of active connections
+ | Number of active connections.
|
Max Active Connections
|
-Maximum number of active connections
+ | Maximum number of active connections.
|
Waiting Threads
|
-Number of waiting threads
+ | Number of waiting threads.
|
Max Waiting Threads
|
-Maximum number of waiting threads
+ | Maximum number of waiting threads.
|
Upper Limit for Waiting Threads
|
-Upper limit for waiting threads
+ | Upper limit for waiting threads.
|
Total Connections
|
-Total number of connections
+ | Total number of connections.
|
Connection details
|
Connection Address
|
-Connection address
+ | Connection address.
|
Calls
|
-Number of calls
+ | Number of calls.
|
Total RT (ms)
|
-Total response time (ms)
+ | Total response time (ms).
|
Avg RT (ms)
|
-Average response time (ms)
+ | Average response time (ms).
|
Errors
|
-Number of errors
+ | Number of errors.
|
Max Concurrency
|
-Maximum number of concurrent connections
+ | Maximum number of concurrent connections.
|
Max RT (ms)
|
-Maximum response time
+ | Maximum response time.
|
0 ms–10 ms
|
-Number of requests with 0 ms–10 ms response time
+ | Number of requests with 0 ms–10 ms response time.
|
10 ms–100 ms
|
-Number of requests with 10 ms–100 ms response time
+ | Number of requests with 10 ms–100 ms response time.
|
100 ms–500 ms
|
-Number of requests with 100 ms–500 ms response time
+ | Number of requests with 100 ms–500 ms response time.
|
500 ms–1s
|
-Number of requests with 500 ms–1s response time
+ | Number of requests with 500 ms–1s response time.
|
1s–10s
|
-Number of requests with 1s–10s response time
+ | Number of requests with 1s–10s response time.
|
10s–n
|
-Number of requests with response time longer than 10s
+ | Number of requests with response time longer than 10s.
|
Additional configuration
|
Connection Address
|
-Connection address
+ | Connection address.
|
Max Wait (ms)
|
-Maximum waiting time
+ | Maximum waiting time.
|
Test on Borrow
|
-Whether to verify the validity of a connection before obtaining it from the connection pool
+ | Whether to verify the validity of a connection before obtaining it from the connection pool.
|
Test on Return
|
-Whether to verify the validity of a connection when it is returned
+ | Whether to verify the validity of a connection when it is returned.
|
Test While Idle
@@ -477,7 +477,7 @@
|
Remove Abandoned
|
-Whether to automatically reclaim timeout connections
+ | Whether to automatically reclaim timeout connections.
|
Remove Abandoned TimeoutMillis (ms)
@@ -487,51 +487,51 @@
|
Remove Abandoned Count
|
-Number of timeout connection reclaims
+ | Number of timeout connection reclaims.
|
Min Evictable Idle TimeMillis (ms)
|
-Minimum idle time of a connection in the pool
+ | Minimum idle time of a connection in the pool.
|
Time Between EvictionRunsMillis (ms)
|
-Interval for checking the validity of idle connections
+ | Interval for checking the validity of idle connections.
|
Exception
|
causeType
|
-Exception class
+ | Exception class.
|
Exception Type
|
-Exception type
+ | Exception type.
|
Count
|
-Number of times the exception has occurred
+ | Number of times the exception occurred.
|
Error Message
|
-Message returned when the exception has occurred
+ | Message returned when the exception occurred.
|
Error Stack
|
-Exception stack information
+ | Exception stack information.
|
Version
|
Driver Version
|
-Driver version
+ | Driver version.
|
diff --git a/docs/apm/umn/apm_07_0012.html b/docs/apm/umn/apm_07_0012.html
index 09791db4..6128284b 100644
--- a/docs/apm/umn/apm_07_0012.html
+++ b/docs/apm/umn/apm_07_0012.html
@@ -4,11 +4,11 @@
You can define collection parameters for some collectors corresponding to monitoring items.
On the Monitoring Item tab page, only monitoring items related to the connected application are displayed.
- Configuring a Monitoring Item- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. The instance monitoring page is displayed. - Click the Monitoring Item tab.
- Locate the row that contains the target monitoring item and click Modify in the Operation column.
Figure 1 Configuring a monitoring item
+
-
diff --git a/docs/apm/umn/apm_07_0018.html b/docs/apm/umn/apm_07_0018.html
index c38086c2..08b42aab 100644
--- a/docs/apm/umn/apm_07_0018.html
+++ b/docs/apm/umn/apm_07_0018.html
@@ -8,7 +8,7 @@
The advantage of the preceding algorithm is that once the trace information is generated, the link is complete, helping you make correct decisions. If a large number of URLs are called, abnormal requests may fail to be collected. In this case, you can collect metrics to locate system exceptions.
Trace SearchThis function is used to search for span information, that is, the root event of a node. A trace can be found in multiple environments. For example, in the scenario where service A calls service B and then calls service C, the same trace may be found from services A, B, and C.
- - Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Tracing.
- Specify the following search criteria or add custom criteria to query traces.
+ - Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Tracing.
- Specify the following search criteria or add custom criteria to query traces.
Table 1 Search criteria of tracesSearch Criterion
|
Description
@@ -103,7 +103,7 @@
|
|---|
Custom Parameter
|
-If you have configured Key for Header Value Interception, Key for Parameter Value Interception, and Key for Cookie Value Interception for URL monitoring, you can set key=value to search, for example, httpMethod=POST.
+ | - Search for traces by call parameter. The format is key=value. Example: exceptionMsg=failed.
- Configure required parameters before you search for traces by custom parameter. For example, if you have configured Key for Header Value Interception, Key for Parameter Value Interception, and Key for Cookie Value Interception for URL monitoring, you can set key=value to search, for example, httpMethod=POST.
For details about how to configure URL monitoring, see Configuring the URL Monitoring Item.
|
No
@@ -129,6 +129,8 @@
Viewing Trace DetailsViewing Basic Information About the Trace Filtered Based on the Search Criteria
+ Only the traces of successful or failed requests can be displayed. The following uses Successful Request as an example. - Click the green button next to Successful Request, only the traces of successful requests are displayed. The red button next to Failed Request becomes dimmed.
- If you click the green button again, both the traces of successful and failed requests are displayed. The red button is no longer dimmed.
- The green and red buttons cannot be dimmed at the same time.
+ In the displayed trace list, click  next to the target trace to view its basic information, as shown in the following figure.
Figure 1 Basic information about a trace
Parameter description:
diff --git a/docs/apm/umn/apm_07_0019.html b/docs/apm/umn/apm_07_0019.html
index f6163e0d..17f9a5b8 100644
--- a/docs/apm/umn/apm_07_0019.html
+++ b/docs/apm/umn/apm_07_0019.html
@@ -4,7 +4,7 @@
On the tracing page, you can view the topology of a single call, as well as the overall topology between different services based on collected metric data. There are two types of application topologies:
- Single-component topology: topology of a single component under an environment. You can also view the call relationships of direct and indirect upstream and downstream components.
- Global application topology: topology of some or all components under an application.
Each line in the topology indicates the call relationship between services within a period. The statistics can be collected from the calling or called party. You can click a line to view the call trend on the right. The topology can also display the call relationships between middleware. On the topology, you can view the call relationships between services and check whether the calls between services are normal to quickly locate faults.
- Viewing the Topology of a Component- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the environment whose topology you want to view. - Click the Topology tab to view the call and dependency relationships of the component.
Click a line between components. The detailed data is displayed on the right.
+Viewing the Topology of a Component- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. - Click the Topology tab to view the call and dependency relationships of the component.
Click a line between components. The detailed data is displayed on the right.
Enable Display only calls between components to shield the calls of external components, or click Show All to display the calls between all components except the central node.
Figure 1 Viewing the topology of a component
diff --git a/docs/apm/umn/apm_07_0020.html b/docs/apm/umn/apm_07_0020.html
index f21eb028..9a5b9e0c 100644
--- a/docs/apm/umn/apm_07_0020.html
+++ b/docs/apm/umn/apm_07_0020.html
@@ -2,10 +2,10 @@
URL Tracing
You can view the topology of a single call, as well as the overall topology between different services. In some scenarios, the call relationships of an important business need to be traced. This process is called URL tracing. For example, to trace the API for creating online shopping orders. In APM, URL tracing consumes a large number of resources. Therefore, an entry URL will not be added for tracing by default. However, you can set that if necessary. APM has a limit on the total number of URLs added for tracing. It focuses on tracing the downstream calls for the APIs that are added for tracing. Through URL tracing, you can monitor the call relationships between important APIs and downstream services, and then detect problems more precisely.
-
|
Alarm Policy Type
|
-Options: Single-node and Aggregate. Single-node indicates single-instance metric alarms, and Aggregate indicates aggregated metric alarms of all instances under a component.
+ | Options: Single-node and Aggregate. Single-node indicates single-instance metric alarms, and Aggregate indicates aggregated metric alarms of all instances under a component.
|
Monitoring Item
@@ -92,7 +92,7 @@
| Notification Content
|
Alarm details, which contain up to 500 characters.
-- If Multi-Line Matching is enabled, the alarm notification content supports both Variable and Loop. If Multi-Line Matching is disabled, only Variable can be selected.
- Alarm notification content. You can customize the content or select metrics as required.
- Alarm details, which contain up to 500 characters.
- Select required metrics. Specifically, on the right of the page, click
 next to the target metric. The metric will then be displayed in the notification content.
+- If Multi-Line Matching is enabled, the alarm notification content supports both Variable and Loop. If Multi-Line Matching is disabled, only Variable can be selected.
- Alarm notification content. You can customize the content or select metrics as required.
- Alarm details, which contain up to 500 characters.
- Select required metrics. Specifically, on the right of the page, click next to the target metric. The metric will then be displayed in the notification content.
|
diff --git a/docs/apm/umn/apm_07_0025.html b/docs/apm/umn/apm_07_0025.html
index fc92b046..3bf2978e 100644
--- a/docs/apm/umn/apm_07_0025.html
+++ b/docs/apm/umn/apm_07_0025.html
@@ -2,10 +2,10 @@
Creating a Custom Alarm Policy
You can create a custom alarm policy for a single component.
- Procedure- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. The instance monitoring page is displayed. - Click the Alarm Policy tab.
- Click Add Custom Alarm Policy and set the alarm condition in the same way as that when you create an alarm template.
Figure 1 Creating a custom alarm policy
+
-Create an Alarm Policy Based on a Template- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. The instance monitoring page is displayed. - Click the Alarm Policy tab.
- In the template list, click Copy in the Operation column in the row that contains the template you want to copy.
Figure 2 Create an alarm policy based on a template
+Create an Alarm Policy Based on a Template- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. The instance monitoring page is displayed. - Click the Alarm Policy tab.
- In the template list, click Copy in the Operation column in the row that contains the template you want to copy.
Figure 2 Create an alarm policy based on a template
More OperationsAfter the alarm policy is created, perform the operations listed in Table 1 if needed.
diff --git a/docs/apm/umn/apm_07_0026.html b/docs/apm/umn/apm_07_0026.html
index 59d59995..4c570386 100644
--- a/docs/apm/umn/apm_07_0026.html
+++ b/docs/apm/umn/apm_07_0026.html
@@ -3,7 +3,7 @@
Alarm Notification
Alarms can be sent to specified terminals by SMS message, email, or function. In this way, you can obtain component exceptions in a timely manner and quickly rectify faults to avoid service loss. Ensure that you have the SMN permission. For details, see Simple Message Notification (SMN) User Guide.
If you do not create any notification object, no alarm notifications will be received. To view alarms, log in to the APM console and choose Alarm Center > Alarm List in the navigation pane.
- Creating a Notification Object- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click an application. The metric details page of the application is displayed.
- Click the Notifications tab.
- Click Add.
Figure 1 Creating a notification object
+Creating a Notification Object- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click an application. The metric details page of the application is displayed.
- Click the Notifications tab.
- Click Add.
Figure 1 Creating a notification object
- On the displayed page, specify Region and Topic, and determine whether to enable default notification. If it is enabled, alarm notifications will be sent based on the topic and region you specify.
- If no topic is available, create one.
- If default notification is enabled, alarms will be sent to the specified region when you create an alarm policy.
- Click Yes.
Agent Management
-APM Agents use bytecode enhancement technology to collect application performance data in real time. They run on the server where applications are deployed. Install Agents before using APM. For details, see Manually Installing Agents for Java Applications.
-
+- Introduction
+
- Operating Agents
- Upgrading Agents
diff --git a/docs/apm/umn/apm_07_0028.html b/docs/apm/umn/apm_07_0028.html
index d9c04b34..45ce165c 100644
--- a/docs/apm/umn/apm_07_0028.html
+++ b/docs/apm/umn/apm_07_0028.html
@@ -1,8 +1,8 @@
Operating Agents
-Agent Management allows you to view the deployment and running statuses of the Agents that are connected to APM, and to stop, start, or delete them.
- Viewing Agents- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Agent Management.
- View the Agent list.
- In the upper left corner of the page, select a target region and application.
- Set the search criteria and click
 in the search box in the upper right corner of the page to filter Agents.
+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.
+ Checking Agents- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Agent Management.
- Check the Agent list.
- In the upper left corner of the page, select a target region and application.
- Set the search criteria and click in the search box in the upper right corner of the page to filter Agents.
Figure 1 Viewing Agents
The following table describes the Agent statuses.
@@ -32,8 +32,8 @@
- Batch Operations- In the navigation pane, choose Application Monitoring > Agent Management.
- Click Operation.
Figure 2 Batch operations
- - Select the desired hosts, and click Disable, Enable, or Delete Agent to disable, enable, or delete the Agents for them.
Figure 3 Operating Agents in batches
+Batch Operations- In the navigation pane, choose Application Monitoring > Agent Management.
- Select target objects and click Operation.
Figure 2 Batch operations
+ - Select Disable Agent, Enable Agent, or Delete Agent.
Figure 3 Operating Agents in batches
- In the dialog box that is displayed, click Yes to disable, enable, or delete the Agents for the selected hosts.
Figure 4 Deleting Agents
Collection Center
Collection Center displays collectors in a centralized manner. You can view and manage various collectors, metrics, and collection parameters supported by APM.
- Viewing Collector Details- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Configuration Management > Collection Center.
All the supported collectors are displayed.
-
- In the collector list, click View Details in the Operation column in the row that contains the target collector. The collector details page is displayed.
Figure 1 Viewing collector details
+Viewing Collector Details- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Configuration Management > Collection Center.
All the supported collectors are displayed.
+
- In the collector list, click View Details in the Operation column in the row that contains the target collector. The collector details page is displayed.
Figure 1 Viewing collector details
- The collector details page consists of three modules: basic information, collection parameters, and metric set.
- Basic information
This module displays collector information such as collector name and type.
- Collection parameters
This module displays the custom parameter settings supported by the collector. The settings take effect after being delivered to JavaAgents and are used for custom collection.
- Metric sets
This module displays information about the metrics collected by the collector.
@@ -51,7 +51,7 @@
Character string
|
-Maximum length: 1024 characters
+ | Maximum length: 1,024 characters
|
CLOB
diff --git a/docs/apm/umn/apm_07_0034.html b/docs/apm/umn/apm_07_0034.html
index b7e13f23..c11456a7 100644
--- a/docs/apm/umn/apm_07_0034.html
+++ b/docs/apm/umn/apm_07_0034.html
@@ -1,7 +1,7 @@
Access Keys
-Access Key ID (AK) and Secret Access Key (SK) are your long-term identity credentials. JavaAgents report data with an AK. AK is used together with SK to sign requests cryptographically, ensuring that the requests are secret, complete, and correct.
+ Access Key ID (AK) and Secret Access Key (SK) are your long-term identity credentials. JavaAgents report data with an AK. An AK is used together with an SK to sign requests cryptographically, ensuring that the requests are secret, complete, and correct.
PrecautionsA user can create a maximum of two access keys with identical permissions and unlimited validity. Keep your access keys secure and change them periodically for security purposes. To change an access key, delete it and create a new one.
APM allows you to encrypt and decrypt the SK in the apm.config file.
The encryption and decryption process is as follows:
@@ -11,7 +11,7 @@
- Adding an Access Key- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose System Management > Access Keys.
- On the page that is displayed, click Add Access Key.
Figure 1 Adding an AK/SK
+Adding an Access Key- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose System Management > Access Keys.
- On the page that is displayed, click Add Access Key.
Figure 1 Adding an AK/SK
- Add an access key description and click Yes to generate an access key.
To modify the description, click Modify in the Operation column in the row that contains the target access key.
General Configuration
On the General Configuration page, you can determine whether to collect data through bytecode instrumentation, and specify the slow request threshold and maximum number of rows to collect.
- - Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose System Management > General Configuration.
Figure 1 Modifying general configuration
+- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose System Management > General Configuration.
Figure 1 Modifying general configuration
|
2024-06-30
+ | 2024-07-05
+ |
+1. Added JavaAgent Updates.
+2. Changed the navigation entrance of APM from Management & Deployment to Application.
+ |
+
+2024-06-30
|
This issue is the first official release.
|
diff --git a/docs/apm/umn/apm_07_0040.html b/docs/apm/umn/apm_07_0040.html
index df87f95a..ba8a26e6 100644
--- a/docs/apm/umn/apm_07_0040.html
+++ b/docs/apm/umn/apm_07_0040.html
@@ -2,7 +2,7 @@
Agent Count
APM can count the Agents used by tenants. You can view the number of Agents by time, region, or Agent type.
- - Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation tree, choose System Management > Agent Count.
Figure 1 Agent counting
+- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation tree, choose System Management > Agent Count.
Figure 1 Agent counting
- Current Agent: number of Agents used by the current tenant.
- Historical Agent: number of Agents used in each hour of today, yesterday, or a custom day.
Checking the Number of Agents Used by an Application- In the navigation pane, choose Application Monitoring > Metrics.
- On the displayed page, select an application to view. The Application Info tab page is displayed by default.
- Switch to the Agent Count tab page to view the number of Agents used by the current application.
Figure 2 Agent counting
diff --git a/docs/apm/umn/apm_07_0050.html b/docs/apm/umn/apm_07_0050.html
index 5474a0cd..f658f000 100644
--- a/docs/apm/umn/apm_07_0050.html
+++ b/docs/apm/umn/apm_07_0050.html
@@ -1,17 +1,11 @@
CMDB Management
-APM has a built-in CMDB for managing application structure information and related configurations. It involves the following concepts:
- - Application (global concept): a logical unit. An application can be an independent functional module. The same application information can be viewed in all regions.
- Sub-application (global concept): similar to a folder. There can be up to three layers of sub-applications under an application.
- Component (global concept): a program or microservice. It is generally used together with environments. It may contain one or more environments. For example, an order app can be deployed in the function test environment, pressure test environment, pre-release environment, or live network environment.
- Environment: Components or programs with different configurations are deployed in different environments. Each environment has its own region attribute. You can filter environments by region. You can also add one or more tags to an environment and filter environments by tag.
- Instance: a process in an environment. It is named in the format of "host name+IP address+instance name". An environment is usually deployed on different hosts or containers. If an environment is deployed on one host, differentiation by instance is supported.
- Environment tag: an attribute for filtering environments. Different environments may have the same tag. Tags carry public configuration capabilities. For example, the configuration set on a tag can be shared by the environments with the same tag. Tags defined for environments of one application cannot be applied to other applications.
- The following shows an example of the CMDB structure.
- Figure 1 CMDB structure
- The CMDB structure tree can be hidden.
- - Click Hide to hide the CMDB structure tree.
Figure 2 Hiding the CMDB structure tree
- - Go to the path above in the upper part of the page and select your target node.
Figure 3 Selecting a node
- - Click Expand to display the CMDB structure tree.
- Recommended Alarm Templates
APM provides recommended alarm templates.
- Using Recommended Alarm Templates- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click an application. The metric details page of the application is displayed.
- Choose Alarm Templates > Recommendation Template to view the configured alarm templates.
Figure 1 Viewing recommended alarm templates
+Using Recommended Alarm Templates- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click an application. The metric details page of the application is displayed.
- Choose Alarm Templates > Recommendation Template to view the configured alarm templates.
Figure 1 Viewing recommended alarm templates
- Click View Details in the Operation column in the row that contains the target alarm template.
Figure 2 Recommended template list
- Click Copy to copy the recommended template to the template list. You can customize the template name as required.
Figure 3 Copying an alarm template
- - Click Yes. The copied alarm template is displayed on the template list.
Figure 4 Returning to the alarm template page
+ - Click Yes. The copied alarm template is displayed on the template list.
Figure 4 Returning to the alarm template page
Figure 5 Returning to the alarm template page
- Click Modify in the Operation column and bind nodes to make the copied template to take effect.
Web Container
This function monitors web containers, including Tomcat. This section focuses on Tomcat monitoring.
- Going to the Web Container Page- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. - Click the Web Container tab. By default, the Tomcat monitoring information of all instances is displayed. For details about the metrics, see Table 1.
Figure 1 Going to the web container page
+Going to the Web Container Page- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. - Click the Web Container tab. By default, the Tomcat monitoring information of all instances is displayed. For details about the metrics, see Table 1.
Figure 1 Going to the web container page
Table 1 Tomcat monitoring parametersMetric Set
|
@@ -16,49 +16,49 @@
name
|
-Port name
+ | Port name.
|
|---|
Current Threads
|
-Number of current threads on the port
+ | Number of current threads on the port.
|
Busy Threads
|
-Number of busy threads on the port at the time of collection
+ | Number of busy threads on the port at the time of collection.
|
Peak Busy Threads
|
-Maximum number of busy threads on the port in a collection period
+ | Maximum number of busy threads on the port in a collection period.
|
Max Threads
|
-Maximum number of threads on the port
+ | Maximum number of threads on the port.
|
Max Connections
|
-Maximum number of connections on the port
+ | Maximum number of connections on the port.
|
Current Connections
|
-Number of current connections of the port at the time of collection
+ | Number of current connections of the port at the time of collection.
|
Peak Connections
|
-Maximum number of connections on the port in a collection period
+ | Maximum number of connections on the port in a collection period.
|
Version
|
Version
|
-Tomcat version
+ | Tomcat version.
|
@@ -68,7 +68,7 @@
- On the displayed Web Container tab page, select a target instance and monitoring item to view the monitoring data in different metric sets.
Figure 2 Selecting an instance and monitoring item
- Select a time range. Default: Last 20 minutes.
Options: Last 20 minutes, Last hour, Last 3 hours, Last 6 hours, Last day, Today, Yesterday, Last week, Last month, or Custom.
Figure 3 Selecting a time range
- - Click
 in the upper right corner of the list and select the metric data you want to view.
+- Click
 in the upper right corner of the list and select the metric data you want to view.
diff --git a/docs/apm/umn/apm_07_0067.html b/docs/apm/umn/apm_07_0067.html
index 43ff390c..b02d1eb8 100644
--- a/docs/apm/umn/apm_07_0067.html
+++ b/docs/apm/umn/apm_07_0067.html
@@ -2,12 +2,12 @@
Topology
The topology displays the call relationships between services within a period. The statistics can be collected from the caller or the callee. You can also view the trend. On the topology, you can view the call relationships between services and check whether the calls between services are normal to quickly locate faults. The application relationships, call data (service and instance metrics), and health status are clearly displayed.
- Viewing the Topology- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click
 next to the target environment. - Switch to the Topology tab page. The call trend of the selected instance is displayed.
Figure 1 Viewing the topology
+Viewing the Topology- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click next to the target environment.
- Switch to the Topology tab page. The call trend of the selected instance is displayed.
Figure 1 Viewing the topology
- Click
 next to Display only calls between components.Figure 2 Displaying only calls between components
When the button turns blue, only the calls between components are displayed.
Figure 3 Calls between components
- Click Show All to display all call relationships of the selected instance in a specified time range.
Figure 4 Showing all
- - Select the refresh mode and time. Default: Manual Refresh. In addition, Automatic refresh in 1 minute, Automatic refresh in 5 minutes, and Automatic refresh in 15 minutes are supported.
Figure 5 Selecting a refresh mode
+ - Click Reset Layout to restore to the initial topology.
- Select the refresh mode and time. Default: Manual Refresh. In addition, Automatic refresh in 1 minute, Automatic refresh in 5 minutes, and Automatic refresh in 15 minutes are supported.
Figure 5 Selecting a refresh mode
- Select a time dimension. Default: Last 20 minutes.
Options: Last 20 minutes, Last hour, Last 3 hours, Last 6 hours, Last day, Today, Yesterday, Last week, Last month, or Custom.
Figure 6 Selecting a time dimension
diff --git a/docs/apm/umn/apm_07_0151.html b/docs/apm/umn/apm_07_0151.html
index 63800713..c36eb043 100644
--- a/docs/apm/umn/apm_07_0151.html
+++ b/docs/apm/umn/apm_07_0151.html
@@ -1,7 +1,7 @@
Creating an Application
- - Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- Click
 on the right of Application Metric to create an application.Figure 1 Creating an application
+- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Metrics.
- Click on the right of Application Metric to create an application.
Figure 1 Creating an application
- In the displayed dialog box, set application parameters.
Table 1 Parameters for creating an applicationParameter
|
@@ -17,8 +17,8 @@
|---|
Display Name
|
-Display name of an application, which cannot be empty.
-Enter 1 to 128 characters. Only digits, letters, underscores (_), hyphens (-), brackets, and periods (.) are allowed.
+ | Application alias. The alias takes precedence over the application name to display.
+Enter 1 to 128 characters. Only digits, letters, underscores (_), hyphens (-), brackets, and periods (.) are allowed.
|
Enterprise Project
diff --git a/docs/apm/umn/apm_07_0152.html b/docs/apm/umn/apm_07_0152.html
index 4090b98b..5f8afcf2 100644
--- a/docs/apm/umn/apm_07_0152.html
+++ b/docs/apm/umn/apm_07_0152.html
@@ -1,7 +1,7 @@
Configuring an Application and Sub-application
-- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- Click
 next to the application or sub-application name in the tree.Figure 1 Configuring an application and sub-application
+- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Metrics.
- Click next to the application or sub-application name in the tree.
Figure 1 Configuring an application and sub-application
- Configure the application and sub-application according to Table 1.
Table 1 Parameters for configuring the application and sub-applicationOperation
|
diff --git a/docs/apm/umn/apm_07_0153.html b/docs/apm/umn/apm_07_0153.html
index c4e73316..fd3489d7 100644
--- a/docs/apm/umn/apm_07_0153.html
+++ b/docs/apm/umn/apm_07_0153.html
@@ -1,7 +1,7 @@
Creating a Sub-application
-- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- Click
 next to your target application in the tree.Figure 1 Creating a sub-application
+- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Metrics.
- Click next to your target application in the tree.
Figure 1 Creating a sub-application
- In the displayed dialog box, set sub-application parameters.
Table 1 Parameters for creating a sub-applicationParameter
|
diff --git a/docs/apm/umn/apm_07_0208.html b/docs/apm/umn/apm_07_0208.html
new file mode 100644
index 00000000..52527f33
--- /dev/null
+++ b/docs/apm/umn/apm_07_0208.html
@@ -0,0 +1,25 @@
+
+
+Introduction
+APM has a built-in CMDB for managing application structure information and related configurations. It involves the following concepts:
+ - Application (global concept): a logical unit. An application can be an independent functional module. The same application information can be viewed in all regions.
- Sub-application (global concept): similar to a folder. There can be up to three layers of sub-applications under an application.
- Component (global concept): a program or microservice. It is generally used together with environments. It may contain one or more environments. For example, an order app can be deployed in the function test environment, pressure test environment, pre-release environment, or live network environment.
- Environment: Components or programs with different configurations are deployed in different environments. Each environment has its own region attribute. You can filter environments by region. You can also add one or more tags to an environment and filter environments by tag.
- Instance: a process in an environment. It is named in the format of "host name+IP address+instance name". An environment is usually deployed on different hosts or containers. If an environment is deployed on one host, differentiation by instance is supported.
- Environment tag: an attribute for filtering environments. Different environments may have the same tag. Tags carry public configuration capabilities. For example, the configuration set on a tag can be shared by the environments with the same tag. Tags defined for environments of one application cannot be applied to other applications.
+ The following shows an example of the CMDB structure.
+ Figure 1 CMDB structure
+ The CMDB structure tree can be hidden.
+ - Click Hide to hide the CMDB structure tree.
Figure 2 Hiding the CMDB structure tree
+ - Go to the path above in the upper part of the page and select your target node.
Figure 3 Selecting a node
+ - Click Expand to display the CMDB structure tree.
+ Introduction
+APM Agents use bytecode enhancement technology to collect application performance data in real time. They run on the server where applications are deployed. Install Agents before using APM. For details, see Manually Installing Agents for Java Applications.
+ A global tag is used to set a collector corresponding to the monitoring item under all environments of an application.
Priority: Global tag collector configuration > Tag collector configuration > Collector configuration of a monitoring item under an environment
-Adding a Tag- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation pane, choose Application Monitoring > Metrics.
- In the navigation tree, select a target application.
- Click the Tags tab.
- Click Add Tag.
Figure 1 Adding a tag
+Adding a Tag- Log in to the management console.
- Click on the left and choose Application > Application Performance Management.
- In the navigation pane, choose Application Monitoring > Metrics.
- In the navigation tree, select a target application.
- Click the Tags tab.
- Click Add Tag.
Figure 1 Adding a tag
- On the page that is displayed, set Tag and Description, and select the environment to be associated.
Table 1 Tag parametersParameter
|
diff --git a/docs/apm/umn/apm_07_1018.html b/docs/apm/umn/apm_07_1018.html
index 0307f1be..c38b2d86 100644
--- a/docs/apm/umn/apm_07_1018.html
+++ b/docs/apm/umn/apm_07_1018.html
@@ -4,12 +4,12 @@
You can set policies to mask the data reported using APM.
APM will collect and store masked data. Do not upload privacy or sensitive data to APM. If you need to upload such data, encrypt it.
- Querying a Data Masking Configuration- Log in to the management console.
- Click
 on the left and choose Management & Deployment > Application Performance Management. - In the navigation tree on the left, choose Configuration Management > Data Masking and select your target node. The configuration information is displayed.
Figure 1 Viewing a data masking configuration
- - In the search box, enter a configuration name keyword and click the search icon or press Enter.
Figure 2 Searching for a configuration
+Querying a Data Masking Configuration- Log in to the management console.
- Click
 on the left and choose Application > Application Performance Management. - In the navigation tree on the left, choose Configuration Management > Data Masking and select your target node. The configuration information is displayed.
Figure 1 Viewing a data masking configuration
+ - In the search box, enter a configuration name keyword and click the search icon or press Enter.
Figure 2 Searching for a configuration
Adding a Data Masking Configuration- In the navigation tree on the left, choose Configuration Management > Data Masking and select your target node.
Figure 3 Configuring data masking
- - Click Add and set configuration parameters.
Figure 4 Adding a configuration
+Adding a Data Masking Configuration- In the navigation tree on the left, choose Configuration Management > Data Masking and select your target node.
Figure 3 Configuring data masking
+ - Click Add and set configuration parameters.
Figure 4 Adding a configuration
Table 1 Configuration parametersParameter
|
@@ -38,11 +38,11 @@
- Click Yes.
-Modifying a Data Masking Configuration- In the navigation tree on the left, choose Configuration Management > Data Masking and select your target node.
- Click Modify in the Operation column to modify the configuration.
Figure 5 Modifying the data masking configuration
+Modifying a Data Masking Configuration- In the navigation tree on the left, choose Configuration Management > Data Masking and select your target node.
- Click Modify in the Operation column to modify the configuration.
Figure 5 Modifying the data masking configuration
- Click Yes.
Deleting Data Masking Configurations- In the navigation tree on the left, choose Configuration Management > Data Masking and select your target node.
- Click Delete in the Operation column. In the displayed dialog box, click Yes to delete the configuration.
Figure 6 Deleting the data masking configuration
- - Select multiple data masking configurations and click Batch Delete above the list. In the displayed dialog box, click Yes to delete multiple data masking configurations at a time.
Figure 7 Deleting configurations in batches
+Deleting Data Masking Configurations- In the navigation tree on the left, choose Configuration Management > Data Masking and select your target node.
- Click Delete in the Operation column. In the displayed dialog box, click Yes to delete the configuration.
Figure 6 Deleting the data masking configuration
+ - Select multiple data masking configurations and click Batch Delete above the list. In the displayed dialog box, click Yes to delete multiple data masking configurations at a time.
Figure 7 Deleting configurations in batches
|---|
|---|
|---|
|---|
|
|
|---|
|
|---|
|
