diff --git a/docs/apm/umn/ALL_META.TXT.json b/docs/apm/umn/ALL_META.TXT.json
new file mode 100644
index 00000000..a35e979b
--- /dev/null
+++ b/docs/apm/umn/ALL_META.TXT.json
@@ -0,0 +1,2724 @@
+[
+ {
+ "dockw":"User Guide"
+ },
+ {
+ "uri":"apm_01_0001.html",
+ "node_id":"apm_01_0001.xml",
+ "product_code":"",
+ "code":"1",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"Service Overview",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Service Overview",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0002.html",
+ "node_id":"apm_01_0002.xml",
+ "product_code":"apm",
+ "code":"2",
+ "des":"In the cloud era, applications in the microservice architecture are increasingly diversified, bringing many application exceptions. Application O&M faces the following ch",
+ "doc_type":"usermanual",
+ "kw":"What Is APM,Service Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"What Is APM",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0003.html",
+ "node_id":"apm_01_0003.xml",
+ "product_code":"apm",
+ "code":"3",
+ "des":"APM manages cloud application performance. It provides application metric monitoring, tracing, application topology, URL tracing, intelligent alarm reporting, and tag/Age",
+ "doc_type":"usermanual",
+ "kw":"Functions,Service Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Functions",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0004.html",
+ "node_id":"apm_01_0004.xml",
+ "product_code":"apm",
+ "code":"4",
+ "des":"APM is widely used. The following lists some typical scenarios.Pain PointsIn the distributed microservice architecture, enterprises can develop diverse applications effic",
+ "doc_type":"usermanual",
+ "kw":"Application Scenarios,Service Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Application Scenarios",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0005.html",
+ "node_id":"apm_01_0005.xml",
+ "product_code":"apm",
+ "code":"5",
+ "des":"A topology graphically displays call and dependency relationships between applications. It is composed of circles, lines with arrows, and resources. Each line with an arr",
+ "doc_type":"usermanual",
+ "kw":"Basic Concepts,Service Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Basic Concepts",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0006.html",
+ "node_id":"apm_01_0006.xml",
+ "product_code":"apm",
+ "code":"6",
+ "des":"APM provides basic and enterprise editions and supports interconnection with Java applications. The following table lists the functions supported by each edition.The ente",
+ "doc_type":"productdesc",
+ "kw":"Edition Differences,Service Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "IsBot":"Yes",
+ "prodname":"apm",
+ "documenttype":"productdesc",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Edition Differences",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0007.html",
+ "node_id":"apm_01_0007.xml",
+ "product_code":"apm",
+ "code":"7",
+ "des":"If you need to assign different permissions to employees in your enterprise to access your APM resources, Identity and Access Management (IAM) is a good choice for fine-g",
+ "doc_type":"usermanual",
+ "kw":"Permissions Management,Service Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Permissions Management",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0013.html",
+ "node_id":"apm_01_0013.xml",
+ "product_code":"",
+ "code":"8",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"Metric Overview",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Metric Overview",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0015.html",
+ "node_id":"apm_01_0015.xml",
+ "product_code":"",
+ "code":"9",
+ "des":"This section describes the types, names, and meanings of exception metrics collected by APM.",
+ "doc_type":"",
+ "kw":"Exception,Metric Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Exception",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0016.html",
+ "node_id":"apm_01_0016.xml",
+ "product_code":"",
+ "code":"10",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"Basic Monitoring",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Basic Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0027.html",
+ "node_id":"apm_01_0027.xml",
+ "product_code":"",
+ "code":"11",
+ "des":"This section describes the types, names, and meanings of GC metrics collected by APM.",
+ "doc_type":"",
+ "kw":"GC Monitoring,Basic Monitoring,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"GC Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0028.html",
+ "node_id":"apm_01_0028.xml",
+ "product_code":"",
+ "code":"12",
+ "des":"This section describes the types, names, and meanings of JavaMethod metrics collected by APM.",
+ "doc_type":"",
+ "kw":"JavaMethod,Basic Monitoring,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"JavaMethod",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0029.html",
+ "node_id":"apm_01_0029.xml",
+ "product_code":"",
+ "code":"13",
+ "des":"This section describes the types, names, and meanings of JVM metrics collected by APM.",
+ "doc_type":"",
+ "kw":"JVM Monitoring,Basic Monitoring,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"JVM Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0030.html",
+ "node_id":"apm_01_0030.xml",
+ "product_code":"",
+ "code":"14",
+ "des":"This section describes the types, names, and meanings of JVMInfo metrics collected by APM.",
+ "doc_type":"",
+ "kw":"JVMInfo,Basic Monitoring,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"JVMInfo",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0031.html",
+ "node_id":"apm_01_0031.xml",
+ "product_code":"",
+ "code":"15",
+ "des":"This section describes the types, names, and meanings of Netty memory metrics collected by APM.",
+ "doc_type":"",
+ "kw":"Netty Memory,Basic Monitoring,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Netty Memory",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0032.html",
+ "node_id":"apm_01_0032.xml",
+ "product_code":"",
+ "code":"16",
+ "des":"This section describes the types, names, and meanings of thread metrics collected by APM.",
+ "doc_type":"",
+ "kw":"Threads,Basic Monitoring,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Threads",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0017.html",
+ "node_id":"apm_01_0017.xml",
+ "product_code":"",
+ "code":"17",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"Databases",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Databases",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0033.html",
+ "node_id":"apm_01_0033.xml",
+ "product_code":"",
+ "code":"18",
+ "des":"This section describes the types, names, and meanings of C3P0 connection pool metrics collected by APM.",
+ "doc_type":"",
+ "kw":"C3P0 Connection Pool Monitoring,Databases,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"C3P0 Connection Pool Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0034.html",
+ "node_id":"apm_01_0034.xml",
+ "product_code":"",
+ "code":"19",
+ "des":"This section describes the types, names, and meanings of Cassandra metrics collected by APM.",
+ "doc_type":"",
+ "kw":"Cassandra Monitoring,Databases,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Cassandra Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0035.html",
+ "node_id":"apm_01_0035.xml",
+ "product_code":"",
+ "code":"20",
+ "des":"This section describes the types, names, and meanings of ClickHouse database metrics collected by APM.",
+ "doc_type":"",
+ "kw":"ClickHouse Database,Databases,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"ClickHouse Database",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0036.html",
+ "node_id":"apm_01_0036.xml",
+ "product_code":"",
+ "code":"21",
+ "des":"This section describes the types, names, and meanings of DBCP connection pool metrics collected by APM.",
+ "doc_type":"",
+ "kw":"DBCP Connection Pool Monitoring,Databases,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"DBCP Connection Pool Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0037.html",
+ "node_id":"apm_01_0037.xml",
+ "product_code":"",
+ "code":"22",
+ "des":"This section describes the types, names, and meanings of Druid connection pool metrics collected by APM.",
+ "doc_type":"",
+ "kw":"Druid Connection Pool Monitoring,Databases,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Druid Connection Pool Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0038.html",
+ "node_id":"apm_01_0038.xml",
+ "product_code":"",
+ "code":"23",
+ "des":"This section describes the types, names, and meanings of EsRestClient metrics collected by APM.",
+ "doc_type":"",
+ "kw":"EsRestClient Monitoring,Databases,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"EsRestClient Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0039.html",
+ "node_id":"apm_01_0039.xml",
+ "product_code":"",
+ "code":"24",
+ "des":"This section describes the types, names, and meanings of GaussDB database metrics collected by APM.",
+ "doc_type":"",
+ "kw":"GaussDB Database,Databases,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"GaussDB Database",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0040.html",
+ "node_id":"apm_01_0040.xml",
+ "product_code":"",
+ "code":"25",
+ "des":"This section describes the types, names, and meanings of HBase metrics collected by APM.",
+ "doc_type":"",
+ "kw":"HBase Monitoring,Databases,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"HBase Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0041.html",
+ "node_id":"apm_01_0041.xml",
+ "product_code":"",
+ "code":"26",
+ "des":"This section describes the types, names, and meanings of Hikari connection pool metrics collected by APM.",
+ "doc_type":"",
+ "kw":"Hikari Connection Pool Monitoring,Databases,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Hikari Connection Pool Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0042.html",
+ "node_id":"apm_01_0042.xml",
+ "product_code":"",
+ "code":"27",
+ "des":"This section describes the types, names, and meanings of Jetcd metrics collected by APM.",
+ "doc_type":"",
+ "kw":"Jetcd Monitoring,Databases,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Jetcd Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0043.html",
+ "node_id":"apm_01_0043.xml",
+ "product_code":"",
+ "code":"28",
+ "des":"This section describes the types, names, and meanings of MongoDB metrics collected by APM.",
+ "doc_type":"",
+ "kw":"MongoDB Monitoring,Databases,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"MongoDB Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0044.html",
+ "node_id":"apm_01_0044.xml",
+ "product_code":"",
+ "code":"29",
+ "des":"This section describes the types, names, and meanings of MySQL database metrics collected by APM.",
+ "doc_type":"",
+ "kw":"MySQL Database,Databases,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"MySQL Database",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0045.html",
+ "node_id":"apm_01_0045.xml",
+ "product_code":"",
+ "code":"30",
+ "des":"This section describes the types, names, and meanings of ObsClient metrics collected by APM.",
+ "doc_type":"",
+ "kw":"ObsClient Monitoring,Databases,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"ObsClient Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0046.html",
+ "node_id":"apm_01_0046.xml",
+ "product_code":"",
+ "code":"31",
+ "des":"This section describes the types, names, and meanings of Oracle database metrics collected by APM.",
+ "doc_type":"",
+ "kw":"Oracle Database,Databases,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Oracle Database",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0047.html",
+ "node_id":"apm_01_0047.xml",
+ "product_code":"",
+ "code":"32",
+ "des":"This section describes the types, names, and meanings of PostgreSQL database metrics collected by APM.",
+ "doc_type":"",
+ "kw":"PostgreSQL Database,Databases,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"PostgreSQL Database",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0018.html",
+ "node_id":"apm_01_0018.xml",
+ "product_code":"",
+ "code":"33",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"URLs",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"URLs",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0048.html",
+ "node_id":"apm_01_0048.xml",
+ "product_code":"",
+ "code":"34",
+ "des":"This section describes the types, names, and meanings of CSEProvider cluster metrics collected by APM.",
+ "doc_type":"",
+ "kw":"CSEProvider Cluster Monitoring,URLs,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"CSEProvider Cluster Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0049.html",
+ "node_id":"apm_01_0049.xml",
+ "product_code":"",
+ "code":"35",
+ "des":"This section describes the types, names, and meanings of DubboProvider metrics collected by APM.",
+ "doc_type":"",
+ "kw":"DubboProvider Monitoring,URLs,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"DubboProvider Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0050.html",
+ "node_id":"apm_01_0050.xml",
+ "product_code":"",
+ "code":"36",
+ "des":"This section describes the types, names, and meanings of FunctionGraph metrics collected by APM.",
+ "doc_type":"",
+ "kw":"FunctionGraph Monitoring,URLs,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"FunctionGraph Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0052.html",
+ "node_id":"apm_01_0052.xml",
+ "product_code":"",
+ "code":"37",
+ "des":"This section describes the types, names, and meanings of URL metrics collected by APM.",
+ "doc_type":"",
+ "kw":"URL Monitoring,URLs,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"URL Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0019.html",
+ "node_id":"apm_01_0019.xml",
+ "product_code":"",
+ "code":"38",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"External Calls",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"External Calls",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0053.html",
+ "node_id":"apm_01_0053.xml",
+ "product_code":"",
+ "code":"39",
+ "des":"This section describes the types, names, and meanings of ApacheHttpAsyncClient connection pool metrics collected by APM.",
+ "doc_type":"",
+ "kw":"ApacheHttpAsyncClient Connection Pool,External Calls,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"ApacheHttpAsyncClient Connection Pool",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0054.html",
+ "node_id":"apm_01_0054.xml",
+ "product_code":"",
+ "code":"40",
+ "des":"This section describes the types, names, and meanings of ApacheHttpClient connection pool metrics collected by APM.",
+ "doc_type":"",
+ "kw":"ApacheHttpClient Connection Pool,External Calls,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"ApacheHttpClient Connection Pool",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0055.html",
+ "node_id":"apm_01_0055.xml",
+ "product_code":"",
+ "code":"41",
+ "des":"This section describes the types, names, and meanings of CSEConsumer cluster metrics collected by APM.",
+ "doc_type":"",
+ "kw":"CSEConsumer Cluster Monitoring,External Calls,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"CSEConsumer Cluster Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0056.html",
+ "node_id":"apm_01_0056.xml",
+ "product_code":"",
+ "code":"42",
+ "des":"This section describes the types, names, and meanings of DubboConsumer metrics collected by APM.",
+ "doc_type":"",
+ "kw":"DubboConsumer Monitoring,External Calls,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"DubboConsumer Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0051.html",
+ "node_id":"apm_01_0051.xml",
+ "product_code":"",
+ "code":"43",
+ "des":"This section describes the types, names, and meanings of HttpClient metrics collected by APM.",
+ "doc_type":"",
+ "kw":"HttpClient Monitoring,External Calls,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"HttpClient Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0020.html",
+ "node_id":"apm_01_0020.xml",
+ "product_code":"",
+ "code":"44",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"Cache",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Cache",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0057.html",
+ "node_id":"apm_01_0057.xml",
+ "product_code":"",
+ "code":"45",
+ "des":"This section describes the types, names, and meanings of Redis method call metrics collected by APM.",
+ "doc_type":"",
+ "kw":"Redis Method Call,Cache,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Redis Method Call",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0058.html",
+ "node_id":"apm_01_0058.xml",
+ "product_code":"",
+ "code":"46",
+ "des":"This section describes the types, names, and meanings of Jedis metrics collected by APM.",
+ "doc_type":"",
+ "kw":"Jedis Monitoring,Cache,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Jedis Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0059.html",
+ "node_id":"apm_01_0059.xml",
+ "product_code":"",
+ "code":"47",
+ "des":"This section describes the types, names, and meanings of Lettuce client metrics collected by APM.",
+ "doc_type":"",
+ "kw":"Lettuce Client,Cache,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Lettuce Client",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0021.html",
+ "node_id":"apm_01_0021.xml",
+ "product_code":"",
+ "code":"48",
+ "des":"This section describes the types, names, and meanings of Agent monitoring metrics collected by APM.",
+ "doc_type":"",
+ "kw":"Agent Monitoring,Metric Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Agent Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0022.html",
+ "node_id":"apm_01_0022.xml",
+ "product_code":"",
+ "code":"49",
+ "des":"This section describes the types, names, and meanings of Tomcat metrics collected by APM.",
+ "doc_type":"",
+ "kw":"Tomcat Monitoring,Metric Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Tomcat Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0023.html",
+ "node_id":"apm_01_0023.xml",
+ "product_code":"",
+ "code":"50",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"Message Queues",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Message Queues",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0061.html",
+ "node_id":"apm_01_0061.xml",
+ "product_code":"",
+ "code":"51",
+ "des":"This section describes the types, names, and meanings of KafkaConsumer metrics collected by APM.",
+ "doc_type":"",
+ "kw":"KafkaConsumer Monitoring,Message Queues,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"KafkaConsumer Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0062.html",
+ "node_id":"apm_01_0062.xml",
+ "product_code":"",
+ "code":"52",
+ "des":"This section describes the types, names, and meanings of KafkaProducer metrics collected by APM.",
+ "doc_type":"",
+ "kw":"KafkaProducer Monitoring,Message Queues,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"KafkaProducer Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0063.html",
+ "node_id":"apm_01_0063.xml",
+ "product_code":"",
+ "code":"53",
+ "des":"This section describes the types, names, and meanings of RabbitMqCommon metrics collected by APM.",
+ "doc_type":"",
+ "kw":"RabbitMqCommon Monitoring,Message Queues,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"RabbitMqCommon Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0064.html",
+ "node_id":"apm_01_0064.xml",
+ "product_code":"",
+ "code":"54",
+ "des":"This section describes the types, names, and meanings of RabbitMqConsumer metrics collected by APM.",
+ "doc_type":"",
+ "kw":"RabbitMqConsumer Monitoring,Message Queues,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"RabbitMqConsumer Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0065.html",
+ "node_id":"apm_01_0065.xml",
+ "product_code":"",
+ "code":"55",
+ "des":"This section describes the types, names, and meanings of RabbitMqProducer metrics collected by APM.",
+ "doc_type":"",
+ "kw":"RabbitMqProducer Monitoring,Message Queues,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"RabbitMqProducer Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0066.html",
+ "node_id":"apm_01_0066.xml",
+ "product_code":"",
+ "code":"56",
+ "des":"This section describes the types, names, and meanings of RocketMqConsumer metrics collected by APM.",
+ "doc_type":"",
+ "kw":"RocketMqConsumer Monitoring,Message Queues,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"RocketMqConsumer Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0067.html",
+ "node_id":"apm_01_0067.xml",
+ "product_code":"",
+ "code":"57",
+ "des":"This section describes the types, names, and meanings of RocketMqProducer metrics collected by APM.",
+ "doc_type":"",
+ "kw":"RocketMqProducer Monitoring,Message Queues,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"RocketMqProducer Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0024.html",
+ "node_id":"apm_01_0024.xml",
+ "product_code":"",
+ "code":"58",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"RPC",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"RPC",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0068.html",
+ "node_id":"apm_01_0068.xml",
+ "product_code":"",
+ "code":"59",
+ "des":"This section describes the types, names, and meanings of GRPCClient metrics collected by APM.",
+ "doc_type":"",
+ "kw":"GRPCClient Monitoring,RPC,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"GRPCClient Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0069.html",
+ "node_id":"apm_01_0069.xml",
+ "product_code":"",
+ "code":"60",
+ "des":"This section describes the types, names, and meanings of GRPCServer metrics collected by APM.",
+ "doc_type":"",
+ "kw":"GRPCServer Monitoring,RPC,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"GRPCServer Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0025.html",
+ "node_id":"apm_01_0025.xml",
+ "product_code":"",
+ "code":"61",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"IoT",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"IoT",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0070.html",
+ "node_id":"apm_01_0070.xml",
+ "product_code":"",
+ "code":"62",
+ "des":"This section describes the types, names, and meanings of CoapClient metrics collected by APM.",
+ "doc_type":"",
+ "kw":"CoapClient Monitoring,IoT,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"CoapClient Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0071.html",
+ "node_id":"apm_01_0071.xml",
+ "product_code":"",
+ "code":"63",
+ "des":"This section describes the types, names, and meanings of CoapServer metrics collected by APM.",
+ "doc_type":"",
+ "kw":"CoapServer Monitoring,IoT,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"CoapServer Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0072.html",
+ "node_id":"apm_01_0072.xml",
+ "product_code":"",
+ "code":"64",
+ "des":"This section describes the types, names, and meanings of MoquetteBroker metrics collected by APM.",
+ "doc_type":"",
+ "kw":"MoquetteBroker Monitoring,IoT,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"MoquetteBroker Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0073.html",
+ "node_id":"apm_01_0073.xml",
+ "product_code":"",
+ "code":"65",
+ "des":"This section describes the types, names, and meanings of PahoPublisher metrics collected by APM.",
+ "doc_type":"",
+ "kw":"PahoPublisher Monitoring,IoT,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"PahoPublisher Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0074.html",
+ "node_id":"apm_01_0074.xml",
+ "product_code":"",
+ "code":"66",
+ "des":"This section describes the types, names, and meanings of PahoSubscriber metrics collected by APM.",
+ "doc_type":"",
+ "kw":"PahoSubscriber Monitoring,IoT,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"PahoSubscriber Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0026.html",
+ "node_id":"apm_01_0026.xml",
+ "product_code":"",
+ "code":"67",
+ "des":"This section describes the types, names, and meanings of WebSocket metrics collected by APM.",
+ "doc_type":"",
+ "kw":"Communication Protocol,Metric Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Communication Protocol",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0008.html",
+ "node_id":"apm_01_0008.xml",
+ "product_code":"apm",
+ "code":"68",
+ "des":"All O&M data will be displayed on the APM console. Therefore, you are not advised to upload your privacy or sensitive data to APM. If you need to upload such data, encryp",
+ "doc_type":"productdesc",
+ "kw":"Privacy and Sensitive Information Protection Statement,Service Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "IsBot":"Yes",
+ "prodname":"apm",
+ "documenttype":"productdesc",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Privacy and Sensitive Information Protection Statement",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0009.html",
+ "node_id":"apm_01_0009.xml",
+ "product_code":"apm",
+ "code":"69",
+ "des":"After you enable data collection, APM collects application performance metrics and tracing data. Your personal privacy data will not be collected. The collected data will",
+ "doc_type":"productdesc",
+ "kw":"Data Collection,Service Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "IsBot":"Yes",
+ "prodname":"apm",
+ "documenttype":"productdesc",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Data Collection",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0010.html",
+ "node_id":"apm_01_0010.xml",
+ "product_code":"apm",
+ "code":"70",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"productdesc",
+ "kw":"Usage Restrictions",
+ "search_title":"",
+ "metedata":[
+ {
+ "IsBot":"Yes",
+ "prodname":"apm",
+ "documenttype":"productdesc",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Usage Restrictions",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_0094.html",
+ "node_id":"apm_01_0094.xml",
+ "product_code":"",
+ "code":"71",
+ "des":"Currently, APM can connect to Java applications. APM supports multiple mainstream Java frameworks, web servers, communications protocols, and databases.Java components an",
+ "doc_type":"",
+ "kw":"Java,Usage Restrictions,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Java",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_02_1002.html",
+ "node_id":"apm_02_1002.xml",
+ "product_code":"",
+ "code":"72",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"Getting Started",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Getting Started",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_02_0001.html",
+ "node_id":"apm_02_0001.xml",
+ "product_code":"apm",
+ "code":"73",
+ "des":"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 Differen",
+ "doc_type":"usermanual",
+ "kw":"Enabling APM,Getting Started,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"apm",
+ "documenttype":"usermanual",
+ "opensource":"true",
+ "IsMulti":"Yes",
+ "IsBot":"Yes"
+ }
+ ],
+ "title":"Enabling APM",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_02_0002.html",
+ "node_id":"apm_02_0002.xml",
+ "product_code":"apm",
+ "code":"74",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Monitoring Java Applications",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"apm",
+ "documenttype":"usermanual",
+ "opensource":"true",
+ "IsMulti":"Yes",
+ "IsBot":"Yes"
+ }
+ ],
+ "title":"Monitoring Java Applications",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_02_0003.html",
+ "node_id":"apm_02_0003.xml",
+ "product_code":"apm",
+ "code":"75",
+ "des":"The network between your host and APM is normal.You can run the Telnet command to check the network.",
+ "doc_type":"usermanual",
+ "kw":"Connecting Agents,Monitoring Java Applications,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"apm",
+ "documenttype":"usermanual",
+ "opensource":"true",
+ "IsMulti":"Yes",
+ "IsBot":"Yes"
+ }
+ ],
+ "title":"Connecting Agents",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_02_0004.html",
+ "node_id":"apm_02_0004.xml",
+ "product_code":"apm",
+ "code":"76",
+ "des":"The 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.The AK/SK required",
+ "doc_type":"usermanual",
+ "kw":"Manually Installing Agents for Java Applications,Monitoring Java Applications,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"apm",
+ "documenttype":"usermanual",
+ "opensource":"true",
+ "IsMulti":"Yes",
+ "IsBot":"Yes"
+ }
+ ],
+ "title":"Manually Installing Agents for Java Applications",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_02_0007.html",
+ "node_id":"apm_02_0007.xml",
+ "product_code":"apm",
+ "code":"77",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"JavaAgent Download Addresses,Getting Started,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"apm",
+ "documenttype":"usermanual",
+ "opensource":"true",
+ "IsMulti":"Yes",
+ "IsBot":"Yes"
+ }
+ ],
+ "title":"JavaAgent Download Addresses",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_02_0008.html",
+ "node_id":"apm_02_0008.xml",
+ "product_code":"apm",
+ "code":"78",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Access Address (master.address),Getting Started,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"apm",
+ "documenttype":"usermanual",
+ "opensource":"true",
+ "IsMulti":"Yes",
+ "IsBot":"Yes"
+ }
+ ],
+ "title":"Access Address (master.address)",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0001.html",
+ "node_id":"apm_07_0001.xml",
+ "product_code":"apm",
+ "code":"79",
+ "des":"This document describes how to use Application Performance Management (APM).",
+ "doc_type":"usermanual",
+ "kw":"Before You Start,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Before You Start",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0002.html",
+ "node_id":"apm_07_0002.xml",
+ "product_code":"",
+ "code":"80",
+ "des":"The Applications page displays information such as components, environments, Agent status, and supported operations.Component|Environment: name of a component or environm",
+ "doc_type":"",
+ "kw":"Application List,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Application List",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0050.html",
+ "node_id":"apm_07_0050.xml",
+ "product_code":"apm",
+ "code":"81",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"CMDB Management",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"CMDB Management",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0151.html",
+ "node_id":"apm_07_0151.xml",
+ "product_code":"",
+ "code":"82",
+ "des":"After an application is created, connect it to APM for monitoring.",
+ "doc_type":"",
+ "kw":"Creating an Application,CMDB Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Creating an Application",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0153.html",
+ "node_id":"apm_07_0153.xml",
+ "product_code":"",
+ "code":"83",
+ "des":"A maximum of three layers of sub-applications can be created.",
+ "doc_type":"",
+ "kw":"Creating a Sub-application,CMDB Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Creating a Sub-application",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0152.html",
+ "node_id":"apm_07_0152.xml",
+ "product_code":"",
+ "code":"84",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"Configuring an Application and Sub-application,CMDB Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring an Application and Sub-application",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0003.html",
+ "node_id":"apm_07_0003.xml",
+ "product_code":"apm",
+ "code":"85",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Application Metric Monitoring",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Application Metric Monitoring",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0004.html",
+ "node_id":"apm_07_0004.xml",
+ "product_code":"apm",
+ "code":"86",
+ "des":"APM Agents periodically collect performance metric data to measure the overall health status of applications. They can collect the metric data of JVM, GC, service calls, ",
+ "doc_type":"usermanual",
+ "kw":"Overview,Application Metric Monitoring,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Overview",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0005.html",
+ "node_id":"apm_07_0005.xml",
+ "product_code":"apm",
+ "code":"87",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Application Monitoring Details",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Application Monitoring Details",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0067.html",
+ "node_id":"apm_07_0067.xml",
+ "product_code":"",
+ "code":"88",
+ "des":"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.",
+ "doc_type":"",
+ "kw":"Topology,Application Monitoring Details,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Topology",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0006.html",
+ "node_id":"apm_07_0006.xml",
+ "product_code":"apm",
+ "code":"89",
+ "des":"This function monitors the calls of the current application by external services. It includes URL, Dubbo server, CSE server, CSEProvider cluster, and FunctionGraph monito",
+ "doc_type":"usermanual",
+ "kw":"URL,Application Monitoring Details,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"URL",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0007.html",
+ "node_id":"apm_07_0007.xml",
+ "product_code":"apm",
+ "code":"90",
+ "des":"This function monitors JVMInfo, JVMMonitor, GC, thread, and JavaMethod.Options: Last 20 minutes, Last hour, Last 3 hours, Last 6 hours, Last day, Today, Yesterday, Last w",
+ "doc_type":"usermanual",
+ "kw":"JVM,Application Monitoring Details,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"JVM",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0008.html",
+ "node_id":"apm_07_0008.xml",
+ "product_code":"apm",
+ "code":"91",
+ "des":"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 colle",
+ "doc_type":"usermanual",
+ "kw":"Exception,Application Monitoring Details,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Exception",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0009.html",
+ "node_id":"apm_07_0009.xml",
+ "product_code":"apm",
+ "code":"92",
+ "des":"This function monitors the calls of external services by the current application. It covers CSEConsumer, ApacheHttpClient, ApacheHttpAsyncClient, DubboConsumer, and HttpC",
+ "doc_type":"usermanual",
+ "kw":"Call,Application Monitoring Details,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Call",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0010.html",
+ "node_id":"apm_07_0010.xml",
+ "product_code":"apm",
+ "code":"93",
+ "des":"This function monitors database access. The databases that can be monitored include the C3P0, Cassandra, ClickHouse, DBCP, Druid, EsRestClient, GaussDB, Hikari, Jetcd, Ob",
+ "doc_type":"usermanual",
+ "kw":"SQL,Application Monitoring Details,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"SQL",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0061.html",
+ "node_id":"apm_07_0061.xml",
+ "product_code":"",
+ "code":"94",
+ "des":"This function monitors web containers, including Tomcat. This section focuses on Tomcat monitoring.Click a number in blue (such as those in the Current Threads, Busy Thre",
+ "doc_type":"",
+ "kw":"Web Container,Application Monitoring Details,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Web Container",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0011.html",
+ "node_id":"apm_07_0011.xml",
+ "product_code":"apm",
+ "code":"95",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Application Monitoring Configuration",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Application Monitoring Configuration",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0012.html",
+ "node_id":"apm_07_0012.xml",
+ "product_code":"apm",
+ "code":"96",
+ "des":"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",
+ "doc_type":"usermanual",
+ "kw":"Configuration Details,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Configuration Details",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0013.html",
+ "node_id":"apm_07_0013.xml",
+ "product_code":"apm",
+ "code":"97",
+ "des":"On the Modify MySQL Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.Collect Original SQL: ",
+ "doc_type":"usermanual",
+ "kw":"Configuring the MySQL Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Configuring the MySQL Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0014.html",
+ "node_id":"apm_07_0014.xml",
+ "product_code":"apm",
+ "code":"98",
+ "des":"On the Modify HttpClient Monitoring Configuration page, set the following URL normalization parameters:Collection Interval: The default value is 60s and cannot be changed",
+ "doc_type":"usermanual",
+ "kw":"Configuring the HttpClient Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Configuring the HttpClient Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0015.html",
+ "node_id":"apm_07_0015.xml",
+ "product_code":"apm",
+ "code":"99",
+ "des":"On the Modify URL Monitoring Configuration page, set the following parameters:For security purposes, do not contain sensitive data in headers, URL parameters, cookies, or",
+ "doc_type":"usermanual",
+ "kw":"Configuring the URL Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Configuring the URL Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0016.html",
+ "node_id":"apm_07_0016.xml",
+ "product_code":"apm",
+ "code":"100",
+ "des":"On the Modify JavaMethod Monitoring Configuration page, set method interception parameters.Collection Interval: The default value is 60s and cannot be changed.Method Inte",
+ "doc_type":"usermanual",
+ "kw":"Configuring the JavaMethod Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Configuring the JavaMethod Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0048.html",
+ "node_id":"apm_07_0048.xml",
+ "product_code":"",
+ "code":"101",
+ "des":"On the Modify Druid Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.TraceReportTimeSpanThr",
+ "doc_type":"",
+ "kw":"Configuring the Druid Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the Druid Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0047.html",
+ "node_id":"apm_07_0047.xml",
+ "product_code":"",
+ "code":"102",
+ "des":"On the Modify ApacheHttpAsyncClient Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.",
+ "doc_type":"",
+ "kw":"Configuring the ApacheHttpAsyncClient Monitoring Item,Application Monitoring Configuration,User Guid",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the ApacheHttpAsyncClient Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0046.html",
+ "node_id":"apm_07_0046.xml",
+ "product_code":"",
+ "code":"103",
+ "des":"On the Modify Redis Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.Parameter Parsing: The",
+ "doc_type":"",
+ "kw":"Configuring the Redis Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the Redis Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0045.html",
+ "node_id":"apm_07_0045.xml",
+ "product_code":"",
+ "code":"104",
+ "des":"On the Modify Jedis Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "doc_type":"",
+ "kw":"Configuring the Jedis Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the Jedis Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0044.html",
+ "node_id":"apm_07_0044.xml",
+ "product_code":"",
+ "code":"105",
+ "des":"On the Modify HBase Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "doc_type":"",
+ "kw":"Configuring the HBase Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the HBase Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0043.html",
+ "node_id":"apm_07_0043.xml",
+ "product_code":"",
+ "code":"106",
+ "des":"On the Modify ApacheHttpClient Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "doc_type":"",
+ "kw":"Configuring the ApacheHttpClient Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the ApacheHttpClient Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0042.html",
+ "node_id":"apm_07_0042.xml",
+ "product_code":"",
+ "code":"107",
+ "des":"On the Modify Tomcat Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "doc_type":"",
+ "kw":"Configuring the Tomcat Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the Tomcat Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0041.html",
+ "node_id":"apm_07_0041.xml",
+ "product_code":"",
+ "code":"108",
+ "des":"On the Modify EsRestClient Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.Index Normalizat",
+ "doc_type":"",
+ "kw":"Configuring the EsRestClient Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the EsRestClient Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0049.html",
+ "node_id":"apm_07_0049.xml",
+ "product_code":"",
+ "code":"109",
+ "des":"On the Modify WebSocket Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "doc_type":"",
+ "kw":"Configuring the WebSocket Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the WebSocket Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0053.html",
+ "node_id":"apm_07_0053.xml",
+ "product_code":"",
+ "code":"110",
+ "des":"On the Modify KafkaProducer Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "doc_type":"",
+ "kw":"Configuring the KafkaProducer Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the KafkaProducer Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0054.html",
+ "node_id":"apm_07_0054.xml",
+ "product_code":"",
+ "code":"111",
+ "des":"On the Modify Hikari Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.TraceReportTimeSpanTh",
+ "doc_type":"",
+ "kw":"Configuring the Hikari Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the Hikari Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0055.html",
+ "node_id":"apm_07_0055.xml",
+ "product_code":"",
+ "code":"112",
+ "des":"On the Modify Exception Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.Determine Trace Ex",
+ "doc_type":"",
+ "kw":"Configuring the Exception Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the Exception Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0056.html",
+ "node_id":"apm_07_0056.xml",
+ "product_code":"",
+ "code":"113",
+ "des":"On the Modify Thread Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.",
+ "doc_type":"",
+ "kw":"Configuring the Thread Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the Thread Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0057.html",
+ "node_id":"apm_07_0057.xml",
+ "product_code":"",
+ "code":"114",
+ "des":"On the Modify GC Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "doc_type":"",
+ "kw":"Configuring the GC Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the GC Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0058.html",
+ "node_id":"apm_07_0058.xml",
+ "product_code":"",
+ "code":"115",
+ "des":"On the Modify JVMInfo Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "doc_type":"",
+ "kw":"Configuring the JVMInfo Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the JVMInfo Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0064.html",
+ "node_id":"apm_07_0064.xml",
+ "product_code":"",
+ "code":"116",
+ "des":"On the Modify JVMMonitor Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.Call Chain Stack ",
+ "doc_type":"",
+ "kw":"Configuring the JVMMonitor Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring the JVMMonitor Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0065.html",
+ "node_id":"apm_07_0065.xml",
+ "product_code":"",
+ "code":"117",
+ "des":"On the Modify ProbeInfo Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "doc_type":"",
+ "kw":"Configuring ProbeInfo Monitoring Item,Application Monitoring Configuration,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring ProbeInfo Monitoring Item",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0017.html",
+ "node_id":"apm_07_0017.xml",
+ "product_code":"apm",
+ "code":"118",
+ "des":"APM supports summary tables, trend graphs, latest data tables, and original data tables.Summary table: records the summary calculation results based on the primary key me",
+ "doc_type":"usermanual",
+ "kw":"Monitoring Item Views,Application Metric Monitoring,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Monitoring Item Views",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0018.html",
+ "node_id":"apm_07_0018.xml",
+ "product_code":"apm",
+ "code":"119",
+ "des":"When the calls between enterprise microservices are complex, APM Agents sample some requests, and intercept corresponding requests and subsequent call information. For ex",
+ "doc_type":"usermanual",
+ "kw":"Tracing,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Tracing",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0019.html",
+ "node_id":"apm_07_0019.xml",
+ "product_code":"apm",
+ "code":"120",
+ "des":"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 ",
+ "doc_type":"usermanual",
+ "kw":"Application Topology,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Application Topology",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0020.html",
+ "node_id":"apm_07_0020.xml",
+ "product_code":"apm",
+ "code":"121",
+ "des":"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",
+ "doc_type":"usermanual",
+ "kw":"URL Tracing,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"URL Tracing",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0027.html",
+ "node_id":"apm_07_0027.xml",
+ "product_code":"apm",
+ "code":"122",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Agent Management",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Agent Management",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0028.html",
+ "node_id":"apm_07_0028.xml",
+ "product_code":"apm",
+ "code":"123",
+ "des":"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.In the upper left corn",
+ "doc_type":"usermanual",
+ "kw":"Operating Agents,Agent Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Operating Agents",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0029.html",
+ "node_id":"apm_07_0029.xml",
+ "product_code":"apm",
+ "code":"124",
+ "des":"Update Agent versions according to the following procedure.To upgrade the manually installed Agent, download the new Agent by referring to JavaAgent Download Addresses. F",
+ "doc_type":"usermanual",
+ "kw":"Upgrading Agents,Agent Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Upgrading Agents",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_1017.html",
+ "node_id":"apm_07_1017.xml",
+ "product_code":"apm",
+ "code":"125",
+ "des":"You can add tags for different environments and applications for easy management.Tag management covers tags and global tags.A tag is used to set a collector corresponding",
+ "doc_type":"usermanual",
+ "kw":"Managing Tags,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Managing Tags",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0021.html",
+ "node_id":"apm_07_0021.xml",
+ "product_code":"apm",
+ "code":"126",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Alarm Management",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Alarm Management",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0022.html",
+ "node_id":"apm_07_0022.xml",
+ "product_code":"apm",
+ "code":"127",
+ "des":"Alarms are reported by services connected to APM Agents when specified conditions are met. You can learn about service exceptions in a timely manner and quickly rectify f",
+ "doc_type":"usermanual",
+ "kw":"Alarm List,Alarm Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Alarm List",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0023.html",
+ "node_id":"apm_07_0023.xml",
+ "product_code":"apm",
+ "code":"128",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Alarm Policies",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Alarm Policies",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0024.html",
+ "node_id":"apm_07_0024.xml",
+ "product_code":"apm",
+ "code":"129",
+ "des":"APM allows you to configure alarm templates. You can create multiple alarm policies under a template and bind them to nodes.Enter basic information and then click Next.Te",
+ "doc_type":"usermanual",
+ "kw":"Configuring an Alarm Template,Alarm Policies,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Configuring an Alarm Template",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0025.html",
+ "node_id":"apm_07_0025.xml",
+ "product_code":"apm",
+ "code":"130",
+ "des":"You can create a custom alarm policy for a single component.After the alarm policy is created, perform the operations listed in Table 1 if needed.",
+ "doc_type":"usermanual",
+ "kw":"Creating a Custom Alarm Policy,Alarm Policies,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Creating a Custom Alarm Policy",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0059.html",
+ "node_id":"apm_07_0059.xml",
+ "product_code":"",
+ "code":"131",
+ "des":"APM provides recommended alarm templates.",
+ "doc_type":"",
+ "kw":"Recommended Alarm Templates,Alarm Policies,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Recommended Alarm Templates",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0026.html",
+ "node_id":"apm_07_0026.xml",
+ "product_code":"apm",
+ "code":"132",
+ "des":"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 faul",
+ "doc_type":"usermanual",
+ "kw":"Alarm Notification,Alarm Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Alarm Notification",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0030.html",
+ "node_id":"apm_07_0030.xml",
+ "product_code":"apm",
+ "code":"133",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Configuration Management",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Configuration Management",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0031.html",
+ "node_id":"apm_07_0031.xml",
+ "product_code":"apm",
+ "code":"134",
+ "des":"Collection Center displays collectors in a centralized manner. You can view and manage various collectors, metrics, and collection parameters supported by APM.All the sup",
+ "doc_type":"usermanual",
+ "kw":"Collection Center,Configuration Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Collection Center",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_1018.html",
+ "node_id":"apm_07_1018.xml",
+ "product_code":"",
+ "code":"135",
+ "des":"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 suc",
+ "doc_type":"",
+ "kw":"Data Masking,Configuration Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Data Masking",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0033.html",
+ "node_id":"apm_07_0033.xml",
+ "product_code":"apm",
+ "code":"136",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"System Management",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"System Management",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0034.html",
+ "node_id":"apm_07_0034.xml",
+ "product_code":"apm",
+ "code":"137",
+ "des":"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 cry",
+ "doc_type":"usermanual",
+ "kw":"Access Keys,System Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Access Keys",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0035.html",
+ "node_id":"apm_07_0035.xml",
+ "product_code":"apm",
+ "code":"138",
+ "des":"On the General Configuration page, you can determine whether to collect data through bytecode instrumentation, and specify the slow request threshold and maximum number o",
+ "doc_type":"usermanual",
+ "kw":"General Configuration,System Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"General Configuration",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0040.html",
+ "node_id":"apm_07_0040.xml",
+ "product_code":"apm",
+ "code":"139",
+ "des":"APM can count the Agents used by tenants. You can view the number of Agents by time, region, or Agent type.Current Agent: number of Agents used by the current tenant.Hist",
+ "doc_type":"usermanual",
+ "kw":"Agent Count,System Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Agent Count",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0036.html",
+ "node_id":"apm_07_0036.xml",
+ "product_code":"apm",
+ "code":"140",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Permissions Management",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Permissions Management",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0037.html",
+ "node_id":"apm_07_0037.xml",
+ "product_code":"apm",
+ "code":"141",
+ "des":"Enterprise Project Management Service (EPS) is used to control user access to APM resources. After creating IAM user groups for employees, you can create enterprise proje",
+ "doc_type":"usermanual",
+ "kw":"Authorizing Users and User Groups Using Enterprise Projects,Permissions Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Authorizing Users and User Groups Using Enterprise Projects",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0038.html",
+ "node_id":"apm_07_0038.xml",
+ "product_code":"apm",
+ "code":"142",
+ "des":"This chapter describes how to use IAM for fine-grained permissions control for your APM resources. With IAM, you can:Create IAM users for employees based on your enterpri",
+ "doc_type":"usermanual",
+ "kw":"Creating a User and Granting Permissions,Permissions Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"true",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Creating a User and Granting Permissions",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_01_1000.html",
+ "node_id":"apm_01_1000.xml",
+ "product_code":"",
+ "code":"143",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"FAQs",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"FAQs",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_03_0001.html",
+ "node_id":"apm_03_0001.xml",
+ "product_code":"apm",
+ "code":"144",
+ "des":"APM Agents are incompatible with other Agents. Generally, APM implements bytecode instrumentation based on the ASM framework. Installing two Agents means two instrumentat",
+ "doc_type":"usermanual",
+ "kw":"Are APM Agents Compatible with Other Agents Such as Pinpoint?,FAQs,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "IsMltu":"Yes",
+ "IsBot":"Yes",
+ "prodname":"apm",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Are APM Agents Compatible with Other Agents Such as Pinpoint?",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_03_0002.html",
+ "node_id":"apm_03_0002.xml",
+ "product_code":"apm",
+ "code":"145",
+ "des":"Metric data is collected periodically. The default collection period is 1 minute.",
+ "doc_type":"usermanual",
+ "kw":"What Is APM's Metric Data Sampling Policy?,FAQs,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "IsMltu":"Yes",
+ "IsBot":"Yes",
+ "prodname":"apm",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"What Is APM's Metric Data Sampling Policy?",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_03_0004.html",
+ "node_id":"apm_03_0004.xml",
+ "product_code":"apm",
+ "code":"146",
+ "des":"You can view metric data several minutes after you connect Agents.If data collection is stopped, the possible causes are as follows:Instance level: Agents are stopped on ",
+ "doc_type":"usermanual",
+ "kw":"Why Does Metric Data Collection Fail?,FAQs,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "IsMltu":"Yes",
+ "IsBot":"Yes",
+ "prodname":"apm",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Why Does Metric Data Collection Fail?",
+ "githuburl":""
+ },
+ {
+ "uri":"apm_07_0039.html",
+ "node_id":"apm_07_0039.xml",
+ "product_code":"apm",
+ "code":"147",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Change History,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"usermanual",
+ "prodname":"apm",
+ "IsBot":"Yes",
+ "opensource":"false",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Change History",
+ "githuburl":""
+ }
+]
\ No newline at end of file
diff --git a/docs/apm/umn/CLASS.TXT.json b/docs/apm/umn/CLASS.TXT.json
new file mode 100644
index 00000000..69ee8a71
--- /dev/null
+++ b/docs/apm/umn/CLASS.TXT.json
@@ -0,0 +1,1325 @@
+[
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Service Overview",
+ "uri":"apm_01_0001.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"1"
+ },
+ {
+ "desc":"In the cloud era, applications in the microservice architecture are increasingly diversified, bringing many application exceptions. Application O&M faces the following ch",
+ "product_code":"apm",
+ "title":"What Is APM",
+ "uri":"apm_01_0002.html",
+ "doc_type":"usermanual2",
+ "p_code":"1",
+ "code":"2"
+ },
+ {
+ "desc":"APM manages cloud application performance. It provides application metric monitoring, tracing, application topology, URL tracing, intelligent alarm reporting, and tag/Age",
+ "product_code":"apm",
+ "title":"Functions",
+ "uri":"apm_01_0003.html",
+ "doc_type":"usermanual2",
+ "p_code":"1",
+ "code":"3"
+ },
+ {
+ "desc":"APM is widely used. The following lists some typical scenarios.Pain PointsIn the distributed microservice architecture, enterprises can develop diverse applications effic",
+ "product_code":"apm",
+ "title":"Application Scenarios",
+ "uri":"apm_01_0004.html",
+ "doc_type":"usermanual2",
+ "p_code":"1",
+ "code":"4"
+ },
+ {
+ "desc":"A topology graphically displays call and dependency relationships between applications. It is composed of circles, lines with arrows, and resources. Each line with an arr",
+ "product_code":"apm",
+ "title":"Basic Concepts",
+ "uri":"apm_01_0005.html",
+ "doc_type":"usermanual2",
+ "p_code":"1",
+ "code":"5"
+ },
+ {
+ "desc":"APM provides basic and enterprise editions and supports interconnection with Java applications. The following table lists the functions supported by each edition.The ente",
+ "product_code":"apm",
+ "title":"Edition Differences",
+ "uri":"apm_01_0006.html",
+ "doc_type":"usermanual2",
+ "p_code":"1",
+ "code":"6"
+ },
+ {
+ "desc":"If you need to assign different permissions to employees in your enterprise to access your APM resources, Identity and Access Management (IAM) is a good choice for fine-g",
+ "product_code":"apm",
+ "title":"Permissions Management",
+ "uri":"apm_01_0007.html",
+ "doc_type":"usermanual2",
+ "p_code":"1",
+ "code":"7"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Metric Overview",
+ "uri":"apm_01_0013.html",
+ "doc_type":"usermanual2",
+ "p_code":"1",
+ "code":"8"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of exception metrics collected by APM.",
+ "product_code":"apm",
+ "title":"Exception",
+ "uri":"apm_01_0015.html",
+ "doc_type":"usermanual2",
+ "p_code":"8",
+ "code":"9"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Basic Monitoring",
+ "uri":"apm_01_0016.html",
+ "doc_type":"usermanual2",
+ "p_code":"8",
+ "code":"10"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of GC metrics collected by APM.",
+ "product_code":"apm",
+ "title":"GC Monitoring",
+ "uri":"apm_01_0027.html",
+ "doc_type":"usermanual2",
+ "p_code":"10",
+ "code":"11"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of JavaMethod metrics collected by APM.",
+ "product_code":"apm",
+ "title":"JavaMethod",
+ "uri":"apm_01_0028.html",
+ "doc_type":"usermanual2",
+ "p_code":"10",
+ "code":"12"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of JVM metrics collected by APM.",
+ "product_code":"apm",
+ "title":"JVM Monitoring",
+ "uri":"apm_01_0029.html",
+ "doc_type":"usermanual2",
+ "p_code":"10",
+ "code":"13"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of JVMInfo metrics collected by APM.",
+ "product_code":"apm",
+ "title":"JVMInfo",
+ "uri":"apm_01_0030.html",
+ "doc_type":"usermanual2",
+ "p_code":"10",
+ "code":"14"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of Netty memory metrics collected by APM.",
+ "product_code":"apm",
+ "title":"Netty Memory",
+ "uri":"apm_01_0031.html",
+ "doc_type":"usermanual2",
+ "p_code":"10",
+ "code":"15"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of thread metrics collected by APM.",
+ "product_code":"apm",
+ "title":"Threads",
+ "uri":"apm_01_0032.html",
+ "doc_type":"usermanual2",
+ "p_code":"10",
+ "code":"16"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Databases",
+ "uri":"apm_01_0017.html",
+ "doc_type":"usermanual2",
+ "p_code":"8",
+ "code":"17"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of C3P0 connection pool metrics collected by APM.",
+ "product_code":"apm",
+ "title":"C3P0 Connection Pool Monitoring",
+ "uri":"apm_01_0033.html",
+ "doc_type":"usermanual2",
+ "p_code":"17",
+ "code":"18"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of Cassandra metrics collected by APM.",
+ "product_code":"apm",
+ "title":"Cassandra Monitoring",
+ "uri":"apm_01_0034.html",
+ "doc_type":"usermanual2",
+ "p_code":"17",
+ "code":"19"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of ClickHouse database metrics collected by APM.",
+ "product_code":"apm",
+ "title":"ClickHouse Database",
+ "uri":"apm_01_0035.html",
+ "doc_type":"usermanual2",
+ "p_code":"17",
+ "code":"20"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of DBCP connection pool metrics collected by APM.",
+ "product_code":"apm",
+ "title":"DBCP Connection Pool Monitoring",
+ "uri":"apm_01_0036.html",
+ "doc_type":"usermanual2",
+ "p_code":"17",
+ "code":"21"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of Druid connection pool metrics collected by APM.",
+ "product_code":"apm",
+ "title":"Druid Connection Pool Monitoring",
+ "uri":"apm_01_0037.html",
+ "doc_type":"usermanual2",
+ "p_code":"17",
+ "code":"22"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of EsRestClient metrics collected by APM.",
+ "product_code":"apm",
+ "title":"EsRestClient Monitoring",
+ "uri":"apm_01_0038.html",
+ "doc_type":"usermanual2",
+ "p_code":"17",
+ "code":"23"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of GaussDB database metrics collected by APM.",
+ "product_code":"apm",
+ "title":"GaussDB Database",
+ "uri":"apm_01_0039.html",
+ "doc_type":"usermanual2",
+ "p_code":"17",
+ "code":"24"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of HBase metrics collected by APM.",
+ "product_code":"apm",
+ "title":"HBase Monitoring",
+ "uri":"apm_01_0040.html",
+ "doc_type":"usermanual2",
+ "p_code":"17",
+ "code":"25"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of Hikari connection pool metrics collected by APM.",
+ "product_code":"apm",
+ "title":"Hikari Connection Pool Monitoring",
+ "uri":"apm_01_0041.html",
+ "doc_type":"usermanual2",
+ "p_code":"17",
+ "code":"26"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of Jetcd metrics collected by APM.",
+ "product_code":"apm",
+ "title":"Jetcd Monitoring",
+ "uri":"apm_01_0042.html",
+ "doc_type":"usermanual2",
+ "p_code":"17",
+ "code":"27"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of MongoDB metrics collected by APM.",
+ "product_code":"apm",
+ "title":"MongoDB Monitoring",
+ "uri":"apm_01_0043.html",
+ "doc_type":"usermanual2",
+ "p_code":"17",
+ "code":"28"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of MySQL database metrics collected by APM.",
+ "product_code":"apm",
+ "title":"MySQL Database",
+ "uri":"apm_01_0044.html",
+ "doc_type":"usermanual2",
+ "p_code":"17",
+ "code":"29"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of ObsClient metrics collected by APM.",
+ "product_code":"apm",
+ "title":"ObsClient Monitoring",
+ "uri":"apm_01_0045.html",
+ "doc_type":"usermanual2",
+ "p_code":"17",
+ "code":"30"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of Oracle database metrics collected by APM.",
+ "product_code":"apm",
+ "title":"Oracle Database",
+ "uri":"apm_01_0046.html",
+ "doc_type":"usermanual2",
+ "p_code":"17",
+ "code":"31"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of PostgreSQL database metrics collected by APM.",
+ "product_code":"apm",
+ "title":"PostgreSQL Database",
+ "uri":"apm_01_0047.html",
+ "doc_type":"usermanual2",
+ "p_code":"17",
+ "code":"32"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"URLs",
+ "uri":"apm_01_0018.html",
+ "doc_type":"usermanual2",
+ "p_code":"8",
+ "code":"33"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of CSEProvider cluster metrics collected by APM.",
+ "product_code":"apm",
+ "title":"CSEProvider Cluster Monitoring",
+ "uri":"apm_01_0048.html",
+ "doc_type":"usermanual2",
+ "p_code":"33",
+ "code":"34"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of DubboProvider metrics collected by APM.",
+ "product_code":"apm",
+ "title":"DubboProvider Monitoring",
+ "uri":"apm_01_0049.html",
+ "doc_type":"usermanual2",
+ "p_code":"33",
+ "code":"35"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of FunctionGraph metrics collected by APM.",
+ "product_code":"apm",
+ "title":"FunctionGraph Monitoring",
+ "uri":"apm_01_0050.html",
+ "doc_type":"usermanual2",
+ "p_code":"33",
+ "code":"36"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of URL metrics collected by APM.",
+ "product_code":"apm",
+ "title":"URL Monitoring",
+ "uri":"apm_01_0052.html",
+ "doc_type":"usermanual2",
+ "p_code":"33",
+ "code":"37"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"External Calls",
+ "uri":"apm_01_0019.html",
+ "doc_type":"usermanual2",
+ "p_code":"8",
+ "code":"38"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of ApacheHttpAsyncClient connection pool metrics collected by APM.",
+ "product_code":"apm",
+ "title":"ApacheHttpAsyncClient Connection Pool",
+ "uri":"apm_01_0053.html",
+ "doc_type":"usermanual2",
+ "p_code":"38",
+ "code":"39"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of ApacheHttpClient connection pool metrics collected by APM.",
+ "product_code":"apm",
+ "title":"ApacheHttpClient Connection Pool",
+ "uri":"apm_01_0054.html",
+ "doc_type":"usermanual2",
+ "p_code":"38",
+ "code":"40"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of CSEConsumer cluster metrics collected by APM.",
+ "product_code":"apm",
+ "title":"CSEConsumer Cluster Monitoring",
+ "uri":"apm_01_0055.html",
+ "doc_type":"usermanual2",
+ "p_code":"38",
+ "code":"41"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of DubboConsumer metrics collected by APM.",
+ "product_code":"apm",
+ "title":"DubboConsumer Monitoring",
+ "uri":"apm_01_0056.html",
+ "doc_type":"usermanual2",
+ "p_code":"38",
+ "code":"42"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of HttpClient metrics collected by APM.",
+ "product_code":"apm",
+ "title":"HttpClient Monitoring",
+ "uri":"apm_01_0051.html",
+ "doc_type":"usermanual2",
+ "p_code":"38",
+ "code":"43"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Cache",
+ "uri":"apm_01_0020.html",
+ "doc_type":"usermanual2",
+ "p_code":"8",
+ "code":"44"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of Redis method call metrics collected by APM.",
+ "product_code":"apm",
+ "title":"Redis Method Call",
+ "uri":"apm_01_0057.html",
+ "doc_type":"usermanual2",
+ "p_code":"44",
+ "code":"45"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of Jedis metrics collected by APM.",
+ "product_code":"apm",
+ "title":"Jedis Monitoring",
+ "uri":"apm_01_0058.html",
+ "doc_type":"usermanual2",
+ "p_code":"44",
+ "code":"46"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of Lettuce client metrics collected by APM.",
+ "product_code":"apm",
+ "title":"Lettuce Client",
+ "uri":"apm_01_0059.html",
+ "doc_type":"usermanual2",
+ "p_code":"44",
+ "code":"47"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of Agent monitoring metrics collected by APM.",
+ "product_code":"apm",
+ "title":"Agent Monitoring",
+ "uri":"apm_01_0021.html",
+ "doc_type":"usermanual2",
+ "p_code":"8",
+ "code":"48"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of Tomcat metrics collected by APM.",
+ "product_code":"apm",
+ "title":"Tomcat Monitoring",
+ "uri":"apm_01_0022.html",
+ "doc_type":"usermanual2",
+ "p_code":"8",
+ "code":"49"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Message Queues",
+ "uri":"apm_01_0023.html",
+ "doc_type":"usermanual2",
+ "p_code":"8",
+ "code":"50"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of KafkaConsumer metrics collected by APM.",
+ "product_code":"apm",
+ "title":"KafkaConsumer Monitoring",
+ "uri":"apm_01_0061.html",
+ "doc_type":"usermanual2",
+ "p_code":"50",
+ "code":"51"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of KafkaProducer metrics collected by APM.",
+ "product_code":"apm",
+ "title":"KafkaProducer Monitoring",
+ "uri":"apm_01_0062.html",
+ "doc_type":"usermanual2",
+ "p_code":"50",
+ "code":"52"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of RabbitMqCommon metrics collected by APM.",
+ "product_code":"apm",
+ "title":"RabbitMqCommon Monitoring",
+ "uri":"apm_01_0063.html",
+ "doc_type":"usermanual2",
+ "p_code":"50",
+ "code":"53"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of RabbitMqConsumer metrics collected by APM.",
+ "product_code":"apm",
+ "title":"RabbitMqConsumer Monitoring",
+ "uri":"apm_01_0064.html",
+ "doc_type":"usermanual2",
+ "p_code":"50",
+ "code":"54"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of RabbitMqProducer metrics collected by APM.",
+ "product_code":"apm",
+ "title":"RabbitMqProducer Monitoring",
+ "uri":"apm_01_0065.html",
+ "doc_type":"usermanual2",
+ "p_code":"50",
+ "code":"55"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of RocketMqConsumer metrics collected by APM.",
+ "product_code":"apm",
+ "title":"RocketMqConsumer Monitoring",
+ "uri":"apm_01_0066.html",
+ "doc_type":"usermanual2",
+ "p_code":"50",
+ "code":"56"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of RocketMqProducer metrics collected by APM.",
+ "product_code":"apm",
+ "title":"RocketMqProducer Monitoring",
+ "uri":"apm_01_0067.html",
+ "doc_type":"usermanual2",
+ "p_code":"50",
+ "code":"57"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"RPC",
+ "uri":"apm_01_0024.html",
+ "doc_type":"usermanual2",
+ "p_code":"8",
+ "code":"58"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of GRPCClient metrics collected by APM.",
+ "product_code":"apm",
+ "title":"GRPCClient Monitoring",
+ "uri":"apm_01_0068.html",
+ "doc_type":"usermanual2",
+ "p_code":"58",
+ "code":"59"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of GRPCServer metrics collected by APM.",
+ "product_code":"apm",
+ "title":"GRPCServer Monitoring",
+ "uri":"apm_01_0069.html",
+ "doc_type":"usermanual2",
+ "p_code":"58",
+ "code":"60"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"IoT",
+ "uri":"apm_01_0025.html",
+ "doc_type":"usermanual2",
+ "p_code":"8",
+ "code":"61"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of CoapClient metrics collected by APM.",
+ "product_code":"apm",
+ "title":"CoapClient Monitoring",
+ "uri":"apm_01_0070.html",
+ "doc_type":"usermanual2",
+ "p_code":"61",
+ "code":"62"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of CoapServer metrics collected by APM.",
+ "product_code":"apm",
+ "title":"CoapServer Monitoring",
+ "uri":"apm_01_0071.html",
+ "doc_type":"usermanual2",
+ "p_code":"61",
+ "code":"63"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of MoquetteBroker metrics collected by APM.",
+ "product_code":"apm",
+ "title":"MoquetteBroker Monitoring",
+ "uri":"apm_01_0072.html",
+ "doc_type":"usermanual2",
+ "p_code":"61",
+ "code":"64"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of PahoPublisher metrics collected by APM.",
+ "product_code":"apm",
+ "title":"PahoPublisher Monitoring",
+ "uri":"apm_01_0073.html",
+ "doc_type":"usermanual2",
+ "p_code":"61",
+ "code":"65"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of PahoSubscriber metrics collected by APM.",
+ "product_code":"apm",
+ "title":"PahoSubscriber Monitoring",
+ "uri":"apm_01_0074.html",
+ "doc_type":"usermanual2",
+ "p_code":"61",
+ "code":"66"
+ },
+ {
+ "desc":"This section describes the types, names, and meanings of WebSocket metrics collected by APM.",
+ "product_code":"apm",
+ "title":"Communication Protocol",
+ "uri":"apm_01_0026.html",
+ "doc_type":"usermanual2",
+ "p_code":"8",
+ "code":"67"
+ },
+ {
+ "desc":"All O&M data will be displayed on the APM console. Therefore, you are not advised to upload your privacy or sensitive data to APM. If you need to upload such data, encryp",
+ "product_code":"apm",
+ "title":"Privacy and Sensitive Information Protection Statement",
+ "uri":"apm_01_0008.html",
+ "doc_type":"usermanual2",
+ "p_code":"1",
+ "code":"68"
+ },
+ {
+ "desc":"After you enable data collection, APM collects application performance metrics and tracing data. Your personal privacy data will not be collected. The collected data will",
+ "product_code":"apm",
+ "title":"Data Collection",
+ "uri":"apm_01_0009.html",
+ "doc_type":"usermanual2",
+ "p_code":"1",
+ "code":"69"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Usage Restrictions",
+ "uri":"apm_01_0010.html",
+ "doc_type":"usermanual2",
+ "p_code":"1",
+ "code":"70"
+ },
+ {
+ "desc":"Currently, APM can connect to Java applications. APM supports multiple mainstream Java frameworks, web servers, communications protocols, and databases.Java components an",
+ "product_code":"apm",
+ "title":"Java",
+ "uri":"apm_01_0094.html",
+ "doc_type":"usermanual2",
+ "p_code":"70",
+ "code":"71"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Getting Started",
+ "uri":"apm_02_1002.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"72"
+ },
+ {
+ "desc":"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 Differen",
+ "product_code":"apm",
+ "title":"Enabling APM",
+ "uri":"apm_02_0001.html",
+ "doc_type":"usermanual2",
+ "p_code":"72",
+ "code":"73"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Monitoring Java Applications",
+ "uri":"apm_02_0002.html",
+ "doc_type":"usermanual2",
+ "p_code":"72",
+ "code":"74"
+ },
+ {
+ "desc":"The network between your host and APM is normal.You can run the Telnet command to check the network.",
+ "product_code":"apm",
+ "title":"Connecting Agents",
+ "uri":"apm_02_0003.html",
+ "doc_type":"usermanual2",
+ "p_code":"74",
+ "code":"75"
+ },
+ {
+ "desc":"The 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.The AK/SK required",
+ "product_code":"apm",
+ "title":"Manually Installing Agents for Java Applications",
+ "uri":"apm_02_0004.html",
+ "doc_type":"usermanual2",
+ "p_code":"74",
+ "code":"76"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"JavaAgent Download Addresses",
+ "uri":"apm_02_0007.html",
+ "doc_type":"usermanual2",
+ "p_code":"72",
+ "code":"77"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Access Address (master.address)",
+ "uri":"apm_02_0008.html",
+ "doc_type":"usermanual2",
+ "p_code":"72",
+ "code":"78"
+ },
+ {
+ "desc":"This document describes how to use Application Performance Management (APM).",
+ "product_code":"apm",
+ "title":"Before You Start",
+ "uri":"apm_07_0001.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"79"
+ },
+ {
+ "desc":"The Applications page displays information such as components, environments, Agent status, and supported operations.Component|Environment: name of a component or environm",
+ "product_code":"apm",
+ "title":"Application List",
+ "uri":"apm_07_0002.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"80"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"CMDB Management",
+ "uri":"apm_07_0050.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"81"
+ },
+ {
+ "desc":"After an application is created, connect it to APM for monitoring.",
+ "product_code":"apm",
+ "title":"Creating an Application",
+ "uri":"apm_07_0151.html",
+ "doc_type":"usermanual2",
+ "p_code":"81",
+ "code":"82"
+ },
+ {
+ "desc":"A maximum of three layers of sub-applications can be created.",
+ "product_code":"apm",
+ "title":"Creating a Sub-application",
+ "uri":"apm_07_0153.html",
+ "doc_type":"usermanual2",
+ "p_code":"81",
+ "code":"83"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Configuring an Application and Sub-application",
+ "uri":"apm_07_0152.html",
+ "doc_type":"usermanual2",
+ "p_code":"81",
+ "code":"84"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Application Metric Monitoring",
+ "uri":"apm_07_0003.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"85"
+ },
+ {
+ "desc":"APM Agents periodically collect performance metric data to measure the overall health status of applications. They can collect the metric data of JVM, GC, service calls, ",
+ "product_code":"apm",
+ "title":"Overview",
+ "uri":"apm_07_0004.html",
+ "doc_type":"usermanual2",
+ "p_code":"85",
+ "code":"86"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Application Monitoring Details",
+ "uri":"apm_07_0005.html",
+ "doc_type":"usermanual2",
+ "p_code":"85",
+ "code":"87"
+ },
+ {
+ "desc":"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.",
+ "product_code":"apm",
+ "title":"Topology",
+ "uri":"apm_07_0067.html",
+ "doc_type":"usermanual2",
+ "p_code":"87",
+ "code":"88"
+ },
+ {
+ "desc":"This function monitors the calls of the current application by external services. It includes URL, Dubbo server, CSE server, CSEProvider cluster, and FunctionGraph monito",
+ "product_code":"apm",
+ "title":"URL",
+ "uri":"apm_07_0006.html",
+ "doc_type":"usermanual2",
+ "p_code":"87",
+ "code":"89"
+ },
+ {
+ "desc":"This function monitors JVMInfo, JVMMonitor, GC, thread, and JavaMethod.Options: Last 20 minutes, Last hour, Last 3 hours, Last 6 hours, Last day, Today, Yesterday, Last w",
+ "product_code":"apm",
+ "title":"JVM",
+ "uri":"apm_07_0007.html",
+ "doc_type":"usermanual2",
+ "p_code":"87",
+ "code":"90"
+ },
+ {
+ "desc":"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 colle",
+ "product_code":"apm",
+ "title":"Exception",
+ "uri":"apm_07_0008.html",
+ "doc_type":"usermanual2",
+ "p_code":"87",
+ "code":"91"
+ },
+ {
+ "desc":"This function monitors the calls of external services by the current application. It covers CSEConsumer, ApacheHttpClient, ApacheHttpAsyncClient, DubboConsumer, and HttpC",
+ "product_code":"apm",
+ "title":"Call",
+ "uri":"apm_07_0009.html",
+ "doc_type":"usermanual2",
+ "p_code":"87",
+ "code":"92"
+ },
+ {
+ "desc":"This function monitors database access. The databases that can be monitored include the C3P0, Cassandra, ClickHouse, DBCP, Druid, EsRestClient, GaussDB, Hikari, Jetcd, Ob",
+ "product_code":"apm",
+ "title":"SQL",
+ "uri":"apm_07_0010.html",
+ "doc_type":"usermanual2",
+ "p_code":"87",
+ "code":"93"
+ },
+ {
+ "desc":"This function monitors web containers, including Tomcat. This section focuses on Tomcat monitoring.Click a number in blue (such as those in the Current Threads, Busy Thre",
+ "product_code":"apm",
+ "title":"Web Container",
+ "uri":"apm_07_0061.html",
+ "doc_type":"usermanual2",
+ "p_code":"87",
+ "code":"94"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Application Monitoring Configuration",
+ "uri":"apm_07_0011.html",
+ "doc_type":"usermanual2",
+ "p_code":"85",
+ "code":"95"
+ },
+ {
+ "desc":"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",
+ "product_code":"apm",
+ "title":"Configuration Details",
+ "uri":"apm_07_0012.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"96"
+ },
+ {
+ "desc":"On the Modify MySQL Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.Collect Original SQL: ",
+ "product_code":"apm",
+ "title":"Configuring the MySQL Monitoring Item",
+ "uri":"apm_07_0013.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"97"
+ },
+ {
+ "desc":"On the Modify HttpClient Monitoring Configuration page, set the following URL normalization parameters:Collection Interval: The default value is 60s and cannot be changed",
+ "product_code":"apm",
+ "title":"Configuring the HttpClient Monitoring Item",
+ "uri":"apm_07_0014.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"98"
+ },
+ {
+ "desc":"On the Modify URL Monitoring Configuration page, set the following parameters:For security purposes, do not contain sensitive data in headers, URL parameters, cookies, or",
+ "product_code":"apm",
+ "title":"Configuring the URL Monitoring Item",
+ "uri":"apm_07_0015.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"99"
+ },
+ {
+ "desc":"On the Modify JavaMethod Monitoring Configuration page, set method interception parameters.Collection Interval: The default value is 60s and cannot be changed.Method Inte",
+ "product_code":"apm",
+ "title":"Configuring the JavaMethod Monitoring Item",
+ "uri":"apm_07_0016.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"100"
+ },
+ {
+ "desc":"On the Modify Druid Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.TraceReportTimeSpanThr",
+ "product_code":"apm",
+ "title":"Configuring the Druid Monitoring Item",
+ "uri":"apm_07_0048.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"101"
+ },
+ {
+ "desc":"On the Modify ApacheHttpAsyncClient Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.",
+ "product_code":"apm",
+ "title":"Configuring the ApacheHttpAsyncClient Monitoring Item",
+ "uri":"apm_07_0047.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"102"
+ },
+ {
+ "desc":"On the Modify Redis Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.Parameter Parsing: The",
+ "product_code":"apm",
+ "title":"Configuring the Redis Monitoring Item",
+ "uri":"apm_07_0046.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"103"
+ },
+ {
+ "desc":"On the Modify Jedis Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "product_code":"apm",
+ "title":"Configuring the Jedis Monitoring Item",
+ "uri":"apm_07_0045.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"104"
+ },
+ {
+ "desc":"On the Modify HBase Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "product_code":"apm",
+ "title":"Configuring the HBase Monitoring Item",
+ "uri":"apm_07_0044.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"105"
+ },
+ {
+ "desc":"On the Modify ApacheHttpClient Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "product_code":"apm",
+ "title":"Configuring the ApacheHttpClient Monitoring Item",
+ "uri":"apm_07_0043.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"106"
+ },
+ {
+ "desc":"On the Modify Tomcat Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "product_code":"apm",
+ "title":"Configuring the Tomcat Monitoring Item",
+ "uri":"apm_07_0042.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"107"
+ },
+ {
+ "desc":"On the Modify EsRestClient Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.Index Normalizat",
+ "product_code":"apm",
+ "title":"Configuring the EsRestClient Monitoring Item",
+ "uri":"apm_07_0041.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"108"
+ },
+ {
+ "desc":"On the Modify WebSocket Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "product_code":"apm",
+ "title":"Configuring the WebSocket Monitoring Item",
+ "uri":"apm_07_0049.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"109"
+ },
+ {
+ "desc":"On the Modify KafkaProducer Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "product_code":"apm",
+ "title":"Configuring the KafkaProducer Monitoring Item",
+ "uri":"apm_07_0053.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"110"
+ },
+ {
+ "desc":"On the Modify Hikari Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.TraceReportTimeSpanTh",
+ "product_code":"apm",
+ "title":"Configuring the Hikari Monitoring Item",
+ "uri":"apm_07_0054.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"111"
+ },
+ {
+ "desc":"On the Modify Exception Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.Determine Trace Ex",
+ "product_code":"apm",
+ "title":"Configuring the Exception Monitoring Item",
+ "uri":"apm_07_0055.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"112"
+ },
+ {
+ "desc":"On the Modify Thread Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.",
+ "product_code":"apm",
+ "title":"Configuring the Thread Monitoring Item",
+ "uri":"apm_07_0056.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"113"
+ },
+ {
+ "desc":"On the Modify GC Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "product_code":"apm",
+ "title":"Configuring the GC Monitoring Item",
+ "uri":"apm_07_0057.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"114"
+ },
+ {
+ "desc":"On the Modify JVMInfo Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "product_code":"apm",
+ "title":"Configuring the JVMInfo Monitoring Item",
+ "uri":"apm_07_0058.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"115"
+ },
+ {
+ "desc":"On the Modify JVMMonitor Monitoring Configuration page, set the following parameters:Collection Interval: The default value is 60s and cannot be changed.Call Chain Stack ",
+ "product_code":"apm",
+ "title":"Configuring the JVMMonitor Monitoring Item",
+ "uri":"apm_07_0064.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"116"
+ },
+ {
+ "desc":"On the Modify ProbeInfo Monitoring Configuration page, set the following parameter:Collection Interval: The default value is 60s and cannot be changed.",
+ "product_code":"apm",
+ "title":"Configuring ProbeInfo Monitoring Item",
+ "uri":"apm_07_0065.html",
+ "doc_type":"usermanual2",
+ "p_code":"95",
+ "code":"117"
+ },
+ {
+ "desc":"APM supports summary tables, trend graphs, latest data tables, and original data tables.Summary table: records the summary calculation results based on the primary key me",
+ "product_code":"apm",
+ "title":"Monitoring Item Views",
+ "uri":"apm_07_0017.html",
+ "doc_type":"usermanual2",
+ "p_code":"85",
+ "code":"118"
+ },
+ {
+ "desc":"When the calls between enterprise microservices are complex, APM Agents sample some requests, and intercept corresponding requests and subsequent call information. For ex",
+ "product_code":"apm",
+ "title":"Tracing",
+ "uri":"apm_07_0018.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"119"
+ },
+ {
+ "desc":"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 ",
+ "product_code":"apm",
+ "title":"Application Topology",
+ "uri":"apm_07_0019.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"120"
+ },
+ {
+ "desc":"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",
+ "product_code":"apm",
+ "title":"URL Tracing",
+ "uri":"apm_07_0020.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"121"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Agent Management",
+ "uri":"apm_07_0027.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"122"
+ },
+ {
+ "desc":"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.In the upper left corn",
+ "product_code":"apm",
+ "title":"Operating Agents",
+ "uri":"apm_07_0028.html",
+ "doc_type":"usermanual2",
+ "p_code":"122",
+ "code":"123"
+ },
+ {
+ "desc":"Update Agent versions according to the following procedure.To upgrade the manually installed Agent, download the new Agent by referring to JavaAgent Download Addresses. F",
+ "product_code":"apm",
+ "title":"Upgrading Agents",
+ "uri":"apm_07_0029.html",
+ "doc_type":"usermanual2",
+ "p_code":"122",
+ "code":"124"
+ },
+ {
+ "desc":"You can add tags for different environments and applications for easy management.Tag management covers tags and global tags.A tag is used to set a collector corresponding",
+ "product_code":"apm",
+ "title":"Managing Tags",
+ "uri":"apm_07_1017.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"125"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Alarm Management",
+ "uri":"apm_07_0021.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"126"
+ },
+ {
+ "desc":"Alarms are reported by services connected to APM Agents when specified conditions are met. You can learn about service exceptions in a timely manner and quickly rectify f",
+ "product_code":"apm",
+ "title":"Alarm List",
+ "uri":"apm_07_0022.html",
+ "doc_type":"usermanual2",
+ "p_code":"126",
+ "code":"127"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Alarm Policies",
+ "uri":"apm_07_0023.html",
+ "doc_type":"usermanual2",
+ "p_code":"126",
+ "code":"128"
+ },
+ {
+ "desc":"APM allows you to configure alarm templates. You can create multiple alarm policies under a template and bind them to nodes.Enter basic information and then click Next.Te",
+ "product_code":"apm",
+ "title":"Configuring an Alarm Template",
+ "uri":"apm_07_0024.html",
+ "doc_type":"usermanual2",
+ "p_code":"128",
+ "code":"129"
+ },
+ {
+ "desc":"You can create a custom alarm policy for a single component.After the alarm policy is created, perform the operations listed in Table 1 if needed.",
+ "product_code":"apm",
+ "title":"Creating a Custom Alarm Policy",
+ "uri":"apm_07_0025.html",
+ "doc_type":"usermanual2",
+ "p_code":"128",
+ "code":"130"
+ },
+ {
+ "desc":"APM provides recommended alarm templates.",
+ "product_code":"apm",
+ "title":"Recommended Alarm Templates",
+ "uri":"apm_07_0059.html",
+ "doc_type":"usermanual2",
+ "p_code":"128",
+ "code":"131"
+ },
+ {
+ "desc":"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 faul",
+ "product_code":"apm",
+ "title":"Alarm Notification",
+ "uri":"apm_07_0026.html",
+ "doc_type":"usermanual2",
+ "p_code":"126",
+ "code":"132"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Configuration Management",
+ "uri":"apm_07_0030.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"133"
+ },
+ {
+ "desc":"Collection Center displays collectors in a centralized manner. You can view and manage various collectors, metrics, and collection parameters supported by APM.All the sup",
+ "product_code":"apm",
+ "title":"Collection Center",
+ "uri":"apm_07_0031.html",
+ "doc_type":"usermanual2",
+ "p_code":"133",
+ "code":"134"
+ },
+ {
+ "desc":"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 suc",
+ "product_code":"apm",
+ "title":"Data Masking",
+ "uri":"apm_07_1018.html",
+ "doc_type":"usermanual2",
+ "p_code":"133",
+ "code":"135"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"System Management",
+ "uri":"apm_07_0033.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"136"
+ },
+ {
+ "desc":"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 cry",
+ "product_code":"apm",
+ "title":"Access Keys",
+ "uri":"apm_07_0034.html",
+ "doc_type":"usermanual2",
+ "p_code":"136",
+ "code":"137"
+ },
+ {
+ "desc":"On the General Configuration page, you can determine whether to collect data through bytecode instrumentation, and specify the slow request threshold and maximum number o",
+ "product_code":"apm",
+ "title":"General Configuration",
+ "uri":"apm_07_0035.html",
+ "doc_type":"usermanual2",
+ "p_code":"136",
+ "code":"138"
+ },
+ {
+ "desc":"APM can count the Agents used by tenants. You can view the number of Agents by time, region, or Agent type.Current Agent: number of Agents used by the current tenant.Hist",
+ "product_code":"apm",
+ "title":"Agent Count",
+ "uri":"apm_07_0040.html",
+ "doc_type":"usermanual2",
+ "p_code":"136",
+ "code":"139"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Permissions Management",
+ "uri":"apm_07_0036.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"140"
+ },
+ {
+ "desc":"Enterprise Project Management Service (EPS) is used to control user access to APM resources. After creating IAM user groups for employees, you can create enterprise proje",
+ "product_code":"apm",
+ "title":"Authorizing Users and User Groups Using Enterprise Projects",
+ "uri":"apm_07_0037.html",
+ "doc_type":"usermanual2",
+ "p_code":"140",
+ "code":"141"
+ },
+ {
+ "desc":"This chapter describes how to use IAM for fine-grained permissions control for your APM resources. With IAM, you can:Create IAM users for employees based on your enterpri",
+ "product_code":"apm",
+ "title":"Creating a User and Granting Permissions",
+ "uri":"apm_07_0038.html",
+ "doc_type":"usermanual2",
+ "p_code":"140",
+ "code":"142"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"FAQs",
+ "uri":"apm_01_1000.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"143"
+ },
+ {
+ "desc":"APM Agents are incompatible with other Agents. Generally, APM implements bytecode instrumentation based on the ASM framework. Installing two Agents means two instrumentat",
+ "product_code":"apm",
+ "title":"Are APM Agents Compatible with Other Agents Such as Pinpoint?",
+ "uri":"apm_03_0001.html",
+ "doc_type":"usermanual2",
+ "p_code":"143",
+ "code":"144"
+ },
+ {
+ "desc":"Metric data is collected periodically. The default collection period is 1 minute.",
+ "product_code":"apm",
+ "title":"What Is APM's Metric Data Sampling Policy?",
+ "uri":"apm_03_0002.html",
+ "doc_type":"usermanual2",
+ "p_code":"143",
+ "code":"145"
+ },
+ {
+ "desc":"You can view metric data several minutes after you connect Agents.If data collection is stopped, the possible causes are as follows:Instance level: Agents are stopped on ",
+ "product_code":"apm",
+ "title":"Why Does Metric Data Collection Fail?",
+ "uri":"apm_03_0004.html",
+ "doc_type":"usermanual2",
+ "p_code":"143",
+ "code":"146"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"apm",
+ "title":"Change History",
+ "uri":"apm_07_0039.html",
+ "doc_type":"usermanual2",
+ "p_code":"",
+ "code":"147"
+ }
+]
\ No newline at end of file
diff --git a/docs/apm/umn/PARAMETERS.txt b/docs/apm/umn/PARAMETERS.txt
new file mode 100644
index 00000000..6da8d5f0
--- /dev/null
+++ b/docs/apm/umn/PARAMETERS.txt
@@ -0,0 +1,3 @@
+version=""
+language="en-us"
+type=""
\ No newline at end of file
diff --git a/docs/apm/umn/apm_01_0001.html b/docs/apm/umn/apm_01_0001.html
new file mode 100644
index 00000000..40a0bac3
--- /dev/null
+++ b/docs/apm/umn/apm_01_0001.html
@@ -0,0 +1,29 @@
+
+
+Service Overview
+
+
+
diff --git a/docs/apm/umn/apm_01_0002.html b/docs/apm/umn/apm_01_0002.html
new file mode 100644
index 00000000..06aa16ba
--- /dev/null
+++ b/docs/apm/umn/apm_01_0002.html
@@ -0,0 +1,70 @@
+
+
+What Is APM
+O&M Challenges
In the cloud era, applications in the microservice architecture are increasingly diversified, bringing many application exceptions. Application O&M faces the following challenges:
+
- Distributed applications have complex relationships. As a result, it is hard to ensure normal application running, and quickly locate faults and performance bottlenecks.
- Users choose to leave due to poor experience. If O&M personnel cannot detect and trace services with poor experience in real time, or diagnose application exceptions in a timely manner, user experience will be greatly affected.
- There are a large number of widely distributed applications in the service system. Calls across systems, regions, and applications are frequent. Enterprises urgently need to reduce application management and O&M costs and improve O&M efficiency.
+
+
Introduction to APM
Application Performance Management (APM) helps O&M personnel quickly identify application performance bottlenecks and locate root causes of faults, ensuring user experience.
+
You only need to install Agents for applications so that APM can monitor them in an all-round manner. APM can quickly locate error APIs and slow APIs, reproduce calling parameters, and detect system bottlenecks, facilitating online diagnosis. Currently, APM supports Java applications. The following table lists the application monitoring capabilities of APM.
+
APM is short for Application Performance Management. apm2 is the registered endpoint address.
+
+
+
Table 1 APM monitoring capabilitiesCapability
+ |
+Description
+ |
+
|---|
+
+Non-intrusive collection of application performance data
+ |
+You do not need to modify application code. Instead, you only need to deploy an APM Agent package and modify application startup parameters to monitor applications.
+ |
+
+Application metric monitoring
+ |
+APM automatically monitors application metrics, such as JVM, JavaMethod, URL, Exception, Tomcat, HttpClient, MySQL, Redis, and Kafka.
+ |
+
+Application topology
+ |
+APM automatically generates call relationships between distributed applications based on dynamic analysis and intelligent computing of remote procedure call (RPC) information.
+ |
+
+Tracing
+ |
+After multiple applications are connected to APM, APM automatically samples requests, and collects the call relationships between services and the health status of intermediate calls for automatic tracing.
+ |
+
+Metric drill-down analysis
+ |
+APM enables you to drill down and analyze metrics such as application response time, number of requests, and error rate, and view metrics by application, component, environment, database, middleware, or other dimensions.
+ |
+
+Error or slow URL tracing
+ |
+APM identifies error or slow URLs based on URL tracing, and automatically associates them with corresponding APIs, such as SQL and MQ APIs.
+ |
+
+
+
+
+
- Access to APM: Applications need to implement AK/SK authentication to connect to APM.
- O&M data collection: APM can collect data about applications, basic resources, and user experience from Agents in non-intrusive mode.
- Service implementation: APM supports application metric monitoring, application topology, tracing, and intelligent alarm reporting.
- Service expansion:
- You can quickly diagnose application performance exceptions based on the application topology and tracing of APM, and make judgments based on the application O&M metrics of Application Operations Management (AOM).
- Based on the historical metric data learned by using intelligent algorithms, APM associates metrics for analysis from multiple dimensions, extracts the context data of both normal and abnormal services for comparison, and locates root causes through cluster analysis.
+
+
+
Advantages
+
Connects to applications without having to modify code, and collects data in a non-intrusive mode.
+
- APM Agents collect service call, service inventory, and call KPI data.
+
+
Delivers high throughput (hundreds of millions of API calls), ensuring premium experience.
+
+
Provides open APIs to query O&M data, offers collection standards, and supports independent development.
+
+
Reports alarms using Artificial Intelligence (AI) threshold detection and machine learning based on historical baseline data, and supports root cause analysis.
+
+
Functions
+APM manages cloud application performance. It provides application metric monitoring, tracing, application topology, URL tracing, intelligent alarm reporting, and tag/Agent/configuration/system management.
+
Application Metric Monitoring
This function enables you to monitor the overall health status of applications. APM Agents collect metrics of JVM, GC, service calls, exceptions, external calls, database access, and middleware of Java applications, helping you monitor application running.
+
+
Tracing
APM comprehensively monitors calls and displays service execution traces and statuses, helping you quickly locate performance bottlenecks and faults.
+
- In the displayed trace list, click the target trace to view its basic information.
- On the trace details page, you can view the trace's complete information, including the local method stack and remote call relationships.
+
+
Application Topology
There are two types of application topologies:
+
- Single-component topology: topology of a single component under a certain 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.
+
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.
+
+
URL Tracing
If you need to find out the call relationships of an important application (for example, calling an e-commerce system's API to create orders), use URL tracing analysis. 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 detect problems more precisely.
+
+
Tag Management
You can add tags for different environments and applications for easy management.
+
+
Intelligent Alarm Reporting
When an application connected to APM meets a preset alarm condition, an alarm is triggered and reported. In this way, you can quickly learn about service exceptions and rectify faults to prevent loss.
+
APM allows you to configure alarm templates. You can create multiple alarm policies under a template and bind them to nodes.
+
With intelligent alarm reporting, you can receive alarms by SMS, email, or function.
+
+
Agent Management
You can view the deployment and running statuses of the Agents that are connected to APM, and to stop, start, or delete them.
+
+
Configuration Management
Configuration Management consists of Collection Center and Data Masking.
+
- Collection Center: displays collectors in a centralized manner. You can view and manage various collectors, metrics, and collection parameters supported by APM.
- Data Masking: You can set policies to mask the data reported using APM APIs.
+
+
System Management
System Management consists of Access Keys, General Configuration, and Agent Count.
+
- Access Keys: 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.
- General Configuration: You can determine whether to collect data through bytecode instrumentation, and specify the slow request threshold and maximum number of rows to collect.
- Agent Count: APM can count the Agents used by tenants. You can view the number of Agents by time, region, or Agent type.
+
+
Application Scenarios
+APM is widely used. The following lists some typical scenarios.
+
Diagnosis of Application Exceptions
Pain Points
+
In the distributed microservice architecture, enterprises can develop diverse applications efficiently, but face great challenges in traditional O&M and diagnosis. An e-commerce application may face the following problems:
+
- Difficult fault locating
After receiving the feedback from customers, customer service personnel submit problems to technical personnel for troubleshooting. In the distributed microservice architecture, a request usually undergoes multiple services/nodes before a result is returned. If a fault occurs, O&M personnel need to repeatedly view logs on multiple hosts to locate the fault. Even for simple problems, troubleshooting requires cooperation from multiple teams.
+ - Difficult architecture sort-out
When service logic becomes complex, it is difficult to find out the downstream services (databases, HTTP APIs, and caches) that an application depends on, and external services that depend on the application from the code perspective. It is also difficult to sort out the service logic, manage the architecture, and plan capacities. For example, enterprises are hard to determine the number of hosts required in their activities.
+
+
Service Implementation
+
APM can diagnose exceptions in large distributed applications. When an application breaks down or a request fails, you can locate faults in minutes through topologies and drill-downs.
+
- Visible topology: Abnormal application instances can be automatically discovered on the topology.
- Tracing: You can locate root causes in code through drill-downs after identifying abnormal applications.
- SQL analysis: APM displays graphs of key metrics (such as number of SQL statement calls, latency, and number of errors), and supports analysis of database performance problems caused by abnormal SQL statements.
+
+
User Experience Management
Pain Points
+
In the Internet era where user experience is of crucial importance, you cannot obtain user access information even if backend services run stably. It is much more difficult to locate frontend problems that occur occasionally. After a system goes online, if users cannot access the system due to errors and APM fails to obtain the information in time, lots of users will choose to leave. If users report page problems, how can APM reproduce the problems immediately? How can error details be obtained for fast troubleshooting?
+
Service Implementation
+
APM analyzes the complete process (user request > server > database > server > user request) of application transactions in real time, enabling you to monitor comprehensive user experience in real time. For transactions with poor user experience, locate problems through topologies and tracing.
+
- Application KPI analysis: KPIs such as throughput, latency, and call success rate are displayed, so that you can monitor user experience easily.
- Full-link performance tracing: Web services, caches, and databases are traced, so that you can detect performance bottlenecks quickly.
+
+
Intelligent Diagnosis
Pain Points
+
Massive services bring abundant but unassociated application O&M data, including hundreds of monitoring metrics, KPI data, and tracing data. How can metric and alarm data be associated for analysis from the application, component, or URL tracing perspective? How can possible causes be provided for exceptions based on the historical data and O&M experience library?
+
Service Implementation
+
APM supports automatic detection of faults using machine learning algorithms, and intelligent diagnosis. When an exception is found during URL tracing, APM learns historical metric data based on intelligent algorithms, associates exception metrics for multi-dimensional analysis, extracts characteristics of context data (such as resources, parameters, and call structures) for both normal and abnormal services, and locate root causes through cluster analysis.
+
+
Basic Concepts
+Application Topology
A topology graphically displays call and dependency relationships between applications. It is composed of circles, lines with arrows, and resources. Each line with an arrow represents a call relationship. The number of requests, average response time, and the number of errors are displayed above the line. Different colors indicate different RT ranges, helping you quickly detect and locate faults.
+
- Database: When the database call time is greater than or equal to 100 ms, the value turns yellow. When this time is greater than or equal to 200 ms, the value turns red.
- Cache: When the cache call time is greater than or equal to 10 ms, the value turns yellow. When this time is greater than or equal to 30 ms, the value turns red.
- Other API calls: When the API call time is greater than or equal to 500 ms, the value turns yellow. When this time is greater than or equal to 1000 ms, the value turns red.
- If the number of errors is greater than 0, the value turns red.
+
+
Figure 1 Application topology
+
+
Tracing
By tracing and recording application calls, APM displays the execution traces and statuses of application requests in systems, so that you can quickly locate performance bottlenecks and faults.
+
+
APM Agent
APM Agents use bytecode enhancement technology to collect application performance data in real time. They run on the server where applications are deployed. For details about data collection and usage, see Data Collection. Before using APM, ensure that APM Agents have been installed.
+
+
URL Tracing
URL tracing is to trace the call relationship of an application. For example, the complete process of calling an e-commerce system's API to create orders is "user request > web server > database > web server > user request."
+
If a URL is added for tracing, APM will focus on tracing its downstream calls. Through URL tracing, you can monitor the call relationships between important APIs and downstream services, and detect problems more precisely.
+
+
Apdex
Apdex is an open standard developed by the Apdex alliance. It defines a standard method to measure application performance. The Apdex standard converts the application response time into user satisfaction with application performance in the range of 0 to 1.
+
+
Apdex defines the threshold "T" for application response time. "T" is determined based on performance expectations. Based on the actual response time and "T", user experience can be categorized as follows:
+
Satisfied: indicates that the actual response time is shorter than or equal to "T". For example, if "T" is 1.5s and the actual response time is 1s, user experience is satisfied.
+
Tolerable: indicates that the actual response time is greater than "T", but shorter than or equal to "4T". For example, if "T" is 1s, the tolerable upper threshold for the response time is 4s.
+
Frustrated: indicates that the actual response time is greater than "4T".
+
+
- Apdex calculation
In APM, the Apdex threshold is the maximum response time that makes users satisfied. The application response latency is the service latency. The Apdex value ranges from 0 to 1 and is calculated as follows:
+Apdex = (Number of satisfied samples + Number of tolerable samples x 0.5)/Total number of samples
+
+
+
CMDB
Configuration Management Database (CMDB) structures and displays application resource configuration, so that you can better monitor and manage applications. It consists of:
+
- Application (global concept): refers to a logical unit. You can view the same application information in all regions. For example, an independent functional module under an account can be regarded as an application.
- Sub-application (global concept): similar to a folder. You can create up to three layers of sub-applications under an application.
- Component (global concept): refers to a program or microservice. It is generally used together with environments. A component can 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: refers to 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.
+
+
Edition Differences
+APM provides basic and enterprise editions and supports interconnection with Java applications. The following table lists the functions supported by each edition.
+
+
Edition
+ |
+Free
+ |
+Enterprise
+ |
+
|---|
+
+Description
+ |
+Free of charge. Up to 10 Agents can be connected. Reactivate them every 15 days.
+ |
+All functions are open.
+ |
+
+Data storage duration
+ |
+7 days
+ |
+30 days
+ |
+
+Application topology
+ |
+√
+ |
+√
+ |
+
+Tracing
+ |
+√
+ |
+√
+ |
+
+Cross-region tracing
+ |
+√
+ |
+√
+ |
+
+Metric monitoring
+ |
+√
+ |
+√
+ |
+
+URL tracing analysis
+ |
+√
+ |
+√
+ |
+
+Alarm
+ |
+√
+ |
+√
+ |
+
+CMDB
+ |
+√
+ |
+√
+ |
+
+Note: √ indicates supported, and x indicates not supported.
+ |
+
+
+
+
+
The enterprise edition cannot be downgraded back to the free edition (basic edition).
+
+
Permissions Management
+If you need to assign different permissions to employees in your enterprise to access your APM resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your cloud resources.
+
With IAM, you can use your account to create IAM users for your employees, and assign permissions to the users to control their access to specific resources. For example, some software developers in your enterprise need to use APM resources but cannot delete them or perform any high-risk operations. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using APM resources.
+
If your account does not need individual IAM users for permissions management, you may skip over this chapter.
+
IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see IAM Service Overview.
+
APM Permissions
By default, new IAM users do not have any permissions assigned. You need to add a user to one or more groups, and assign permissions policies or roles to these groups. The user then inherits permissions from the groups it is a member of. This process is called authorization. After authorization, the user can perform specified operations on APM.
+
APM is a global service. By default, the APM permissions granted to a user take effect in all regions supported by APM. APM resources are isolated by tenant. All users under a tenant share resources. To isolate resources, use enterprise projects.
+
APM is a global service and can be accessed without specifying a physical region.
+
Table 1 lists all the system permissions supported by APM.
+
+
Table 1 System permissions supported by APMRole
+ |
+Description
+ |
+Category
+ |
+
|---|
+
+APM FullAccess
+ |
+Full permissions for APM
+ |
+System-defined policy
+ |
+
+APM ReadOnlyAccess
+ |
+Read-only permissions for APM
+ |
+System-defined policy
+ |
+
+
+
+
+
Table 2 lists the common operations supported by each system-defined policy or role of APM. Choose policies or roles as required.
+
+
Table 2 Common operations supported by each system-defined policy or role of APMOperation
+ |
+APM FullAccess
+ |
+APM ReadOnlyAccess
+ |
+
|---|
+
+Querying the alarm list
+ |
+√
+ |
+√
+ |
+
+Querying alarm details
+ |
+√
+ |
+√
+ |
+
+Querying alarm notification details
+ |
+√
+ |
+√
+ |
+
+Obtaining application configuration
+ |
+√
+ |
+√
+ |
+
+Creating application configuration
+ |
+√
+ |
+x
+ |
+
+Deleting application configuration
+ |
+√
+ |
+x
+ |
+
+Modifying application configuration
+ |
+√
+ |
+x
+ |
+
+Querying a tag
+ |
+√
+ |
+√
+ |
+
+Adding a tag
+ |
+√
+ |
+x
+ |
+
+Deleting a tag
+ |
+√
+ |
+x
+ |
+
+Modifying a tag
+ |
+√
+ |
+x
+ |
+
+Querying an alarm template
+ |
+√
+ |
+√
+ |
+
+Adding an alarm template
+ |
+√
+ |
+x
+ |
+
+Deleting an alarm template
+ |
+√
+ |
+x
+ |
+
+Modifying an alarm template
+ |
+√
+ |
+x
+ |
+
+Obtaining a notification
+ |
+√
+ |
+√
+ |
+
+Deleting a notification
+ |
+√
+ |
+x
+ |
+
+Adding a notification
+ |
+√
+ |
+x
+ |
+
+Modifying a notification
+ |
+√
+ |
+x
+ |
+
+Obtaining URL tracing configuration
+ |
+√
+ |
+√
+ |
+
+Deleting URL tracing configuration
+ |
+√
+ |
+x
+ |
+
+Adding a URL for tracing
+ |
+√
+ |
+x
+ |
+
+Modifying URL tracing configuration
+ |
+√
+ |
+x
+ |
+
+Querying a URL tracing view
+ |
+√
+ |
+√
+ |
+
+Obtaining the URL tracing list
+ |
+√
+ |
+√
+ |
+
+Obtaining the global topology
+ |
+√
+ |
+√
+ |
+
+Querying a sub-application
+ |
+√
+ |
+√
+ |
+
+Querying environment configuration
+ |
+√
+ |
+√
+ |
+
+Adding environment configuration
+ |
+√
+ |
+x
+ |
+
+Deleting environment configuration
+ |
+√
+ |
+x
+ |
+
+Modifying environment configuration
+ |
+√
+ |
+x
+ |
+
+Obtaining an instance
+ |
+√
+ |
+√
+ |
+
+Deleting an instance
+ |
+√
+ |
+x
+ |
+
+Modifying an instance
+ |
+√
+ |
+x
+ |
+
+Querying a monitoring item
+ |
+√
+ |
+√
+ |
+
+Modifying a monitoring item
+ |
+√
+ |
+x
+ |
+
+Obtaining collection status
+ |
+√
+ |
+√
+ |
+
+Obtaining a custom alarm policy
+ |
+√
+ |
+√
+ |
+
+Deleting a custom alarm policy
+ |
+√
+ |
+x
+ |
+
+Modifying a custom alarm policy
+ |
+√
+ |
+x
+ |
+
+Creating a custom alarm policy
+ |
+√
+ |
+x
+ |
+
+Obtaining the environment topology
+ |
+√
+ |
+√
+ |
+
+Obtaining a metric view
+ |
+√
+ |
+√
+ |
+
+Obtaining the trace list
+ |
+√
+ |
+√
+ |
+
+Obtaining trace details
+ |
+√
+ |
+√
+ |
+
+Obtaining collector information
+ |
+√
+ |
+√
+ |
+
+Obtaining an access key
+ |
+√
+ |
+x
+ |
+
+Modifying an access key
+ |
+√
+ |
+x
+ |
+
+Deleting an access key
+ |
+√
+ |
+x
+ |
+
+Adding an access key
+ |
+√
+ |
+x
+ |
+
+Obtaining general configuration
+ |
+√
+ |
+√
+ |
+
+Modifying general configuration
+ |
+√
+ |
+x
+ |
+
+Querying Agent statistics
+ |
+√
+ |
+√
+ |
+
+
+
+
+
+
Privacy and Sensitive Information Protection Statement
+All O&M data will be displayed on the APM console. Therefore, you are not advised to upload your privacy or sensitive data to APM. If you need to upload such data, encrypt them.
+
Data Collection
+After you enable data collection, APM collects application performance metrics and tracing data. Your personal privacy data will not be collected. The collected data will be used only for application performance analysis and fault diagnosis, and will not be used for commercial purposes.
+
+
Data Type
+ |
+Collected Data
+ |
+Transmission Mode
+ |
+Storage Mode
+ |
+Function
+ |
+Storage Period
+ |
+
|---|
+
+Performance metric data
+ |
+JVM data, exceptions, databases, SQL statements, and middleware call data
+ |
+WebSocket Secure (WSS)
+ |
+Tenant-based isolated storage on the server
+ |
+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.
+ |
+
+Tracing data
+ |
+Trace event data, including middleware invocation data
+ |
+WSS
+ |
+Tenant-based isolated storage on the server
+ |
+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.
+ |
+
+Resource information
+ |
+Service type, service name, creation time, deletion time, node address, and service release API
+ |
+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.
+ |
+
+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.
+ |
+
+
+
+
+
+
Table 1 Restrictions on collection itemsCollection Item
+ |
+Maximum Value
+ |
+
|---|
+
+Monitoring item rows
+ |
+500
+ |
+
+SQL length
+ |
+2000 characters
+ |
+
+SQL result bodies
+ |
+100
+ |
+
+SQL result body content
+ |
+999 characters
+ |
+
+Redis body length
+ |
+100 characters
+ |
+
+Mongo clusters
+ |
+10
+ |
+
+Mongo command length
+ |
+2000 characters
+ |
+
+HBase command length
+ |
+500 characters
+ |
+
+ES RestClients
+ |
+10
+ |
+
+Cassandra CQL length
+ |
+2000 characters
+ |
+
+Cassandra sessions
+ |
+10
+ |
+
+Kafka MBean object names
+ |
+100
+ |
+
+Cache IP addresses corresponding to Kafka client IDs
+ |
+100
+ |
+
+RabbitMQ connection addresses
+ |
+20
+ |
+
+Cache connections for each RabbitMQ address
+ |
+100
+ |
+
+RabbitMQ consumers
+ |
+500
+ |
+
+Cache channels for each RabbitMQ consumer
+ |
+100
+ |
+
+RabbitMQ messages without ACK in each channel
+ |
+3000
+ |
+
+Manual ACK consumers in RabbitMQ cache
+ |
+20
+ |
+
+RocketMQ PIDs
+ |
+20
+ |
+
+RocketMQ client IDs
+ |
+20
+ |
+
+Jetcd tag length
+ |
+500 characters
+ |
+
+HttpClient connections
+ |
+10
+ |
+
+Report time of connection pool trace
+ |
+1 ms
+ |
+
+Dubbo invocation length
+ |
+500 characters
+ |
+
+Dubbo attachment length
+ |
+500 characters
+ |
+
+URL body length
+ |
+9999 characters
+ |
+
+Application code body length
+ |
+0 characters
+ |
+
+Java method body length
+ |
+8192 characters
+ |
+
+
+
+
+
Usage Restrictions
+
+
+
diff --git a/docs/apm/umn/apm_01_0013.html b/docs/apm/umn/apm_01_0013.html
new file mode 100644
index 00000000..657fc101
--- /dev/null
+++ b/docs/apm/umn/apm_01_0013.html
@@ -0,0 +1,40 @@
+
+
+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.
+
+
Exception
+This section describes the types, names, and meanings of exception metrics collected by APM.
+
+
Table 1 Exception collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Determine Trace Exception upon Log Error Detection
+ |
+radio
+ |
+JAVA
+ |
+true
+ |
+2.0.0
+ |
+-
+ |
+Whether to mark a trace as abnormal after a log error is collected.
+ |
+
+
+
+
+
+
Table 2 Exception metric descriptionCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Exception logs (exception: statistics about all exception logs)
+ |
+className
+ |
+className
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+logType
+ |
+logType
+ |
+Exception log type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times that an exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Log version (logVersion: package version of the log component)
+ |
+logType
+ |
+logType
+ |
+Log type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+version
+ |
+version
+ |
+Log version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+
+
+
+
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.
+
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.
+
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.
+
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.
+
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.
+
Agent Monitoring
+This section describes the types, names, and meanings of Agent monitoring metrics collected by APM.
+
+
Table 1 Agent monitoring metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Probe data (detail: probe data metric set)
+ |
+type
+ |
+type
+ |
+Type of data reported by the probe
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+discardBytes
+ |
+discardBytes
+ |
+Number of discarded bytes
+ |
+Byte
+ |
+INT
+ |
+SUM
+ |
+
+discardCount
+ |
+discardCount
+ |
+Number of times that the type of data is discarded
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorBytes
+ |
+errorBytes
+ |
+Number of bytes that fail to be sent
+ |
+Byte
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of times that the type of data fails to be sent
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxBytes
+ |
+maxBytes
+ |
+Maximum number of sent bytes
+ |
+Byte
+ |
+INT
+ |
+MAX
+ |
+
+maxQueueSize
+ |
+maxQueueSize
+ |
+Maximum length of the sending queue
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+sendBytes
+ |
+sendBytes
+ |
+Number of successfully sent bytes
+ |
+Byte
+ |
+INT
+ |
+SUM
+ |
+
+sendCount
+ |
+sendCount
+ |
+Number of times that the type of data is successfully sent
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+sendTotalTime
+ |
+sendTotalTime
+ |
+Total sending time of the data type
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+slowTime
+ |
+slowTime
+ |
+Maximum sending time of the data type
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+Exception (exception: exception metric set)
+ |
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+type
+ |
+type
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of exceptions
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Exception message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Server connection monitoring (transfer: server connection monitoring metric set)
+ |
+host
+ |
+host
+ |
+Host information
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+connectIp
+ |
+connectIp
+ |
+Connection IP address
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+ipList
+ |
+ipList
+ |
+All IP addresses
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+isConnected
+ |
+isConnected
+ |
+Connected or not
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+rt
+ |
+rt
+ |
+Response time
+ |
+ms
+ |
+INT
+ |
+AVG
+ |
+
+Queue monitoring (repository: queue monitoring metric set)
+ |
+monitorQueueSize
+ |
+monitorQueueSize
+ |
+Size of the monitoring data queue
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+monitorObjectSize
+ |
+monitorObjectSize
+ |
+Memory size of the monitoring data
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+traceQueueSize
+ |
+traceQueueSize
+ |
+Size of the trace data queue
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+traceObjectSize
+ |
+traceObjectSize
+ |
+Memory size of the trace data
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
Tomcat Monitoring
+This section describes the types, names, and meanings of Tomcat metrics collected by APM.
+
+
Table 1 Tomcat metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Tomcat information (tomcatInfo: Tomcat package version statistics)
+ |
+tomcatVersion
+ |
+tomcatVersion
+ |
+Tomcat version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Tomcat port monitoring (tomcat: APM counts statistics of Tomcat threads and connections by Tomcat port.)
+ |
+name
+ |
+name
+ |
+Port name
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+currentThreadCount
+ |
+currentThreadCount
+ |
+Number of current threads on the port
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+currentThreadsBusy
+ |
+currentThreadsBusy
+ |
+Number of busy threads on the port at the time of collection
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+currentThreadsBusyMax
+ |
+currentThreadsBusyMax
+ |
+Maximum number of busy threads on the port in a collection period
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+maxThreads
+ |
+maxThreads
+ |
+Maximum number of threads on the port
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+maxConnections
+ |
+maxConnections
+ |
+Maximum number of connections on the port
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+connectionCount
+ |
+connectionCount
+ |
+Number of current connections of the port at the time of collection
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+connectionCountMax
+ |
+connectionCountMax
+ |
+Maximum number of connections on the port in a collection period
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+
+
+
+
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.
+
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.
+
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.
+
Communication Protocol
+This section describes the types, names, and meanings of WebSocket metrics collected by APM.
+
+
Table 1 WebSocket metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Exception (exception: WebSocket exception statistics)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+WebSocket message monitoring (message: WebSocket message processing information)
+ |
+url
+ |
+url
+ |
+URL corresponding to WebSocket
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message processing errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the message processing method is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+traffic
+ |
+traffic
+ |
+Traffic
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+createSessionCount
+ |
+createSessionCount
+ |
+Number of connections that have been created
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+closeSessionCount
+ |
+closeSessionCount
+ |
+Number of closed connections
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+closeReason
+ |
+closeReason
+ |
+Cause of the connection closure
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+WebSocket summary (total: summary statistics)
+ |
+errorCount
+ |
+errorCount
+ |
+Total number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Total number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+createSessionCount
+ |
+createSessionCount
+ |
+Number of connections that have been created
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+closeSessionCount
+ |
+closeSessionCount
+ |
+Number of closed connections
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+traffic
+ |
+traffic
+ |
+Traffic
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
GC Monitoring
+This section describes the types, names, and meanings of GC metrics collected by APM.
+
+
Table 1 GC metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+GC statistics (gc)
+ |
+fullGCCount
+ |
+fullGCCount
+ |
+Number of full GC times in a collection period
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+fullGCCountTotal
+ |
+fullGCCountTotal
+ |
+Total number of full GC times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+fullGCTime
+ |
+fullGCTime
+ |
+Full GC duration in a collection period
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+fullGCTimeTotal
+ |
+fullGCTimeTotal
+ |
+Total full GC duration
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+fullGCMBeanName
+ |
+fullGCMBeanName
+ |
+Name of the full GC recycler
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+youngGCCount
+ |
+youngGCCount
+ |
+Number of young GC times in a collection period
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+youngGCCountTotal
+ |
+youngGCCountTotal
+ |
+Total number of young GC times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+youngGCTime
+ |
+youngGCTime
+ |
+Young GC duration in a collection period
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+youngGCTimeTotal
+ |
+youngGCTimeTotal
+ |
+Total young GC duration
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+youngGCMBeanName
+ |
+youngGCMBeanName
+ |
+Name of the young GC recycler
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+GC details (gcdetail)
+ |
+action
+ |
+action
+ |
+GC type, which can be major or minor
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+cause
+ |
+cause
+ |
+GC cause
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+name
+ |
+name
+ |
+GC collector name
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times that GC has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+GC duration
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Time consumed by the slowest GC
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+detail
+ |
+detail
+ |
+Details about the slowest GC
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+
+
+
+
JavaMethod
+This section describes the types, names, and meanings of JavaMethod metrics collected by APM.
+
+
Table 1 JavaMethod collection parameterParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Method Interception Configuration
+ |
+obj_array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+Specify methods to intercept. Use commas (,) to separate methods. If this parameter is left blank, all public methods will be intercepted by default.
+ |
+
+
+
+
+
+
Table 2 JavaMethod metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Java method (method: Method call statistics are collected based on the configured Java method names.)
+
+ |
+class
+ |
+class
+ |
+Class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+method
+ |
+method
+ |
+Method
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the method
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of times that the method fails to be called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the method is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error information of the method
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the method
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of executions of the method at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of the method
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
JVM Monitoring
+This section describes the types, names, and meanings of JVM metrics collected by APM.
+
+
Table 1 Collection parameters for JVM monitoringParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Trace Stack Collection Threshold
+ |
+integer
+ |
+JAVA
+ |
+0
+ |
+2.0.4
+ |
+-
+ |
+Stacks will be automatically printed when the request latency exceeds the threshold.
+ |
+
+
+
+
+
+
Table 2 JVM monitoring metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Class loading (classLoading: JVM class loading statistics)
+ |
+loadedClassCount
+ |
+loadedClassCount
+ |
+Number of loaded classes
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalLoadedClassCount
+ |
+totalLoadedClassCount
+ |
+Total number of loaded classes
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+unloadedClassCount
+ |
+unloadedClassCount
+ |
+Number of unloaded classes
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Compilation (compile: JVM class compilation time statistics)
+ |
+compilationTime
+ |
+compilationTime
+ |
+Compilation time in a collection period
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+totalCompilationTime
+ |
+totalCompilationTime
+ |
+Total compilation time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+CPU (CPU: CPU usage statistics of JVM processes)
+ |
+cpuRatio
+ |
+cpuRatio
+ |
+CPU usage of the Java process
+ |
+%
+ |
+DOUBLE
+ |
+AVG
+ |
+
+cpuRatioMax
+ |
+cpuRatioMax
+ |
+Maximum CPU usage of the Java process
+ |
+%
+ |
+DOUBLE
+ |
+MAX
+ |
+
+cpuTimeInterval
+ |
+cpuTimeInterval
+ |
+CPU time of the Java process in the collection interval
+ |
+ns
+ |
+INT
+ |
+SUM
+ |
+
+processorCount
+ |
+processorCount
+ |
+Number of processors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+systemTimeInterval
+ |
+systemTimeInterval
+ |
+Collection interval
+ |
+ns
+ |
+INT
+ |
+SUM
+ |
+
+totalCpuTime
+ |
+totalCpuTime
+ |
+Total CPU time
+ |
+ns
+ |
+INT
+ |
+SUM
+ |
+
+Memory (memory: JVM memory statistics)
+ |
+directMemoryUsage
+ |
+directMemoryUsage
+ |
+Used direct memory
+ |
+M
+ |
+INT
+ |
+AVG
+ |
+
+directMemoryCapacity
+ |
+directMemoryCapacity
+ |
+Total direct memory capacity
+ |
+M
+ |
+INT
+ |
+AVG
+ |
+
+heapMemoryUsage
+ |
+heapMemoryUsage
+ |
+Used heap memory
+ |
+M
+ |
+INT
+ |
+AVG
+ |
+
+nonHeapMemoryUsage
+ |
+nonHeapMemoryUsage
+ |
+Used non-heap memory
+ |
+M
+ |
+INT
+ |
+AVG
+ |
+
+objectPendingFinalizationCount
+ |
+objectPendingFinalizationCount
+ |
+Number of objects that are being recycled at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Memory pool (memoryPool: statistics collected by JVM memory pool)
+ |
+committed
+ |
+committed
+ |
+Available memory
+ |
+Byte
+ |
+INT
+ |
+SUM
+ |
+
+init
+ |
+init
+ |
+Initialized memory
+ |
+Byte
+ |
+INT
+ |
+SUM
+ |
+
+max
+ |
+max
+ |
+Maximum memory
+ |
+Byte
+ |
+INT
+ |
+SUM
+ |
+
+name
+ |
+name
+ |
+Memory pool name
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+used
+ |
+used
+ |
+Used memory
+ |
+Byte
+ |
+INT
+ |
+SUM
+ |
+
+Thread (thread: JVM thread statistics)
+ |
+currentThreadCpuTime
+ |
+currentThreadCpuTime
+ |
+CPU time of the current thread
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+currentThreadUserTime
+ |
+currentThreadUserTime
+ |
+User time of the current thread
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+daemonThreadCount
+ |
+daemonThreadCount
+ |
+Number of daemon threads
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+deadlockedThreadsCount
+ |
+deadlockedThreadsCount
+ |
+Number of deadlock threads
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+monitorDeadlockedThreads
+ |
+monitorDeadlockedThreads
+ |
+ID list of current deadlock threads
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+peakThreadCount
+ |
+peakThreadCount
+ |
+Maximum number of threads executed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+threadCount
+ |
+threadCount
+ |
+Number of current threads
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalStartedThreadCount
+ |
+totalStartedThreadCount
+ |
+Total number of threads that are started since the Java process is started
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+newThreadCount
+ |
+newThreadCount
+ |
+Number of threads in the initial state
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runnableThreadCount
+ |
+runnableThreadCount
+ |
+Number of running threads
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+blockedThreadCount
+ |
+blockedThreadCount
+ |
+Number of blocked threads
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+waitingThreadCount
+ |
+waitingThreadCount
+ |
+Number of pending threads
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+timedWaitingThreadCount
+ |
+timedWaitingThreadCount
+ |
+Number of threads that timed out
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+terminatedThreadCount
+ |
+terminatedThreadCount
+ |
+Number of terminated threads
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
JVMInfo
+This section describes the types, names, and meanings of JVMInfo metrics collected by APM.
+
+
Table 1 JVMInfo metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Basic JVM information (info: JVM and JavaAgent basic information)
+ |
+arch
+ |
+arch
+ |
+CPU architecture
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+availableProcessors
+ |
+availableProcessors
+ |
+Number of processors
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+bootClassPath
+ |
+bootClassPath
+ |
+Path of the startup class library
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+classPath
+ |
+classPath
+ |
+Class path
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+fileEncode
+ |
+fileEncode
+ |
+JVM file code
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+inputArguments
+ |
+inputArguments
+ |
+JVM startup parameter
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+javaCollectorVersion
+ |
+javaCollectorVersion
+ |
+Collector version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+javaHome
+ |
+javaHome
+ |
+Java home path
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+javaLibraryPath
+ |
+javaLibraryPath
+ |
+Java class library path
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+javaSpecificationVersion
+ |
+javaSpecificationVersion
+ |
+Java specification version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+javaVersion
+ |
+javaVersion
+ |
+Java version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+jvm
+ |
+jvm
+ |
+Mode
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+name
+ |
+name
+ |
+Server and process names
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+osName
+ |
+osName
+ |
+OS
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+osVersion
+ |
+osVersion
+ |
+OS version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+pid
+ |
+pid
+ |
+Process ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+sdkVersion
+ |
+sdkVersion
+ |
+SDK version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+specName
+ |
+specName
+ |
+Name of the VM specifications
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+specVendor
+ |
+specVendor
+ |
+Vendor that formulates the VM specifications
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+specVersion
+ |
+specVersion
+ |
+Version of the VM specifications
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+startTime
+ |
+startTime
+ |
+JVM startup time
+ |
+-
+ |
+DATETIME
+ |
+LAST
+ |
+
+systemLoadAverage
+ |
+systemLoadAverage
+ |
+Average system load
+ |
+-
+ |
+DOUBLE
+ |
+LAST
+ |
+
+uptime
+ |
+uptime
+ |
+VM running time
+ |
+ms
+ |
+INT
+ |
+LAST
+ |
+
+vmName
+ |
+vmName
+ |
+VM name
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+vmVendor
+ |
+vmVendor
+ |
+VM vendor
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+vmVersion
+ |
+vmVersion
+ |
+VM version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+
+
+
+
Netty Memory
+This section describes the types, names, and meanings of Netty memory metrics collected by APM.
+
+
Table 1 Netty memory metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Memory (memory: memory metrics)
+ |
+directMemoryUsage
+ |
+directMemoryUsage
+ |
+Used direct memory
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+maxDirectMemory
+ |
+maxDirectMemory
+ |
+Maximum direct memory
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+Exception (exception)
+ |
+causeType
+ |
+causeType
+ |
+Class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Count
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Exception message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+
+
+
+
Threads
+This section describes the types, names, and meanings of thread metrics collected by APM.
+
+
Table 1 Thread collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Max. Rows of Thread Details
+ |
+integer
+ |
+JAVA
+ |
+1
+ |
+2.3.19
+ |
+-
+ |
+Maximum number of rows of thread details. You can set it to up to 50.
+ |
+
+
+
+
+
+
Table 2 Thread metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Thread details (threadDetail)
+ |
+threadName
+ |
+threadName
+ |
+Thread name
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+memory
+ |
+memory
+ |
+Memory
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+stack
+ |
+stack
+ |
+Thread stack
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+ids
+ |
+ids
+ |
+Thread ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+cpuTime
+ |
+cpuTime
+ |
+Thread CPU time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+count
+ |
+count
+ |
+Number of threads
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+
+
+
+
C3P0 Connection Pool Monitoring
+This section describes the types, names, and meanings of C3P0 connection pool metrics collected by APM.
+
+
Table 1 Collection parameters for C3P0 connection pool monitoringParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Threshold (ms) for Reporting Connection Trace
+ |
+integer
+ |
+JAVA
+ |
+1
+ |
+2.1.3
+ |
+-
+ |
+Threshold for reporting getConnection method traces. If the threshold is not exceeded, such traces will not be reported.
+ |
+
+Obtain Pool Info or Not
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.1.3
+ |
+-
+ |
+Whether to obtain pool information when getting connections
+ |
+
+
+
+
+
+
Table 2 C3P0 connection pool metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Data source (dataSource)
+ |
+url
+ |
+URL
+ |
+URL
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+driverClass
+ |
+driverClass
+ |
+Driver
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+initialPoolSize
+ |
+initialPoolSize
+ |
+Number of initialized connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+minPoolSize
+ |
+minPoolSize
+ |
+Minimum connection pool size
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+maxPoolSize
+ |
+maxPoolSize
+ |
+Maximum connection pool size
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+numIdleConnections
+ |
+numIdleConnections
+ |
+Number of idle connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+numBusyConnections
+ |
+numBusyConnections
+ |
+Number of busy connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+numConnections
+ |
+numConnections
+ |
+Total number of connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+maxIdleTime
+ |
+maxIdleTime
+ |
+Maximum connection idle time
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+idleConnectionTestPeriod
+ |
+idleConnectionTestPeriod
+ |
+Interval for checking for idle connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+testConnectionOnCheckout
+ |
+testConnectionOnCheckout
+ |
+Connection validity check during check-out
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+testConnectionOnCheckin
+ |
+testConnectionOnCheckin
+ |
+Connection validity check during check-in
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+acquireRetryAttempts
+ |
+acquireRetryAttempts
+ |
+Number of Connection retry times
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+acquireRetryDelay
+ |
+acquireRetryDelay
+ |
+Connection retry interval
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+acquireIncrement
+ |
+acquireIncrement
+ |
+Number of connections created if no connection exists
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+Connection details (connection)
+ |
+url
+ |
+url
+ |
+Connection address
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total time
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+Version (version)
+ |
+version
+ |
+version
+ |
+Version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Exception (exception: C3P0 call exception statistics)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+
+
+
+
Cassandra Monitoring
+This section describes the types, names, and meanings of Cassandra metrics collected by APM.
+
+
Table 1 Collection parameters for Cassandra monitoringParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Threshold (ms) for Reporting Connection Trace
+ |
+integer
+ |
+JAVA
+ |
+1
+ |
+2.2.9
+ |
+-
+ |
+Threshold for reporting borrowConnection() method traces. If the threshold is not exceeded, such traces will not be reported.
+ |
+
+Collect Original CQL Statement or Not
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.2.9
+ |
+-
+ |
+Whether to collect original CQL statements
+ |
+
+
+
+
+
+
Table 2 Cassandra metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+CQL call (Cql)
+ |
+cql
+ |
+cql
+ |
+Executed CQL Statement
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+queryRowCount
+ |
+queryRowCount
+ |
+Number of read rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of executions of the method at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Cassandra node call (node)
+ |
+node
+ |
+node
+ |
+Node address
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Cassandra cluster call (cluster)
+ |
+nodes
+ |
+nodes
+ |
+Cluster node information
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Connection details (connection)
+ |
+host
+ |
+host
+ |
+Connected host
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Exception (exception: Cassandra call exception statistics)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Cassandra summary (total: summary of Cassandra call statistics)
+ |
+invokeCount
+ |
+invokeCount
+ |
+Total number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+queryRowCount
+ |
+queryRowCount
+ |
+Total number of read rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Total number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Cassandra version (version)
+ |
+version
+ |
+version
+ |
+Version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+
+
+
+
ClickHouse Database
+This section describes the types, names, and meanings of ClickHouse database metrics collected by APM.
+
+
Table 1 ClickHouse database collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Collect Original SQL Statement or Not
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.0.0
+ |
+-
+ |
+Whether to collect and report original SQL statements
+ |
+
+
+
+
+
+
Table 2 ClickHouse database metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Database connection (connection: APM counts SQL call statistics by database.)
+ |
+db
+ |
+db
+ |
+Database name
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+createdCount
+ |
+createdCount
+ |
+Number of connections created by the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+currentCount
+ |
+currentCount
+ |
+Current number of connections of the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+destroyedCount
+ |
+destroyedCount
+ |
+Number of the database's connections that have been destroyed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors that the database encounters
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the database is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the database
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+readRowCount
+ |
+readRowCount
+ |
+Number of rows read from the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updatedRowCount
+ |
+updatedRowCount
+ |
+Number of rows updated in the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowestSql
+ |
+slowestSql
+ |
+Slowest SQL statement of the database in the collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Exception (exception: exception statistics about SQL calls)
+ |
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of exceptions
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Exception message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+sql
+ |
+sql
+ |
+SQL statement that encounters an exception
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Version (version: ClickHouse package version)
+ |
+version
+ |
+version
+ |
+Driver package version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+SQL monitoring (sql: APM counts call statistics by SQL.)
+ |
+sql
+ |
+sql
+ |
+Unique ID of the SQL statement, which is used for alarm configuration
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the SQL statement
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors that the SQL statement encounters
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the SQL statement is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+SQL error information
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the SQL statement
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+readRowCount
+ |
+readRowCount
+ |
+Number of read rows of the SQL statement
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of SQL statements that are being executed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+sqlString
+ |
+sqlString
+ |
+SQL statement
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updatedRowCount
+ |
+updatedRowCount
+ |
+Number of updated rows of the SQL statement
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Summary (total: summary about SQL statement call statistics)
+ |
+invokeCount
+ |
+invokeCount
+ |
+Total number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Total number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+readRowCount
+ |
+readRowCount
+ |
+Total number of read rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updatedRowCount
+ |
+updatedRowCount
+ |
+Total number of updated rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
DBCP Connection Pool Monitoring
+This section describes the types, names, and meanings of DBCP connection pool metrics collected by APM.
+
+
Table 1 DBCP connection pool collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Threshold (ms) for Reporting Connection Trace
+ |
+integer
+ |
+JAVA
+ |
+1
+ |
+2.1.3
+ |
+-
+ |
+Threshold for reporting getConnection method traces. If the threshold is not exceeded, such traces will not be reported.
+ |
+
+Obtain Pool Info or Not
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.1.3
+ |
+-
+ |
+Whether to obtain pool information when getting connections
+ |
+
+
+
+
+
+
Table 2 DBCP connection pool metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Data source (dataSource)
+ |
+url
+ |
+url
+ |
+url
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+driverClassName
+ |
+driverClassName
+ |
+Driver
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+initialSize
+ |
+initialSize
+ |
+Number of initialized connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+minIdle
+ |
+minIdle
+ |
+Minimum number of idle connections in the pool
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+maxIdle
+ |
+maxIdle
+ |
+Maximum number of idle connections in the pool
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+maxTotal
+ |
+maxTotal
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+numIdle
+ |
+numIdle
+ |
+Number of idle connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+numActive
+ |
+numActive
+ |
+Number of active connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+maxWaitMillis
+ |
+maxWaitMillis
+ |
+Maximum time for a waiting connection to be reclaimed (when no connection is available) before an exception is thrown
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+testOnCreate
+ |
+testOnCreate
+ |
+Whether to check the validity of a connection after it is created
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+testOnBorrow
+ |
+testOnBorrow
+ |
+Check whether a connection is valid before obtaining it from the connection pool.
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+testWhileIdle
+ |
+testWhileIdle
+ |
+Whether to verify the validity of an idle connection when an application applies for it from the pool
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+timeBetweenEvictionRunsMillis
+ |
+timeBetweenEvictionRunsMillis
+ |
+If testOnBorrow is set to false and testWhileIdle is set to true, the application checks whether the idle time of a connection is greater than timeBetweenEvictionRunsMillis before obtaining the connection. If it is greater than that value, the application checks whether the connection is valid.
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+removeAbandonedOnBorrow
+ |
+removeAbandonedOnBorrow
+ |
+Whether to remove discarded connections when obtaining connections. (The following conditions must be met: "getNumActive() > getMaxTotal() – 3" and "getNumIdle() < 2")
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+removeAbandonedOnMaintenance
+ |
+removeAbandonedOnMaintenance
+ |
+Whether to remove discarded connections in the maintenance cycle (when the eviction ends)
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+removeAbandonedTimeout
+ |
+removeAbandonedTimeout
+ |
+If a connection is not used within the specified timeout, it is regarded as a discarded connection and can be removed.
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+Connection details (connection)
+ |
+url
+ |
+url
+ |
+Connection address
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+Version (version)
+ |
+version
+ |
+version
+ |
+Version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Exception (exception: exception statistics of DBCP calls)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+
+
+
+
Druid Connection Pool Monitoring
+This section describes the types, names, and meanings of Druid connection pool metrics collected by APM.
+
+
Table 1 Druid connection pool collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Threshold (ms) for Reporting Connection Trace
+ |
+integer
+ |
+JAVA
+ |
+1
+ |
+2.1.3
+ |
+-
+ |
+Threshold for reporting getConnection method traces. If the threshold is not exceeded, such traces will not be reported.
+ |
+
+Obtain Pool Info or Not
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.1.3
+ |
+-
+ |
+Whether to obtain pool information when getting connections
+ |
+
+
+
+
+
+
Table 2 Druid connection pool metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Data source (dataSource)
+ |
+url
+ |
+url
+ |
+url
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+dbType
+ |
+dbType
+ |
+Database type
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+driverClassName
+ |
+driverClassName
+ |
+Driver
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+initialSize
+ |
+initialSize
+ |
+Number of initialized connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+minIdle
+ |
+minIdle
+ |
+Minimum number of idle connections in the pool
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+maxIdle
+ |
+maxIdle
+ |
+Maximum number of idle connections in the pool
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+maxActive
+ |
+maxActive
+ |
+Maximum connection pool size
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+waitThreadCount
+ |
+waitThreadCount
+ |
+Number of waiting threads
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+maxWaitThreadCount
+ |
+maxWaitThreadCount
+ |
+Maximum number of waiting threads
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+poolingCount
+ |
+poolingCount
+ |
+Number of connections in the pool
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+poolingPeak
+ |
+poolingPeak
+ |
+Maximum number of connections in the pool
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+activeCount
+ |
+activeCount
+ |
+Number of active connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+activePeak
+ |
+activePeak
+ |
+Maximum number of active connections
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+logicConnectCount
+ |
+logicConnectCount
+ |
+Total number of connections
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxWait
+ |
+maxWait
+ |
+Maximum waiting time of a connection
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+removeAbandoned
+ |
+removeAbandoned
+ |
+Whether to automatically reclaim timeout connections
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+removeAbandonedCount
+ |
+removeAbandonedCount
+ |
+Number of times that timeout connections are reclaimed
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+removeAbandonedTimeoutMillis
+ |
+removeAbandonedTimeoutMillis
+ |
+If a connection in the pool is not returned within the specified duration, the connection will be reclaimed.
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+testWhileIdle
+ |
+testWhileIdle
+ |
+Whether to verify the validity of an idle connection when an application applies for it from the pool
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+testOnBorrow
+ |
+testOnBorrow
+ |
+Check whether a connection is valid before obtaining it from the connection pool.
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+testOnReturn
+ |
+testOnReturn
+ |
+Whether to verify the validity of a connection when it is returned
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+minEvictableIdleTimeMillis
+ |
+minEvictableIdleTimeMillis
+ |
+Idle time that is allowed for connections in the pool
+ |
+ms
+ |
+INT
+ |
+LAST
+ |
+
+timeBetweenEvictionRunsMillis
+ |
+timeBetweenEvictionRunsMillis
+ |
+Interval for checking the validity of idle connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+Connection details (connection)
+ |
+url
+ |
+url
+ |
+Connection address
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+Version (version)
+ |
+version
+ |
+version
+ |
+Version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Exception (exception: exception statistics of Druid calls)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+
+
+
+
EsRestClient Monitoring
+This section describes the types, names, and meanings of EsRestClient metrics collected by APM.
+
+
Table 1 EsRestClient collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Index Normalization Configuration
+ |
+obj_array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+Implement "regex" matching and normalize the URL index.
+ |
+
+
+
+
+
+
Table 2 EsRestClient metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Exception (exception: exception statistics of EsRestClient calls)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Client information (clientInfo)
+ |
+clientId
+ |
+clientId
+ |
+Client ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+RestClientVersion
+ |
+RestClientVersion
+ |
+RestClient version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+RestHighLevelClientVersion
+ |
+RestHighLevelClientVersion
+ |
+RestHighLevelClient version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+poolId
+ |
+poolId
+ |
+HttpAsyncClient Connection pool ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+esNodes
+ |
+esNodes
+ |
+Cluster node information set on the client
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+esDeadNodes
+ |
+esDeadNodes
+ |
+Disconnected node of the cluster
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+URL monitoring (esClient: APM counts URL call statistics by URL.)
+ |
+clientId
+ |
+clientId
+ |
+RESTClient ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+url
+ |
+url
+ |
+Called URL
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+method
+ |
+method
+ |
+HTTP method of the URL
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the URL
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of call errors of the URL
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+definitiveFailureCount
+ |
+definitiveFailureCount
+ |
+Number of request errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+hostUri
+ |
+hostUri
+ |
+host uri
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the URL is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error details
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the called URL
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of the called URL
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+retryCount
+ |
+retryCount
+ |
+Request retry times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Status code statistics (code: APM counts URL call statistics by status code.)
+ |
+code
+ |
+code
+ |
+Status code
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+url
+ |
+url
+ |
+URL that returns the status code
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times that the status code has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+EsRestClient summary (total: summary of EsRestClient call statistics)
+ |
+definitiveFailureCount
+ |
+definitiveFailureCount
+ |
+Total number of request errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Total number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+retryCount
+ |
+retryCount
+ |
+Total number of request retries
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+EsRestClient node call monitoring (serverNode)
+ |
+serverAddr
+ |
+serverAddr
+ |
+Server node information
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+URL monitoring (invocation: APM counts URL call statistics by URL.)
+ |
+url
+ |
+url
+ |
+Called URL
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+method
+ |
+method
+ |
+HTTP method of the URL
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+client
+ |
+client
+ |
+EsRestClient type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the URL
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of call errors of the URL
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+hostUri
+ |
+hostUri
+ |
+Called URL address
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the URL is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error details
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the called URL
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+responseCloseCount
+ |
+responseCloseCount
+ |
+Number of closed responses when the URL is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of the called URL
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+envId
+ |
+envId
+ |
+Cluster ID corresponding to the called URL
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+EsRestClient cluster call (cluster)
+ |
+esNodes
+ |
+esNodes
+ |
+Cluster node information
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+clientCount
+ |
+clientCount
+ |
+Number of RestClients that have been created
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
GaussDB Database
+This section describes the types, names, and meanings of GaussDB database metrics collected by APM.
+
+
Table 1 GaussDB database collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Collect Original SQL Statement or Not
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.2.8
+ |
+-
+ |
+Whether to collect and report original SQL statements
+ |
+
+
+
+
+
+
Table 2 GaussDB database metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Database connection (connection: APM counts SQL call statistics by database.)
+ |
+db
+ |
+db
+ |
+Database name
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+createdCount
+ |
+createdCount
+ |
+Number of connections created by the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+currentCount
+ |
+currentCount
+ |
+Current number of connections of the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+destroyedCount
+ |
+destroyedCount
+ |
+Number of the database's connections that have been destroyed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors that the database encounters
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the database is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the database
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+ranges
+ |
+ranges
+ |
+Custom response time range
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+readRowCount
+ |
+readRowCount
+ |
+Number of rows read from the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updatedRowCount
+ |
+updatedRowCount
+ |
+Number of rows updated in the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowestSql
+ |
+slowestSql
+ |
+Slowest SQL statement of the database in the collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Exception (exception: exception statistics about SQL calls)
+ |
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of exceptions
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Exception message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+sql
+ |
+sql
+ |
+SQL statement that encounters an exception
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Version (version: GaussDB package version)
+ |
+version
+ |
+version
+ |
+Driver package version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+SQL monitoring (sql: APM counts call statistics by SQL.)
+ |
+sql
+ |
+sql
+ |
+Unique ID of the SQL statement, which is used for alarm configuration
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the SQL statement
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors that the SQL statement encounters
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the SQL statement is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+SQL error information
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the SQL statement
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+readRowCount
+ |
+readRowCount
+ |
+Number of read rows of the SQL statement
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of SQL statements that are being executed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+sqlString
+ |
+sqlString
+ |
+SQL statement
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updatedRowCount
+ |
+updatedRowCount
+ |
+Number of updated rows of the SQL statement
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+ranges
+ |
+ranges
+ |
+Custom response time range
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Summary (total: summary about SQL statement call statistics)
+ |
+invokeCount
+ |
+invokeCount
+ |
+Total number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Total number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+readRowCount
+ |
+readRowCount
+ |
+Total number of read rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updatedRowCount
+ |
+updatedRowCount
+ |
+Total number of updated rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
HBase Monitoring
+This section describes the types, names, and meanings of HBase metrics collected by APM.
+
+
Table 1 HBase metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Exception (exception: exception statistics of HBase calls)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+HBase call monitoring (client)
+ |
+namespaceTable
+ |
+namespaceTable
+ |
+Namespace and table name corresponding to the HBase operation
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+command
+ |
+command
+ |
+Command run on the HBase server
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+queryRowCount
+ |
+queryRowCount
+ |
+Number of read rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updateRowCount
+ |
+updateRowCount
+ |
+Number of updated rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total RT
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+HBase version (version)
+ |
+version
+ |
+version
+ |
+Version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+HBase summary (total: summary of HBase call statistics)
+ |
+invokeCount
+ |
+invokeCount
+ |
+Total number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+queryRowCount
+ |
+queryRowCount
+ |
+Total number of read rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updateRowCount
+ |
+updateRowCount
+ |
+Total number of updated rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Total number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+HBase node call monitoring (serverNode: HBase server RPC call statistics)
+ |
+serverAddr
+ |
+serverAddr
+ |
+Server node information
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+HBase cluster call monitoring (cluster: HBase cluster RPC call information)
+ |
+clusterId
+ |
+clusterId
+ |
+Cluster ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+cachedServers
+ |
+cachedServers
+ |
+Client cache node address
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+zkNodes
+ |
+zkNodes
+ |
+ZooKeeper connection address
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
Hikari Connection Pool Monitoring
+This section describes the types, names, and meanings of Hikari connection pool metrics collected by APM.
+
+
Table 1 Hikari connection pool collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Threshold (ms) for Reporting Connection Trace
+ |
+integer
+ |
+JAVA
+ |
+1
+ |
+2.1.0
+ |
+-
+ |
+Threshold for reporting getConnection method traces. If the threshold is not exceeded, such traces will not be reported.
+ |
+
+Obtain Pool Info or Not
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.1.0
+ |
+-
+ |
+Whether to obtain pool information when getting connections
+ |
+
+
+
+
+
+
Table 2 Hikari connection pool metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Data source (dataSource)
+ |
+url
+ |
+url
+ |
+url
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+maximumPoolSize
+ |
+maximumPoolSize
+ |
+Maximum number of connections that are allowed
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+leakDetectionThreshold
+ |
+leakDetectionThreshold
+ |
+Maximum connection pool size
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+validationTimeout
+ |
+validationTimeout
+ |
+Number of waiting threads
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+maxLifetime
+ |
+maxLifetime
+ |
+Maximum number of waiting threads
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+poolingCount
+ |
+poolingCount
+ |
+Number of connections in the pool
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+poolingPeak
+ |
+poolingPeak
+ |
+Maximum number of connections in the pool
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+activeCount
+ |
+activeCount
+ |
+Number of active connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+activePeak
+ |
+activePeak
+ |
+Maximum number of active connections
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+logicConnectCount
+ |
+logicConnectCount
+ |
+Total number of connections
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxWait
+ |
+maxWait
+ |
+Max. Waiting Time
+ |
+ms
+ |
+INT
+ |
+LAST
+ |
+
+removeAbandoned
+ |
+removeAbandoned
+ |
+Whether to automatically reclaim timeout connections
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+removeAbandonedCount
+ |
+removeAbandonedCount
+ |
+Number of times that timeout connections are reclaimed
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+removeAbandonedTimeoutMillis
+ |
+removeAbandonedTimeoutMillis
+ |
+If a connection in the pool is not returned within the specified duration, the connection will be reclaimed.
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+testWhileIdle
+ |
+testWhileIdle
+ |
+Whether to verify the validity of an idle connection when an application applies for it from the pool
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+testOnBorrow
+ |
+testOnBorrow
+ |
+Check whether a connection is valid before obtaining it from the connection pool.
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+testOnReturn
+ |
+testOnReturn
+ |
+Whether to verify the validity of a connection when it is returned
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+minEvictableIdleTimeMillis
+ |
+minEvictableIdleTimeMillis
+ |
+Idle time that is allowed for connections in the pool
+ |
+ms
+ |
+INT
+ |
+LAST
+ |
+
+timeBetweenEvictionRunsMillis
+ |
+timeBetweenEvictionRunsMillis
+ |
+Interval for checking the validity of idle connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+driverName
+ |
+driverName
+ |
+Driver
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalConnections
+ |
+totalConnections
+ |
+Total number of connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+activeConnections
+ |
+activeConnections
+ |
+Number of active connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+idleConnections
+ |
+idleConnections
+ |
+Number of idle connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+threadsAwaitingConnection
+ |
+threadsAwaitingConnection
+ |
+Number of waiting connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+Connection details (connection)
+ |
+url
+ |
+url
+ |
+Connection address
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Exception (exception: Hikari call exception statistics)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Version (version)
+ |
+version
+ |
+version
+ |
+Version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+
+
+
+
Jetcd Monitoring
+This section describes the types, names, and meanings of Jetcd metrics collected by APM.
+
+
Table 1 Jetcd collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Parse Value or Not
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.2.8
+ |
+-
+ |
+Whether to parse the value of the key-value pair. If it is not parsed, the value will be replaced with a question mark (?).
+ |
+
+
+
+
+
+
Table 2 Jetcd metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Exception (exception: Jetcd call exception statistics)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Jetcd UnaryRpc call monitoring (naryRpc)
+ |
+endpoints
+ |
+endpoints
+ |
+Address of the etcd cluster
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+request
+ |
+request
+ |
+Request type of the etcd API
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Jetcd Watch callback monitoring (watcher)
+ |
+listener
+ |
+listener
+ |
+Listener class name corresponding to WatchImpl
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Jetcd KeepAlive callback monitoring (KeepAlive)
+ |
+observers
+ |
+observers
+ |
+StreamObserver class name corresponding to KeepAlive
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Jetcd Election Observe callback monitoring (electionObserve)
+ |
+listener
+ |
+listener
+ |
+Listener bound to the observe call
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Jetcd summary (total)
+ |
+errorCount
+ |
+errorCount
+ |
+Total number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Total number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Jetcd version (version)
+ |
+version
+ |
+version
+ |
+Version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+
+
+
+
MongoDB Monitoring
+This section describes the types, names, and meanings of MongoDB metrics collected by APM.
+
+
Table 1 Collection parameters for MongoDB monitoringParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+TraceReportTimeSpanThreshold(ms)
+ |
+integer
+ |
+JAVA
+ |
+1
+ |
+2.1.13
+ |
+-
+ |
+Threshold for reporting getConnection method traces. If the threshold is not exceeded, such traces will not be reported.
+ |
+
+isParseOriginalCommand
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.2.2
+ |
+-
+ |
+Indicates whether to collect original Mongo JSON commands.
+ |
+
+
+
+
+
+
Table 2 MongoDB metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Connection details (connection)
+ |
+host
+ |
+host
+ |
+Connected host
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+openedCount
+ |
+openedCount
+ |
+Number of opened connections
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+closedCount
+ |
+closedCount
+ |
+Number of closed connections
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+idleClosedCount
+ |
+idleClosedCount
+ |
+Number of connections that are closed due to long idle time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lifeClosedCount
+ |
+lifeClosedCount
+ |
+Number of connections that are closed due to keepalive timeout
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorClosedCount
+ |
+errorClosedCount
+ |
+Number of connections that are closed due to errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+staleClosedCount
+ |
+staleClosedCount
+ |
+Number of connections that are closed due to pool clearing
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+poolClosedClosedCount
+ |
+poolClosedClosedCount
+ |
+Number of connections that are closed due to pool closure
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Exception (exception: exception statistics of MongoDB calls)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Cluster information (clusterInfo)
+ |
+clusterId
+ |
+clusterId
+ |
+Cluster ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+hosts
+ |
+hosts
+ |
+Cluster node information set on the client
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+MongoDB call monitoring (client)
+ |
+namespace
+ |
+namespace
+ |
+Namespace corresponding to the MongoDB operation
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+command
+ |
+command
+ |
+Command run on the MongoDB server
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+queryCount
+ |
+queryCount
+ |
+Number of read rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updateCount
+ |
+updateCount
+ |
+Number of updated rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+MongoDB version (version)
+ |
+version
+ |
+version
+ |
+Version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+MongoDB summary (total: summary of MongoDB call statistics)
+ |
+invokeCount
+ |
+invokeCount
+ |
+Total number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+queryCount
+ |
+queryCount
+ |
+Total number of read rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updateCount
+ |
+updateCount
+ |
+Total number of updated rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Total number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+MongoDB cluster call (cluster)
+ |
+nodes
+ |
+nodes
+ |
+Cluster node information
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Connection pool monitoring (connectionPool)
+ |
+host
+ |
+host
+ |
+Connection address
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+maxSize
+ |
+maxSize
+ |
+Maximum connection pool size
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+minSize
+ |
+minSize
+ |
+Minimum connection pool size
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+availableCount
+ |
+availableCount
+ |
+Number of idle connections
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+inUseCount
+ |
+inUseCount
+ |
+Number of active connections
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+maxWaitTimeMs
+ |
+maxWaitTimeMs
+ |
+Maximum waiting time of a connection (ms)
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+maxConnectionLifeTimeMs
+ |
+maxConnectionLifeTimeMs
+ |
+Maximum keepalive time of a connection
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+maxConnectionIdleTimeMs
+ |
+maxConnectionIdleTimeMs
+ |
+Maximum idle time of a connection
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+MongoDB node call monitoring (serverNode)
+ |
+serverAddr
+ |
+serverAddr
+ |
+Node address
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+type
+ |
+type
+ |
+Node type
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
MySQL Database
+This section describes the types, names, and meanings of MySQL database metrics collected by APM.
+
+
Table 1 MySQL database collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Collect Original SQL
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.0.0
+ |
+-
+ |
+Whether to collect and report original SQL statements
+ |
+
+shardTableName
+ |
+array
+ |
+JAVA
+ |
+-
+ |
+2.2.2
+ |
+-
+ |
+Table name specified for SQL statement aggregation. Tables starting with this name will be aggregated into the same table.
+ |
+
+
+
+
+
+
Table 2 MySQL database metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Database connection (connection: APM counts SQL call statistics by database.)
+ |
+db
+ |
+db
+ |
+Database name
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+createdCount
+ |
+createdCount
+ |
+Number of connections created by the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+currentCount
+ |
+currentCount
+ |
+Current number of connections of the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+destroyedCount
+ |
+destroyedCount
+ |
+Number of the database's connections that have been destroyed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors that the database encounters
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the database is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the database
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+readRowCount
+ |
+readRowCount
+ |
+Number of rows read from the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updatedRowCount
+ |
+updatedRowCount
+ |
+Number of rows updated in the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of the database
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+slowestSql
+ |
+slowestSql
+ |
+Slowest SQL statement of the database in the collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Exception (exception: exception statistics about SQL calls)
+ |
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of exceptions
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Exception message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+sql
+ |
+sql
+ |
+SQL statement that encounters an exception
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Version (version: MySQL package version)
+ |
+version
+ |
+version
+ |
+Driver package version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+SQL monitoring (sql: APM counts call statistics by SQL.)
+
+ |
+sql
+ |
+sql
+ |
+Unique ID of the SQL statement, which is used for alarm configuration
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the SQL statement
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors that the SQL statement encounters
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the SQL statement is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+SQL error information
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the SQL statement
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+readRowCount
+ |
+readRowCount
+ |
+Number of read rows of the SQL statement
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of SQL statements that are being executed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+sqlString
+ |
+sqlString
+ |
+SQL statement
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+updatedRowCount
+ |
+updatedRowCount
+ |
+Number of updated rows of the SQL statement
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Summary (total: summary about SQL statement call statistics)
+ |
+invokeCount
+ |
+invokeCount
+ |
+Total number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Total number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+readRowCount
+ |
+readRowCount
+ |
+Total number of read rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+updatedRowCount
+ |
+updatedRowCount
+ |
+Total number of updated rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
ObsClient Monitoring
+This section describes the types, names, and meanings of ObsClient metrics collected by APM.
+
+
Table 1 ObsClient metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Exception (exception: exception statistics of ObsClient calls)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+URL monitoring (obsClientInvocation: APM counts URL call statistics by URL.)
+ |
+client
+ |
+client
+ |
+client
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+url
+ |
+url
+ |
+Called URL
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+method
+ |
+method
+ |
+HTTP method of the URL
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the URL
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of call errors of the URL
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+hostUri
+ |
+hostUri
+ |
+hostUri
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the URL is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error details
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the called URL
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+responseCloseCount
+ |
+responseCloseCount
+ |
+Number of responses that are closed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of the called URL
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Status code statistics (code: APM counts URL call statistics by status code.)
+ |
+code
+ |
+code
+ |
+Status code
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+url
+ |
+url
+ |
+URL that returns the status code
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times that the status code has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+ObsClient summary (total)
+ |
+errorCount
+ |
+errorCount
+ |
+Total number of request errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Total number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
Oracle Database
+This section describes the types, names, and meanings of Oracle database metrics collected by APM.
+
+
Table 1 Oracle database collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Collect Original SQL Statement or Not
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.2.9
+ |
+-
+ |
+Whether to collect and report original SQL statements
+ |
+
+
+
+
+
+
Table 2 Oracle database metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Database connection (connection: APM counts SQL call statistics by database.)
+ |
+db
+ |
+db
+ |
+Database name
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+createdCount
+ |
+createdCount
+ |
+Number of connections created by the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+currentCount
+ |
+currentCount
+ |
+Current number of connections of the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+destroyedCount
+ |
+destroyedCount
+ |
+Number of the database's connections that have been destroyed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors that the database encounters
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the database is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the database
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+ranges
+ |
+ranges
+ |
+Custom response time range
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+readRowCount
+ |
+readRowCount
+ |
+Number of rows read from the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updatedRowCount
+ |
+updatedRowCount
+ |
+Number of rows updated in the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowestSql
+ |
+slowestSql
+ |
+Slowest SQL statement of the database in the collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Exception (exception: APM counts SQL call statistics by database.)
+ |
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of exceptions
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Exception message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+sql
+ |
+sql
+ |
+SQL statement that encounters an exception
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Version (version: Oracle package version)
+ |
+version
+ |
+version
+ |
+Driver package version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+SQL monitoring (sql: APM counts call statistics by SQL.)
+ |
+sql
+ |
+sql
+ |
+Unique ID of the SQL statement, which is used for alarm configuration
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the SQL statement
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors that the SQL statement encounters
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the SQL statement is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+SQL error information
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the SQL statement
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+readRowCount
+ |
+readRowCount
+ |
+Number of read rows of the SQL statement
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of SQL statements that are being executed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+sqlString
+ |
+sqlString
+ |
+SQL statement
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updatedRowCount
+ |
+updatedRowCount
+ |
+Number of updated rows of the SQL statement
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+ranges
+ |
+ranges
+ |
+Custom response time range
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Summary (total: summary about SQL statement call statistics)
+ |
+invokeCount
+ |
+invokeCount
+ |
+Total number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Total number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+readRowCount
+ |
+readRowCount
+ |
+Total number of read rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updatedRowCount
+ |
+updatedRowCount
+ |
+Total number of updated rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
PostgreSQL Database
+This section describes the types, names, and meanings of PostgreSQL database metrics collected by APM.
+
+
Table 1 PostgreSQL database collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Collect Original SQL Statement or Not
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.0.0
+ |
+-
+ |
+Whether to collect and report original SQL statements
+ |
+
+
+
+
+
+
Table 2 PostgreSQL database metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Database connection (connection: APM counts SQL call statistics by database.)
+ |
+db
+ |
+db
+ |
+Database name
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+createdCount
+ |
+createdCount
+ |
+Number of connections created by the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+currentCount
+ |
+currentCount
+ |
+Current number of connections of the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+destroyedCount
+ |
+destroyedCount
+ |
+Number of the database's connections that have been destroyed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors that the database encounters
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the database is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the database
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+readRowCount
+ |
+readRowCount
+ |
+Number of rows read from the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updatedRowCount
+ |
+updatedRowCount
+ |
+Number of rows updated in the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of the database
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowestSql
+ |
+slowestSql
+ |
+Slowest SQL statement of the database in the collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Exception (exception: exception statistics about SQL calls)
+ |
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of exceptions
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Exception message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+sql
+ |
+sql
+ |
+SQL statement that encounters an exception
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Version (version: PostgreSQL package version)
+ |
+version
+ |
+version
+ |
+Driver package version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+SQL monitoring (sql: APM counts call statistics by SQL.)
+ |
+sql
+ |
+sql
+ |
+Unique ID of the SQL statement, which is used for alarm configuration
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the SQL statement
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors that the SQL statement encounters
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the SQL statement is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+SQL error information
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the SQL statement
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+readRowCount
+ |
+readRowCount
+ |
+Number of read rows of the SQL statement
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of SQL statements that are being executed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+sqlString
+ |
+sqlString
+ |
+SQL statement
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updatedRowCount
+ |
+updatedRowCount
+ |
+Number of updated rows of the SQL statement
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Summary (total: summary about SQL statement call statistics)
+ |
+invokeCount
+ |
+invokeCount
+ |
+Total number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Total number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+readRowCount
+ |
+readRowCount
+ |
+Total number of read rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+updatedRowCount
+ |
+updatedRowCount
+ |
+Total number of updated rows
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
CSEProvider Cluster Monitoring
+This section describes the types, names, and meanings of CSEProvider cluster metrics collected by APM.
+
+
Table 1 CSEProvider collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Blocklist Configuration
+ |
+obj_array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+URLs in the blacklist will not be collected. There are four modes: "startwith", "endwith", "include", and "regex".
+ |
+
+Max. Status Code Length
+ |
+integer
+ |
+JAVA
+ |
+0
+ |
+2.0.0
+ |
+-
+ |
+The system parses the body content within the specified length and obtains the corresponding service status code.
+ |
+
+Key for Status Code Parsing
+ |
+array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+Key based on which the corresponding body content is to be obtained and reported as the service status code
+ |
+
+Normal Status Code
+ |
+array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+If the obtained status code is not within the range, the request is regarded as an error trace.
+ |
+
+Slow Request Threshold
+ |
+integer
+ |
+JAVA
+ |
+800
+ |
+2.0.0
+ |
+-
+ |
+Slow request threshold. If the threshold is crossed, a URL will be regarded as a slow URL. The system will automatically increase the sampling ratio for it.
+ |
+
+Slow URL Threshold
+ |
+obj_array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+Slow request threshold. If this threshold is crossed, the URL is defined as a slow URL. In that case, the system automatically increases the sampling ratio for it. There are four sampling policies: 1. Full sampling; 2. Percentage sampling; 3. Fixed-quantity sampling per minute; 4. Automatic sampling.
+ |
+
+Key for Header Value Interception
+ |
+array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+Key based on which header value content is to be intercepted
+ |
+
+
+
+
+
+
Table 2 CSEProvider cluster metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+CSEProvider cluster monitoring (cluster: APM counts call statistics based on the ID of the caller's cluster.)
+ |
+clusterId
+ |
+clusterId
+ |
+Cluster ID of the caller
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of times that the cluster fails to be called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of cluster calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for calling the cluster
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for calling the cluster
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+CSEProvider call details (detail: APM counts call statistics by URL.)
+ |
+qualifiedName
+ |
+qualifiedName
+ |
+Called URL of CSEProvider
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+method
+ |
+method
+ |
+HTTP method of the called CSEProvider URL
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the CSEProvider URL
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors occur when the CSEProvider URL is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the CSEProvider URL is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Call error details
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for calling the CSEProvider URL
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for calling the CSEProvider URL
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+CSEProvider summary (total: summary of all URL statistics)
+ |
+errorCount
+ |
+errorCount
+ |
+Total number of CSEProvider call errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Total number of CSEProvider calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of calling CSEProvider
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+Status code monitoring (statuscode: APM counts URL call statistics based on the status code returned.)
+ |
+code
+ |
+code
+ |
+HTTP status code
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times that the status code has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+url
+ |
+url
+ |
+Sample URL which returns the status code
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+
+
+
+
DubboProvider Monitoring
+This section describes the types, names, and meanings of DubboProvider metrics collected by APM.
+
+
Table 1 DubboProvider collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default Value
+ |
+Start Agent Version
+ |
+End Agent Version
+ |
+Description
+ |
+
|---|
+
+Slow Request Threshold
+ |
+integer
+ |
+JAVA
+ |
+800
+ |
+2.0.0
+ |
+-
+ |
+Threshold for determining that a request is slow (unit: ms).
+ |
+
+Sampling Ratio Configuration upon Slow Trace Detection
+ |
+string
+ |
+JAVA
+ |
+100,50,10,2
+ |
+2.0.0
+ |
+-
+ |
+Sampling ratio configuration to be applied when a slow request is detected (Example: For "100,50,10,2", the first three values respectively indicate the sampling ratio (%) under low, medium, and high CPU loads, and the last value indicates the minimum number of samples to be collected for each method.)
+ |
+
+Sampling Ratio Configuration upon Error Trace Detection
+ |
+string
+ |
+JAVA
+ |
+100,50,10,2
+ |
+2.0.0
+ |
+-
+ |
+Sampling ratio configuration to be applied when an error trace is detected (Example: For "100,50,10,2", the first three values respectively indicate the sampling ratio (%) under low, medium, and high CPU loads, and the last value indicates the minimum number of samples to be collected for each method.)
+ |
+
+Default Sampling Ratio Configuration
+ |
+string
+ |
+JAVA
+ |
+20,10,5,1
+ |
+2.0.0
+ |
+-
+ |
+Default sampling ratio configuration (Example: For "20,10,5,1", the first three values respectively indicate the sampling ratio (%) under low, medium, and high CPU loads, and the last value indicates the minimum number of samples to be collected for each method.)
+ |
+
+Excluded Method
+ |
+string
+ |
+JAVA
+ |
+[{"group":"mock"},{"service":"mock*"}]
+ |
+2.0.0
+ |
+-
+ |
+Method not to be traced.
+ |
+
+Method Match Rule
+ |
+string
+ |
+JAVA
+ |
+{{"group":"mock"}:{"percentage":10,"periodCount":1000,"sampleType":"4","slowRequestThreshold":800}}
+ |
+2.0.0
+ |
+-
+ |
+Only call information about the methods that match the rule is collected.
+ |
+
+Default Sampling Configuration
+ |
+string
+ |
+JAVA
+ |
+{"percentage":10,"periodCount":1000,"sampleType":"4","slowRequestThreshold":800}
+ |
+2.0.0
+ |
+-
+ |
+Default sampling configuration (If you customize Dubbo sampling, your configuration will overwrite the global configuration of APM.)
+ |
+
+Collect Call Details
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.0.0
+ |
+-
+ |
+Whether to collect call details such as parameters and return values (Default: not collect).
+ |
+
+Call Length
+ |
+integer
+ |
+JAVA
+ |
+1000
+ |
+2.0.0
+ |
+-
+ |
+Length of the call details to be collected (Default: 1,000 bytes).
+ |
+
+Collect Attachment
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.0.0
+ |
+-
+ |
+Whether to collect attachment (Default: not collect).
+ |
+
+Attachment Length
+ |
+integer
+ |
+JAVA
+ |
+1000
+ |
+2.0.0
+ |
+-
+ |
+Length of the attachment to be collected (Default: 1,000 bytes).
+ |
+
+Attachment Key
+ |
+array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+Key to be collected from Dubbo attachment.
+ |
+
+Filter Key
+ |
+array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+Sensitive information key to be filtered from Dubbo call parameters and returned information.
+ |
+
+
+
+
+
+
Table 2 Dubbo server metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Method call (invocation)
+ |
+serviceUniqueName
+ |
+serviceUniqueName
+ |
+Unique service identifier (group+interface+version)
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+method
+ |
+method
+ |
+Method
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+source
+ |
+source
+ |
+Call source
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+Slowest trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+Error trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of tasks that are being executed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+Host summary (cluster)
+ |
+cluster
+ |
+cluster
+ |
+Host
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of tasks that are being executed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+Return code summary (resultCode)
+ |
+code
+ |
+code
+ |
+Return code
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastMethod
+ |
+lastMethod
+ |
+Last exception type
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Summary (total)
+ |
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+Slowest trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+Error trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of tasks that are being executed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+Thread pool (threadPool)
+ |
+poolId
+ |
+poolId
+ |
+Unique ID of a thread pool
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+poolType
+ |
+poolType
+ |
+Custom Dubbo thread pool type, such as fixed, cached, or limited
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+activeCount
+ |
+activeCount
+ |
+Number of active threads
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+corePoolSize
+ |
+corePoolSize
+ |
+Number of core threads
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maximumPoolSize
+ |
+maximumPoolSize
+ |
+Maximum number of core threads
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+poolSize
+ |
+poolSize
+ |
+Size of the thread pool
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+queueSize
+ |
+queueSize
+ |
+Size of the waiting queue
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+taskCount
+ |
+taskCount
+ |
+Number of tasks
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Client version (version)
+ |
+version
+ |
+version
+ |
+Client version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+
+
+
+
FunctionGraph Monitoring
+This section describes the types, names, and meanings of FunctionGraph metrics collected by APM.
+
+
Table 1 Collection parameters for FunctionGraph monitoringParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Sampling Type
+ |
+radio
+ |
+JAVA
+ |
+4
+ |
+1.0.0
+ |
+-
+ |
+Sampling type. Options: full sampling, percentage sampling, fixed-quantity sampling per minute, and intelligent sampling (default).
+ |
+
+Sampling Ratio
+ |
+integer
+ |
+JAVA
+ |
+10
+ |
+1.0.0
+ |
+-
+ |
+Percentage of samples to the total number of trace data records
+ |
+
+Samples/Minute
+ |
+integer
+ |
+JAVA
+ |
+1000
+ |
+1.0.0
+ |
+-
+ |
+Number of trace data records collected every minute.
+ |
+
+Slow Request Threshold
+ |
+integer
+ |
+JAVA
+ |
+800
+ |
+2.0.0
+ |
+-
+ |
+Slow request threshold. If the threshold is crossed, the method is regarded as a slow method. In that case, the trace sampling ratio will be increased by default.
+ |
+
+Method Configuration
+ |
+obj_array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+Configure the slow request threshold and sampling ratio for each method separately. The following sampling policies can be set: percentage sampling, fixed-quantity sampling per minute, and automatic sampling.
+ |
+
+
+
+
+
+
Table 2 FunctionGraph metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Method monitoring (detail: APM counts URL call statistics by function method.)
+ |
+method
+ |
+method
+ |
+Request method
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the method
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of times that the method fails to be called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the method is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the method in a collection period
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of executions of the method at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of the method
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Cluster call (cluster: APM counts URL call statistics based on the cluster ID of the caller.)
+ |
+clusterId
+ |
+clusterId
+ |
+Cluster ID of the caller
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times the cluster is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for calling the cluster
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of times that the cluster fails to be called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
HttpClient Monitoring
+This section describes the types, names, and meanings of HttpClient metrics collected by APM.
+
+
Table 1 HttpClient collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+URL Normalization Configuration
+ |
+obj_array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+URL normalization configuration, based on which some RESTful URLs are normalized. There are four modes: "startwith", "endwith", "include", and "regex".
+ |
+
+
+
+
+
+
Table 2 HttpClient metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Exception (exception: HttpClient call exception statistics)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+Cluster metrics (hostInvocation: APM counts HttpClient URL call statistics by the called party's cluster.)
+ |
+envId
+ |
+envId
+ |
+Cluster ID of the called party
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+hostUri
+ |
+hostUri
+ |
+Called address
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors that occur when the cluster URL is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the cluster URL is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for calling the cluster URL
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for calling the cluster URL
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+responseCloseCount
+ |
+responseCloseCount
+ |
+Number of closed responses when the cluster URL is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+HttpClient version (info: HttpClient package version statistics)
+ |
+httpClientVersion
+ |
+httpClientVersion
+ |
+Version of the HttpClient package
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+httpCoreVersion
+ |
+httpCoreVersion
+ |
+Version of the HttpCore package
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+URL monitoring (invocation: APM counts URL call statistics by URL.)
+ |
+url
+ |
+url
+ |
+Called URL
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+method
+ |
+method
+ |
+HTTP method of the URL
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+client
+ |
+client
+ |
+HTTP client type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the URL
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of call errors of the URL
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+hostUri
+ |
+hostUri
+ |
+Called URL address
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the URL is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error details
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the called URL
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+responseCloseCount
+ |
+responseCloseCount
+ |
+Number of closed responses when the URL is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of the called URL
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+envId
+ |
+envId
+ |
+Cluster ID corresponding to the called URL
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+HttpClient summary (total: summary about HttpClient call statistics)
+ |
+errorCount
+ |
+errorCount
+ |
+Total number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Total number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+responseCloseCount
+ |
+responseCloseCount
+ |
+Total number of responses that are closed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+Status code statistics (code: HttpClient call exception statistics)
+ |
+code
+ |
+code
+ |
+Status code
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+url
+ |
+url
+ |
+URL that returns the status code
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times that the status code has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
URL Monitoring
+This section describes the types, names, and meanings of URL metrics collected by APM.
+
+
Table 1 Collection parameters for URL monitoringParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Key for Header Value Interception
+ |
+array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+Key based on which header value content is to be intercepted
+ |
+
+Key for Parameter Value Interception
+ |
+array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+Key based on which parameter value content is to be intercepted
+ |
+
+Key for Cookie Value Interception
+ |
+array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+Key based on which cookie value content is to be intercepted
+ |
+
+URL Collection Configuration
+ |
+obj_array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+URL collection configuration, based on which RESTful URLs are normalized. There are four modes: "startwith", "endwith", "include", and "regex".
+ |
+
+Blocklist Configuration
+ |
+obj_array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+URLs that match the specified rule will not be collected. There are four modes: "startwith", "endwith", "include", and "regex".
+ |
+
+Service Code Length
+ |
+integer
+ |
+JAVA
+ |
+0
+ |
+2.0.0
+ |
+-
+ |
+Maximum length of the body content to be collected for service code parsing
+ |
+
+Key for Service Code Interception
+ |
+array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+Specify a key. Then the system parses the key in the body (JSON) and obtains the service status code based on the key.
+ |
+
+Normal Service Code
+ |
+array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+Normal service code range. If a service code is not within this range, the corresponding trace is regarded as an error trace.
+ |
+
+Slow Request Threshold
+ |
+integer
+ |
+JAVA
+ |
+800
+ |
+2.0.0
+ |
+-
+ |
+Slow request threshold. If the threshold is crossed, the URL is regarded as a slow URL. In that case, the trace sampling ratio will be increased by default.
+ |
+
+URL Configuration
+ |
+obj_array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+Configure the slow request threshold and sampling ratio for each URL separately. The following sampling policies can be set: percentage sampling, fixed-quantity sampling per minute, and automatic sampling.
+ |
+
+Error Code
+ |
+radio
+ |
+JAVA
+ |
+500
+ |
+2.0.0
+ |
+-
+ |
+Status codes that are counted as errors
+ |
+
+Auto URL Normalization
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.3.11
+ |
+-
+ |
+Whether the URL will be automatically normalized
+ |
+
+
+
+
+
+
Table 2 URL metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Summary (total: URL call statistics summary)
+ |
+errorCount
+ |
+errorCount
+ |
+Total number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Total number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+satisfiedCount
+ |
+satisfiedCount
+ |
+Number of satisfied requests
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+toleratingCount
+ |
+toleratingCount
+ |
+Number of tolerable requests
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Status code (statuscode: APM counts URL call statistics based on the status code returned.)
+ |
+code
+ |
+code
+ |
+Status code
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times that the status code has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+url
+ |
+url
+ |
+Sample URL which returns the status code in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+URL monitoring (url: APM counts URL call statistics by URL.)
+ |
+url
+ |
+URL
+ |
+Request URL
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+method
+ |
+method
+ |
+Request HTTP method
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the URL
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+URL call errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the URL is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error details
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the URL in a collection period
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+maxTimeNativeUrl
+ |
+maxTimeNativeUrl
+ |
+Slowest URL in the collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of tasks that are being executed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+isRoot
+ |
+isRoot
+ |
+Whether the span is a root span
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+satisfiedCount
+ |
+satisfiedCount
+ |
+Number of satisfied requests
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+toleratingCount
+ |
+toleratingCount
+ |
+Number of tolerable requests
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Cluster call (user: APM counts URL call statistics based on the cluster ID of the caller.)
+ |
+clusterId
+ |
+clusterId
+ |
+Cluster ID of the caller
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times the cluster is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+total1xxCount
+ |
+total1xxCount
+ |
+Number of times that a 1xx status code was returned
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+total2xxCount
+ |
+total2xxCount
+ |
+Number of times that a 2xx status code was returned
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+total3xxCount
+ |
+total3xxCount
+ |
+Number of times that a 3xx status code was returned
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+total4xxCount
+ |
+total4xxCount
+ |
+Number of times that a 4xx status code was returned
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+total5xxCount
+ |
+total5xxCount
+ |
+Number of times that a 5xx status code was returned
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for calling the cluster
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of times that the cluster fails to be called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
ApacheHttpAsyncClient Connection Pool
+This section describes the types, names, and meanings of ApacheHttpAsyncClient connection pool metrics collected by APM.
+
+
Table 1 ApacheHttpAsyncClient collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Threshold (ms) for Reporting Connection Trace
+ |
+integer
+ |
+JAVA
+ |
+1
+ |
+2.1.6
+ |
+-
+ |
+Threshold (ms) for reporting connection traces
+ |
+
+Obtain Pool Info or Not
+ |
+radio
+ |
+JAVA
+ |
+1
+ |
+2.1.6
+ |
+-
+ |
+Whether to obtain pool information when getting connections
+ |
+
+
+
+
+
+
Table 2 ApacheHttpAsyncClient connection pool metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Connection pool (connectionPool: statistics about ApacheHttpAsyncClient connections in different states)
+ |
+poolId
+ |
+poolId
+ |
+ApacheHttpAsyncClient connection pool ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+available
+ |
+available
+ |
+Number of idle connections in the connection pool
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+leased
+ |
+leased
+ |
+Number of connections occupied
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+max
+ |
+max
+ |
+Maximum number of connections in the connection pool
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+pending
+ |
+pending
+ |
+Number of pending connections in the connection pool
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Connection pool route (collectionPoolRoute: APM counts connection statistics by pool route.)
+ |
+poolId
+ |
+poolId
+ |
+ApacheHttpAsyncClient connection pool ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+route
+ |
+route
+ |
+Routing information of the connection pool
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+available
+ |
+available
+ |
+Number of idle connections in the connection pool
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+leased
+ |
+leased
+ |
+Number of connections occupied
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+max
+ |
+max
+ |
+Maximum number of connections in the connection pool
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+pending
+ |
+pending
+ |
+Number of pending connections in the connection pool
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Connection details (connection)
+ |
+route
+ |
+route
+ |
+Route
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+
+
+
+
ApacheHttpClient Connection Pool
+This section describes the types, names, and meanings of ApacheHttpClient connection pool metrics collected by APM.
+
+
Table 1 ApacheHttpClient connection pool metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Connection pool (connectionPool: statistics about ApacheHttpclient connections in different states)
+ |
+poolId
+ |
+poolId
+ |
+ApacheHttpclient connection pool ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+available
+ |
+available
+ |
+Number of idle connections in the connection pool
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+leased
+ |
+leased
+ |
+Number of connections occupied
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+max
+ |
+max
+ |
+Maximum number of connections in the connection pool
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+pending
+ |
+pending
+ |
+Number of pending connections in the connection pool
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Connection pool route (collectionPoolRoute: APM counts connection statistics by pool route.)
+ |
+poolId
+ |
+poolId
+ |
+ApacheHttpClient connection pool ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+route
+ |
+route
+ |
+Routing information of the connection pool
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+available
+ |
+available
+ |
+Number of idle connections in the connection pool
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+leased
+ |
+leased
+ |
+Number of connections occupied
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+max
+ |
+max
+ |
+Maximum number of connections in the connection pool
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+pending
+ |
+pending
+ |
+Number of pending connections in the connection pool
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
CSEConsumer Cluster Monitoring
+This section describes the types, names, and meanings of CSEConsumer cluster metrics collected by APM.
+
+
Table 1 CSEConsumer cluster metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+CSEConsumer cluster monitoring (cluster: APM counts call statistics based on the ID of the cluster called by CSEConsumer.)
+ |
+clusterId
+ |
+clusterId
+ |
+ID of the cluster where the called service is located
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times the cluster is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for calling the cluster
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for calling the cluster
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+CSEConsumer call details (detail: APM counts the call statistics based on the called URL.)
+ |
+qualifiedName
+ |
+qualifiedName
+ |
+CSEConsumer call URL
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+method
+ |
+method
+ |
+HTTP method for CSEConsumer calling
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of concurrent CSEConsumer calls
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of CSEConsumer call errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the error trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of CSEConsumer calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Call error details
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for CSEConsumer calling
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for CSEConsumer calling
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+CSEConsumer summary (total: summary of CSEConsumer call statistics)
+ |
+errorCount
+ |
+errorCount
+ |
+Total number of CSEConsumer call errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Total number of CSEConsumer calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for CSEConsumer calling
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
DubboConsumer Monitoring
+This section describes the types, names, and meanings of DubboConsumer metrics collected by APM.
+
+
Table 1 DubboConsumer metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Method call (invocation)
+ |
+serviceUniqueName
+ |
+serviceUniqueName
+ |
+Unique service identifier (group+interface+version)
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+method
+ |
+method
+ |
+Method
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+Slowest trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+Error trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of tasks that are being executed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+source
+ |
+source
+ |
+Call source
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+Host summary (cluster)
+ |
+cluster
+ |
+cluster
+ |
+Host
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of tasks that are being executed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+Return code summary (resultCode)
+ |
+code
+ |
+code
+ |
+Return code
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastMethod
+ |
+lastMethod
+ |
+Last exception type
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Summary (total)
+ |
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+Slowest trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+Error trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of tasks that are being executed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+Thread pool (threadPool)
+ |
+poolId
+ |
+poolId
+ |
+Unique ID of a thread pool
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+poolType
+ |
+poolType
+ |
+Custom Dubbo thread pool type, such as fixed, cached, or limited
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+activeCount
+ |
+activeCount
+ |
+Number of active threads
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+corePoolSize
+ |
+corePoolSize
+ |
+Number of core threads
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maximumPoolSize
+ |
+maximumPoolSize
+ |
+Maximum number of core threads
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+poolSize
+ |
+poolSize
+ |
+Size of the thread pool
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+queueSize
+ |
+queueSize
+ |
+Size of the waiting queue
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+taskCount
+ |
+taskCount
+ |
+Number of tasks
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Client version (version)
+ |
+version
+ |
+version
+ |
+Version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+
+
+
+
Redis Method Call
+This section describes the types, names, and meanings of Redis method call metrics collected by APM.
+
+
Table 1 Redis method call collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Parameter Parsing
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.0.0
+ |
+-
+ |
+Whether to parse Redis parameters and return values
+ |
+
+Length
+ |
+integer
+ |
+JAVA
+ |
+1000
+ |
+2.0.0
+ |
+-
+ |
+Maximum length of parameters to be parsed
+ |
+
+Port Differentiation
+ |
+radio
+ |
+JAVA
+ |
+false
+ |
+2.0.0
+ |
+-
+ |
+Whether to distinguish Redis ports
+ |
+
+
+
+
+
+
Table 2 Call metricsName
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Call details (detail)
+ |
+host
+ |
+host
+ |
+Host
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+action
+ |
+action
+ |
+Method
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+Slowest trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+Error trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–5 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 5–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 10–50 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 50–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 100–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 1s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+hits
+ |
+hits
+ |
+Hits of methods including GET, HGET, and EXPIRE
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of tasks that are being executed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+blobCount
+ |
+blobCount
+ |
+Number of calls with more than 1000 bytes returned
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+getInvokeCount
+ |
+getInvokeCount
+ |
+Number of times that GET methods including GET, HGET, and EXPIRE have been called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+traffic
+ |
+traffic
+ |
+Call traffic
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Host summary (host)
+ |
+host
+ |
+host
+ |
+Host
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+Slowest trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+Error trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–5 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 5–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 10–50 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 50–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 100–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 1s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+hits
+ |
+hits
+ |
+Hits of methods including GET, HGET, and EXPIRE
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of tasks that are being executed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+blobCount
+ |
+blobCount
+ |
+Number of calls with more than 1000 bytes returned
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+getInvokeCount
+ |
+getInvokeCount
+ |
+Number of times that GET methods including GET, HGET, and EXPIRE have been called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+traffic
+ |
+traffic
+ |
+Call traffic
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Method summary (action)
+ |
+action
+ |
+action
+ |
+Method
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+lastError
+ |
+lastError
+ |
+Last exception type
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+Slowest trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+Error trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–5 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 5–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 10–50 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 50–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 100–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 1s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+hits
+ |
+hits
+ |
+Hits of methods including GET, HGET, and EXPIRE
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Ongoing executions
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+blobCount
+ |
+blobCount
+ |
+Number of calls with more than 1000 bytes returned
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+getInvokeCount
+ |
+getInvokeCount
+ |
+Number of times that GET methods including GET, HGET, and EXPIRE have been called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+traffic
+ |
+traffic
+ |
+Traffic
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Summary (total)
+ |
+lastError
+ |
+lastError
+ |
+Last exception type
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+Slowest trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+Error trace ID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–5 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 5–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 10–50 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 50–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 100–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 1s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+hits
+ |
+hits
+ |
+Hits of methods including GET, HGET, and EXPIRE
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of tasks that are being executed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+blobCount
+ |
+blobCount
+ |
+Number of calls with more than 1000 bytes returned
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+getInvokeCount
+ |
+getInvokeCount
+ |
+Number of times that GET methods including GET, HGET, and EXPIRE have been called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+traffic
+ |
+traffic
+ |
+Traffic
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
Jedis Monitoring
+This section describes the types, names, and meanings of Jedis metrics collected by APM.
+
+
Table 1 Jedis metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Connection pool (jedisPool)
+ |
+pool
+ |
+pool
+ |
+Unique identifier of a connection pool (host name+port number)
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+maxTotal
+ |
+maxTotal
+ |
+Maximum number of connections
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+maxIdle
+ |
+maxIdle
+ |
+Maximum number of idle connections
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+minIdle
+ |
+minIdle
+ |
+Minimum number of idle connections
+ |
+-
+ |
+INT
+ |
+MIN
+ |
+
+numActive
+ |
+numActive
+ |
+Number of active connections
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+numIdle
+ |
+numIdle
+ |
+Number of idle connections
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+numWaiters
+ |
+numWaiters
+ |
+Number of waiting connections
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+createdCount
+ |
+createdCount
+ |
+Number of connections that have been created
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+destroyedCount
+ |
+destroyedCount
+ |
+Number of connections that have been destroyed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+borrowedCount
+ |
+borrowedCount
+ |
+Number of borrowed connections
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxWaitMillis
+ |
+maxWaitMillis
+ |
+Maximum waiting time (ms)
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+maxBorrowWaitTimeMillis
+ |
+maxBorrowWaitTimeMillis
+ |
+Maximum waiting time of borrowed connections (ms)
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+meanActiveTimeMillis
+ |
+meanActiveTimeMillis
+ |
+Average activation time of connections (ms)
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+meanBorrowWaitTimeMillis
+ |
+meanBorrowWaitTimeMillis
+ |
+Average waiting time of borrowed connections
+ |
+ms
+ |
+INT
+ |
+SUM
+ |
+
+Active/standby switchover (switch)
+ |
+from
+ |
+from
+ |
+Source host
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+to
+ |
+to
+ |
+Target host
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+switchTimes
+ |
+switchTimes
+ |
+Number of switchovers
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Client information (clientInfo)
+ |
+version
+ |
+version
+ |
+Client version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+mode
+ |
+mode
+ |
+Redis mode (standalone or cluster)
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+nodes
+ |
+nodes
+ |
+Number of master Redis nodes
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+
+
+
+
Lettuce Client
+This section describes the types, names, and meanings of Lettuce client metrics collected by APM.
+
+
Table 1 Lettuce client metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Client information (clientInfo)
+ |
+version
+ |
+version
+ |
+Client version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+mode
+ |
+mode
+ |
+Redis mode (standalone or cluster)
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+nodes
+ |
+nodes
+ |
+Number of master Redis nodes
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Active/standby switchover (switch)
+ |
+from
+ |
+from
+ |
+Source host
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+to
+ |
+to
+ |
+Target host
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+switchTimes
+ |
+switchTimes
+ |
+Number of switchovers
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
KafkaConsumer Monitoring
+This section describes the types, names, and meanings of KafkaConsumer metrics collected by APM.
+
+
Table 1 KafkaConsumer monitoring collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Kafka Slow Request Threshold
+ |
+integer
+ |
+JAVA
+ |
+800
+ |
+2.1.14
+ |
+-
+ |
+The sampling ratio will increase if the slow request threshold is crossed.
+ |
+
+Kafka Consumption Method Configuration
+ |
+obj_array
+ |
+JAVA
+ |
+-
+ |
+2.1.14
+ |
+-
+ |
+Kafka consumption method configuration
+ |
+
+
+
+
+
+
Table 2 KafkaConsumer metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Topic (topic: Kafka topic monitoring data)
+ |
+id
+ |
+id
+ |
+Client ID and IP address
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+topic
+ |
+topic
+ |
+Kafka topic name
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+bytesConsumedRate
+ |
+bytesConsumedRate
+ |
+Number of bytes consumed per second
+ |
+Byte
+ |
+INT
+ |
+AVG
+ |
+
+fetchSizeAvg
+ |
+fetchSizeAvg
+ |
+Average number of bytes fetched for a request
+ |
+Byte
+ |
+INT
+ |
+AVG
+ |
+
+fetchSizeMax
+ |
+fetchSizeMax
+ |
+Maximum number of bytes fetched for a request
+ |
+Byte
+ |
+INT
+ |
+MAX
+ |
+
+recordsConsumedRate
+ |
+recordsConsumedRate
+ |
+Number of messages consumed per second
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+recordsPerRequestAvg
+ |
+recordsPerRequestAvg
+ |
+Average number of messages of a single request
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+seqIds
+ |
+seqIds
+ |
+Sequence number generated by the producer
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+recordConsumedTotal
+ |
+recordConsumedTotal
+ |
+Total number of consumption times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+bytesConsumedTotal
+ |
+bytesConsumedTotal
+ |
+Total number of bytes that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Fetch monitoring (fetch: Kafka fetch monitoring data)
+ |
+id
+ |
+id
+ |
+Client ID and IP address
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+bytesConsumedRate
+ |
+bytesConsumedRate
+ |
+Number of bytes consumed per second
+ |
+Byte
+ |
+INT
+ |
+AVG
+ |
+
+fetchLatencyAvg
+ |
+fetchLatencyAvg
+ |
+Average request latency
+ |
+ms
+ |
+INT
+ |
+AVG
+ |
+
+fetchLatencyMax
+ |
+fetchLatencyMax
+ |
+Maximum request latency
+ |
+ms
+ |
+INT
+ |
+MAX
+ |
+
+fetchRate
+ |
+fetchRate
+ |
+Number of requests per second
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+fetchSizeAvg
+ |
+fetchSizeAvg
+ |
+Average number of bytes fetched for a request
+ |
+Byte
+ |
+INT
+ |
+AVG
+ |
+
+fetchSizeMax
+ |
+fetchSizeMax
+ |
+Maximum number of bytes fetched for a request
+ |
+Byte
+ |
+INT
+ |
+MAX
+ |
+
+recordsConsumedRate
+ |
+recordsConsumedRate
+ |
+Number of messages consumed per second
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+recordsLagMax
+ |
+recordsLagMax
+ |
+Maximum number of accumulated messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+recordsPerRequestAvg
+ |
+recordsPerRequestAvg
+ |
+Average number of messages of a single request
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+seqIds
+ |
+seqIds
+ |
+Sequence number generated by the producer
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+recordConsumedTotal
+ |
+recordConsumedTotal
+ |
+Total number of consumption times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+bytesConsumedTotal
+ |
+bytesConsumedTotal
+ |
+Total number of bytes that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Partition (partition: Kafka partition data)
+ |
+id
+ |
+id
+ |
+Client ID and IP address
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+partition
+ |
+partition
+ |
+Kafka partition name
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+recordsLag
+ |
+recordsLag
+ |
+Number of accumulated messages
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+recordsLagAvg
+ |
+recordsLagAvg
+ |
+Average number of accumulated messages
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+recordsLagMax
+ |
+recordsLagMax
+ |
+Maximum number of accumulated messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+seqIds
+ |
+seqIds
+ |
+Sequence number generated by the producer
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Kafka consumption method monitoring (consumer)
+ |
+method
+ |
+method
+ |
+Consumption method
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error details
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time in a collection period
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with more than 10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+KafkaConsumer summary (total)
+ |
+recordConsumedTotal
+ |
+recordConsumedTotal
+ |
+Total number of consumption times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+bytesConsumedTotal
+ |
+bytesConsumedTotal
+ |
+Total number of bytes that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+recordsLag
+ |
+recordsLag
+ |
+Total number of messages that have been accumulated
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+Exception (exception: exception statistics about Kafka consumption)
+ |
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+exceptionType
+ |
+exceptionType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of exceptions
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Exception message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+
+
+
+
KafkaProducer Monitoring
+This section describes the types, names, and meanings of KafkaProducer metrics collected by APM.
+
+
Table 1 KafkaProducer metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Topic (topic: Kafka topic monitoring data)
+ |
+id
+ |
+id
+ |
+Client ID and IP address
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+topic
+ |
+topic
+ |
+Kafka topic name
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+byteRate
+ |
+byteRate
+ |
+Number of bytes sent per second
+ |
+Byte
+ |
+INT
+ |
+AVG
+ |
+
+recordErrorRate
+ |
+recordErrorRate
+ |
+Number of errors per second
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+recordRetryRate
+ |
+recordRetryRate
+ |
+Number of retries per second
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+recordSendRate
+ |
+recordSendRate
+ |
+Number of messages sent per second
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+seqIds
+ |
+seqIds
+ |
+Sequence number generated by the producer
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+recordSendTotal
+ |
+recordSendTotal
+ |
+Total number of send times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+byteTotal
+ |
+byteTotal
+ |
+Total number of bytes that have been sent
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+KafkaProducer summary (total)
+ |
+recordSendTotal
+ |
+recordSendTotal
+ |
+Total number of send times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+byteTotal
+ |
+byteTotal
+ |
+Total number of bytes that have been sent
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Exception (exception: exception statistics about Kafka byte sending)
+ |
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+exceptionType
+ |
+exceptionType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of exceptions
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Exception message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Send methods (doSendMethod)
+ |
+topic
+ |
+topic
+ |
+topic
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with more than 10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
RabbitMqCommon Monitoring
+This section describes the types, names, and meanings of RabbitMqCommon metrics collected by APM.
+
+
Table 1 RabbitMqCommon metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Exception (exception: exception statistics of RabbitMqCommon calls)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Connection monitoring (connectionCount: APM counts connection statistics.)
+ |
+connectionCount
+ |
+connectionCount
+ |
+Current number of connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+channelCount
+ |
+channelCount
+ |
+Current number of channels
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+connectionCreated
+ |
+connectionCreated
+ |
+Number of connections that have been created
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+connectionClosed
+ |
+connectionClosed
+ |
+Number of connections that have been destroyed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+channelCreated
+ |
+channelCreated
+ |
+Number of channels that have been created
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+channelClosed
+ |
+channelClosed
+ |
+Number of channels that have been destroyed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Total monitoring (total: APM counts connection statistics by connection.)
+ |
+connectionCount
+ |
+connectionCount
+ |
+Current number of connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+channelCount
+ |
+channelCount
+ |
+Current number of channels
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+connectionCreated
+ |
+connectionCreated
+ |
+Number of connections that have been created
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+connectionClosed
+ |
+connectionClosed
+ |
+Number of connections that have been destroyed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+channelCreated
+ |
+channelCreated
+ |
+Number of channels that have been created
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+channelClosed
+ |
+channelClosed
+ |
+Number of channels that have been destroyed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+RabbitMQ version (version)
+ |
+version
+ |
+version
+ |
+Version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+
+
+
+
RabbitMqConsumer Monitoring
+This section describes the types, names, and meanings of RabbitMqConsumer metrics collected by APM.
+
+
Table 1 Call metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Exception (exception: exception statistics of RabbitMqConsumer calls)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Push-mode consumption monitoring (pushConsume: APM counts statistics about push-mode message consumption.)
+ |
+pushConsumeIdentifier
+ |
+pushConsumeIdentifier
+ |
+Push-mode consumption identifier
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent consumption
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message consumption errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of consumption call times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedMsgCount
+ |
+consumedMsgCount
+ |
+Number of messages that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedBytes
+ |
+consumedBytes
+ |
+Number of bytes that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxSingleMsgBytes
+ |
+maxSingleMsgBytes
+ |
+Maximum number of bytes consumed each time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+manualAckCount
+ |
+manualAckCount
+ |
+Number of ACK messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+rejectCount
+ |
+rejectCount
+ |
+Number of rejected messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+requeueCount
+ |
+requeueCount
+ |
+Number of re-queued messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message consumption
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for consuming messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being consumed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for consuming messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+unackedMsgCount
+ |
+unackedMsgCount
+ |
+Number of unacknowledged messages in the channel
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+Connection monitoring (connectionConsume: APM counts message consumption statistics by connection.)
+ |
+connection
+ |
+connection
+ |
+Consumer connection information
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+connectionCount
+ |
+connectionCount
+ |
+Current number of connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+channelCount
+ |
+channelCount
+ |
+Current number of channels
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+connectionCreated
+ |
+connectionCreated
+ |
+Number of connections that have been created
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+connectionClosed
+ |
+connectionClosed
+ |
+Number of connections that have been destroyed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+channelCreated
+ |
+channelCreated
+ |
+Number of channels that have been created
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+channelClosed
+ |
+channelClosed
+ |
+Number of channels that have been destroyed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent consumption
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message consumption errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of consumption call times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedMsgCount
+ |
+consumedMsgCount
+ |
+Number of messages that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedBytes
+ |
+consumedBytes
+ |
+Number of bytes that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxSingleMsgBytes
+ |
+maxSingleMsgBytes
+ |
+Maximum number of bytes consumed each time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+manualAckCount
+ |
+manualAckCount
+ |
+Number of ACK messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+rejectCount
+ |
+rejectCount
+ |
+Number of rejected messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+requeueCount
+ |
+requeueCount
+ |
+Number of re-queued messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message consumption
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for consuming messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being consumed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for consuming messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+unackedMsgCount
+ |
+unackedMsgCount
+ |
+Number of messages that have not been acknowledged in a connection
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+Total monitoring (total: APM counts message consumption statistics by client.)
+ |
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent consumption
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message consumption errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of consumption call times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedMsgCount
+ |
+consumedMsgCount
+ |
+Number of messages that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedBytes
+ |
+consumedBytes
+ |
+Number of bytes that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxSingleMsgBytes
+ |
+maxSingleMsgBytes
+ |
+Maximum number of bytes consumed each time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+manualAckCount
+ |
+manualAckCount
+ |
+Number of ACK messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+rejectCount
+ |
+rejectCount
+ |
+Number of rejected messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+requeueCount
+ |
+requeueCount
+ |
+Number of re-queued messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message consumption
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for consuming messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being consumed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for consuming messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+unackedMsgCount
+ |
+unackedMsgCount
+ |
+Number of unacknowledged messages on the client
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+
+
+
+
RabbitMqProducer Monitoring
+This section describes the types, names, and meanings of RabbitMqProducer metrics collected by APM.
+
+
Table 1 RabbitMqProducer metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Exception (exception: exception statistics of RabbitMqProducer calls)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Exchange monitoring (exchangePublish: APM counts message push statistics by exchange.)
+ |
+connection
+ |
+connection
+ |
+Producer connection information
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+exchange
+ |
+exchange
+ |
+Exchange name
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent push
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message push errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of message push calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedMsgCount
+ |
+publishedMsgCount
+ |
+Number of push messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedBytes
+ |
+publishedBytes
+ |
+Number of push bytes
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxSingleMsgBytes
+ |
+maxSingleMsgBytes
+ |
+Maximum number of bytes in each push
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message pushing
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for pushing messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being pushed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for pushing messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Connection monitoring (connectionPublish: APM counts message push statistics by connection.)
+ |
+connection
+ |
+connection
+ |
+Producer connection information
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+connectionCount
+ |
+connectionCount
+ |
+Current number of connections
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+channelCount
+ |
+channelCount
+ |
+Current number of channels
+ |
+-
+ |
+INT
+ |
+LAST
+ |
+
+connectionCreated
+ |
+connectionCreated
+ |
+Number of connections that have been created
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+connectionClosed
+ |
+connectionClosed
+ |
+Number of connections that have been destroyed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+channelCreated
+ |
+channelCreated
+ |
+Number of channels that have been created
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+channelClosed
+ |
+channelClosed
+ |
+Number of channels that have been destroyed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent push
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message push errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of message push calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedMsgCount
+ |
+publishedMsgCount
+ |
+Number of push messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedBytes
+ |
+publishedBytes
+ |
+Number of push bytes
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxSingleMsgBytes
+ |
+maxSingleMsgBytes
+ |
+Maximum number of bytes in each push
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message pushing
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for pushing messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being pushed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for pushing messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Total monitoring (total: APM counts message push statistics by client.)
+ |
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent push
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message push errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of message push calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedMsgCount
+ |
+publishedMsgCount
+ |
+Number of push messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedBytes
+ |
+publishedBytes
+ |
+Number of push bytes
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxSingleMsgBytes
+ |
+maxSingleMsgBytes
+ |
+Maximum number of bytes in each push
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message pushing
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for pushing messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being pushed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for pushing messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
RocketMqConsumer Monitoring
+This section describes the types, names, and meanings of RocketMqConsumer metrics collected by APM.
+
+
Table 1 RocketMqConsumer metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Exception (exception: exception statistics of RocketMqConsumer calls)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Consumption pool monitoring (consumeServicePool)
+ |
+clientId
+ |
+clientId
+ |
+Client instance ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+group
+ |
+group
+ |
+Consumer group
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+pid
+ |
+pid
+ |
+PID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+currentConsumeRequestQueueSize
+ |
+currentConsumeRequestQueueSize
+ |
+Current size of the consumption request queue
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+maxConsumeRequestQueueSize
+ |
+maxConsumeRequestQueueSize
+ |
+Maximum size of the consumption request queue
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+currentConsumingThreadCount
+ |
+currentConsumingThreadCount
+ |
+Current number of consumption threads
+ |
+-
+ |
+INT
+ |
+AVG
+ |
+
+maxConsumingPoolSize
+ |
+maxConsumingPoolSize
+ |
+Maximum number of consumption threads
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+Message listener monitoring (consumeListener: APM counts message consumption statistics by MessageListener.)
+ |
+consumeListener
+ |
+consumeListener
+ |
+Registered message listener, which is the callback function for message consumption
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent consumption
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message consumption errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of consumption call times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedMsgCount
+ |
+consumedMsgCount
+ |
+Number of messages that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedBytes
+ |
+consumedBytes
+ |
+Number of bytes that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+reconsumeTimes
+ |
+reconsumeTimes
+ |
+Number of message re-consumption times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message consumption
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for consuming messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being consumed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for consuming messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Client ID monitoring (clientIdConsume: APM counts message consumption statistics by client ID.)
+ |
+clientId
+ |
+clientId
+ |
+Client instance ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+group
+ |
+group
+ |
+Consumer group
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+pid
+ |
+pid
+ |
+PID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent consumption
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message consumption errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of consumption call times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedMsgCount
+ |
+consumedMsgCount
+ |
+Number of messages that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedBytes
+ |
+consumedBytes
+ |
+Number of bytes that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+reconsumeTimes
+ |
+reconsumeTimes
+ |
+Number of message re-consumption times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message consumption
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for consuming messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being consumed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for consuming messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Topic monitoring (topicConsume: APM counts message consumption statistics by topic.)
+ |
+clientId
+ |
+clientId
+ |
+Client instance ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+group
+ |
+group
+ |
+Consumer group
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+pid
+ |
+pid
+ |
+PID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+topic
+ |
+topic
+ |
+Topic for message consumption
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent consumption
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message consumption errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of consumption call times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedMsgCount
+ |
+consumedMsgCount
+ |
+Number of messages that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedBytes
+ |
+consumedBytes
+ |
+Number of bytes that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+reconsumeTimes
+ |
+reconsumeTimes
+ |
+Number of message re-consumption times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message consumption
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for consuming messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being consumed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for consuming messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Queue monitoring (queueConsume: APM counts message consumption statistics by queue.)
+ |
+clientId
+ |
+clientId
+ |
+Client instance ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+group
+ |
+group
+ |
+Consumer group
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+queue
+ |
+queue
+ |
+Message queue ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+pid
+ |
+pid
+ |
+PID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent consumption
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message consumption errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of consumption call times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedMsgCount
+ |
+consumedMsgCount
+ |
+Number of messages that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedBytes
+ |
+consumedBytes
+ |
+Number of bytes that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+reconsumeTimes
+ |
+reconsumeTimes
+ |
+Number of message re-consumption times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message consumption
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for consuming messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being pulled at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for pulling messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Client ID monitoring (clientIdPull: APM counts message pull statistics by client ID.)
+ |
+clientId
+ |
+clientId
+ |
+Client instance ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+group
+ |
+group
+ |
+Consumer group
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+pid
+ |
+pid
+ |
+PID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent pulling
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message pull errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of pull calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+pulledMsgCount
+ |
+pulledMsgCount
+ |
+Number of messages that have been pulled
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+pulledBytes
+ |
+pulledBytes
+ |
+Number of bytes that have been pulled
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message pulling
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for pulling messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being pulled at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for pulling messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Topic monitoring (topicPull: APM counts message pull statistics by topic.)
+ |
+clientId
+ |
+clientId
+ |
+Client instance ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+group
+ |
+group
+ |
+Consumer group
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+topic
+ |
+topic
+ |
+Topic for pulling messages
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+pid
+ |
+pid
+ |
+PID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent pulling
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message pull errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of pull calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+pulledMsgCount
+ |
+pulledMsgCount
+ |
+Number of messages that have been pulled
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+pulledBytes
+ |
+pulledBytes
+ |
+Number of bytes that have been pulled
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message pulling
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for pulling messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being pulled at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for pulling messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Queue monitoring (queuePull: APM counts message pull statistics by queue.)
+ |
+clientId
+ |
+clientId
+ |
+Client instance ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+group
+ |
+group
+ |
+Consumer group
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+queue
+ |
+queue
+ |
+Message queue ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+pid
+ |
+pid
+ |
+PID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent pulling
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message pull errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of pull calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+pulledMsgCount
+ |
+pulledMsgCount
+ |
+Number of messages that have been pulled
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+pulledBytes
+ |
+pulledBytes
+ |
+Number of bytes that have been pulled
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message pulling
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for pulling messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being pulled at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for pulling messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Total monitoring (total: APM counts message consumption statistics by client.)
+ |
+consumeErrorCount
+ |
+consumeErrorCount
+ |
+Number of message consumption errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumeInvokeCount
+ |
+consumeInvokeCount
+ |
+Number of consumption call times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedMsgCount
+ |
+consumedMsgCount
+ |
+Number of messages that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumedBytes
+ |
+consumedBytes
+ |
+Number of bytes that have been consumed
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+consumeTotalTime
+ |
+consumeTotalTime
+ |
+Total response time for consuming messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+reconsumeTimes
+ |
+reconsumeTimes
+ |
+Number of message re-consumption times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+pullErrorCount
+ |
+pullErrorCount
+ |
+Number of message pull errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+pullInvokeCount
+ |
+pullInvokeCount
+ |
+Number of pull calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+pulledMsgCount
+ |
+pulledMsgCount
+ |
+Number of messages that have been pulled
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+pulledBytes
+ |
+pulledBytes
+ |
+Number of bytes that have been pulled
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+pullTotalTime
+ |
+pullTotalTime
+ |
+Total response time for pulling messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
RocketMqProducer Monitoring
+This section describes the types, names, and meanings of RocketMqProducer metrics collected by APM.
+
+
Table 1 RocketMqProducer metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Exception (exception: exception statistics of RabbitMqProducer calls)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+Client ID monitoring (clientIdPublish: APM counts message push statistics by client ID.)
+ |
+clientId
+ |
+clientId
+ |
+Client instance ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+group
+ |
+group
+ |
+Producer group
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+pid
+ |
+pid
+ |
+PID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent push
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message push errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of message push calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedMsgCount
+ |
+publishedMsgCount
+ |
+Number of push messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedBytes
+ |
+publishedBytes
+ |
+Number of push bytes
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message pushing
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for pushing messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being pushed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for pushing messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Topic monitoring (topicPublish: APM counts message push statistics by topic.)
+ |
+clientId
+ |
+clientId
+ |
+Client instance ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+group
+ |
+group
+ |
+Producer group
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+topic
+ |
+topic
+ |
+Topic to which a message is pushed
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+pid
+ |
+pid
+ |
+PID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent push
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message push errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of message push calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedMsgCount
+ |
+publishedMsgCount
+ |
+Number of push messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedBytes
+ |
+publishedBytes
+ |
+Number of push bytes
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message pushing
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for pushing messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being pushed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for pushing messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Queue monitoring (queuePublish: APM counts message push statistics by queue.)
+ |
+clientId
+ |
+clientId
+ |
+Client instance ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+group
+ |
+group
+ |
+Producer group
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+queue
+ |
+queue
+ |
+Message queue ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+pid
+ |
+pid
+ |
+PID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent push
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message push errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of message push calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedMsgCount
+ |
+publishedMsgCount
+ |
+Number of push messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedBytes
+ |
+publishedBytes
+ |
+Number of push bytes
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message pushing
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for pushing messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being pushed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for pushing messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Broker monitoring (brokerPublish: APM counts message push statistics by broker.)
+ |
+clientId
+ |
+clientId
+ |
+Client instance ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+group
+ |
+group
+ |
+Producer group
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+broker
+ |
+broker
+ |
+Broker address
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+pid
+ |
+pid
+ |
+PID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of messages for concurrent push
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of message push errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of message push calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedMsgCount
+ |
+publishedMsgCount
+ |
+Number of push messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedBytes
+ |
+publishedBytes
+ |
+Number of push bytes
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Information about the error that has occurred during message pushing
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for pushing messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of messages that are being pushed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for pushing messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Transaction monitoring (transactionPublish: APM counts transaction message push statistics by client.)
+ |
+clientId
+ |
+clientId
+ |
+Client instance ID
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+group
+ |
+group
+ |
+Producer group
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+pid
+ |
+pid
+ |
+PID
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum number of transaction messages for concurrent push
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of transaction message push errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of message push calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error information generated when an error has occurred during transaction message push
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time for pushing transaction messages
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of transaction messages that are being pushed at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for pushing transaction messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–200 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 200–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Total monitoring (total: APM counts message push statistics by client.)
+ |
+errorCount
+ |
+errorCount
+ |
+Number of message push errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of message push calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedMsgCount
+ |
+publishedMsgCount
+ |
+Number of push messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+publishedBytes
+ |
+publishedBytes
+ |
+Number of push bytes
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for pushing messages
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
GRPCClient Monitoring
+This section describes the types, names, and meanings of GRPCClient metrics collected by APM.
+
+
Table 1 GRPCClient monitoring metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Method monitoring (detail: APM counts URL call statistics by method.)
+ |
+method
+ |
+method
+ |
+Request method
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the method
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of times that the method fails to be called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the method is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the method in a collection period
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of executions of the method at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of the method
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Cluster call (cluster: APM counts URL call statistics based on the cluster ID of the caller.)
+ |
+clusterId
+ |
+clusterId
+ |
+Cluster ID of the caller
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times the cluster is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for calling the cluster
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of times that the cluster fails to be called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
GRPCServer Monitoring
+This section describes the types, names, and meanings of GRPCServer metrics collected by APM.
+
+
Table 1 GRPCServer monitoring collection parametersParameter
+ |
+Data Type
+ |
+Application Type
+ |
+Default
+ |
+Supported Start Agent Version
+ |
+Supported End Agent Version
+ |
+Description
+ |
+
|---|
+
+Sampling Type
+ |
+radio
+ |
+JAVA
+ |
+4
+ |
+1.0.0
+ |
+-
+ |
+Sampling type. Options: full sampling, percentage sampling, fixed-quantity sampling per minute, and intelligent sampling (default).
+ |
+
+Sampling Ratio
+ |
+integer
+ |
+JAVA
+ |
+10
+ |
+1.0.0
+ |
+-
+ |
+Percentage of samples to the total number of trace data records
+ |
+
+Samples/Minute
+ |
+integer
+ |
+JAVA
+ |
+1000
+ |
+1.0.0
+ |
+-
+ |
+Number of trace data records collected every minute.
+ |
+
+Slow Request Threshold
+ |
+integer
+ |
+JAVA
+ |
+800
+ |
+2.0.0
+ |
+-
+ |
+Slow request threshold. If the threshold is crossed, the method is regarded as a slow method. In that case, the trace sampling ratio will be increased by default.
+ |
+
+Method Configuration
+ |
+obj_array
+ |
+JAVA
+ |
+-
+ |
+2.0.0
+ |
+-
+ |
+Configure the slow request threshold and sampling ratio for each method separately. The following sampling policies can be set: percentage sampling, fixed-quantity sampling per minute, and automatic sampling.
+ |
+
+
+
+
+
+
Table 2 GRPCServer monitoring metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Method monitoring (detail: APM counts URL call statistics by method.)
+ |
+method
+ |
+method
+ |
+Request method
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the method
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of times that the method fails to be called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the method is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the method in a collection period
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of executions of the method at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of the method
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Cluster call (cluster: APM counts URL call statistics based on the cluster ID of the caller.)
+ |
+clusterId
+ |
+clusterId
+ |
+Cluster ID of the caller
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times the cluster is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for calling the cluster
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of times that the cluster fails to be called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
CoapClient Monitoring
+This section describes the types, names, and meanings of CoapClient metrics collected by APM.
+
+
Table 1 Call metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+URL monitoring (detail: APM counts URL call statistics by URL, packet type, and request type.)
+ |
+url
+ |
+url
+ |
+Request URL
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+requestType
+ |
+requestType
+ |
+Packet type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the method
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of times that the method fails to be called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the method is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the method in a collection period
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of executions of the method at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of the method
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+method
+ |
+method
+ |
+Request type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Status code (statusInfo: APM counts URL call statistics based on the status code returned.)
+ |
+statusInfo
+ |
+statusInfo
+ |
+Status code
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times that the status code has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+url
+ |
+url
+ |
+Sample URL which returns the status code in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Cluster call (CON packets) (cluster_con: APM counts URL call statistics (CON packets) based on the cluster ID.)
+ |
+clusterId
+ |
+clusterId
+ |
+Cluster ID of the caller
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times the cluster is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for calling the cluster
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of times that the cluster fails to be called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+CoapClient version (version)
+ |
+version
+ |
+version
+ |
+Version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+
+
+
+
CoapServer Monitoring
+This section describes the types, names, and meanings of CoapServer metrics collected by APM.
+
+
Table 1 CoapServer metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+URL monitoring (detail: APM counts URL call statistics by URL, packet type, and request type.)
+ |
+url
+ |
+url
+ |
+Request URL
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+requestType
+ |
+requestType
+ |
+Packet type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency of the method
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of times that the method fails to be called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times that the method is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time of the method in a collection period
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+runningCount
+ |
+runningCount
+ |
+Number of executions of the method at the time of collection
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time of the method
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+method
+ |
+method
+ |
+Request type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Status code (statusInfo: APM counts URL call statistics based on the status code returned.)
+ |
+statusInfo
+ |
+statusInfo
+ |
+Status code
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times that the status code has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+url
+ |
+url
+ |
+URL corresponding to the status code
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+Cluster call (cluster: APM counts URL call statistics based on the cluster ID of the caller.)
+ |
+clusterId
+ |
+clusterId
+ |
+Cluster ID of the caller
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of times the cluster is called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time for calling the cluster
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of times that the cluster fails to be called
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+clientErrorCount
+ |
+clientErrorCount
+ |
+Number of client errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+serverErrorCount
+ |
+serverErrorCount
+ |
+Number of server errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+CoapServer version (version)
+ |
+version
+ |
+version
+ |
+Version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+
+
+
+
MoquetteBroker Monitoring
+This section describes the types, names, and meanings of MoquetteBroker metrics collected by APM.
+
+
Table 1 MoquetteBroker metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Exception (exception: MoquetteBroker call exception statistics)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+MoquetteBroker version (version)
+ |
+version
+ |
+version
+ |
+Version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+MoquetteBroker topic summary (total: MoquetteBroker topic summary)
+ |
+msgSentCount
+ |
+msgSentCount
+ |
+Total number of message sending times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+bytesSent
+ |
+bytesSent
+ |
+Total number of bytes sent
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+msgReceivedCount
+ |
+msgReceivedCount
+ |
+Total number of message receiving times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+bytesReceived
+ |
+bytesReceived
+ |
+Total number of bytes received
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+MoquetteBroker topic-based monitoring (brokerTopic)
+ |
+topic
+ |
+topic
+ |
+Topic
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+subscribeCount
+ |
+subscribeCount
+ |
+Number of subscriptions
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+msgSentCount
+ |
+msgSentCount
+ |
+Number of message sending times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+bytesSent
+ |
+bytesSent
+ |
+Number of bytes sent
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+msgReceivedCount
+ |
+msgReceivedCount
+ |
+Number of message receiving times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+bytesReceived
+ |
+bytesReceived
+ |
+Number of bytes received
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
PahoPublisher Monitoring
+This section describes the types, names, and meanings of PahoPublisher metrics collected by APM.
+
+
Table 1 PahoPublisher metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Monitoring of PUBLISH packets sent by PahoPublisher (message)
+ |
+uri
+ |
+uri
+ |
+URI of the MQTT server connected to PahoPublisher
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+msgType
+ |
+msgType
+ |
+Type of the packet that is sent
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Node-based monitoring of PUBLISH packets sent by PahoPublisher (uriMessage)
+ |
+uri
+ |
+uri
+ |
+URI of the MQTT server connected to PahoPublisher
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Exception (exception: exception statistics of PahoPublisher calls)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+PahoPublisher monitoring by topic (clientPublish)
+ |
+clientId
+ |
+clientId
+ |
+clientId
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+topic
+ |
+topic
+ |
+Topic
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+msgSentCount
+ |
+msgSentCount
+ |
+Number of message sending times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+bytesSent
+ |
+bytesSent
+ |
+Number of bytes sent
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+PahoPublisher version (version)
+ |
+version
+ |
+version
+ |
+Version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+PahoPublisher topic summary (total)
+ |
+msgSentCount
+ |
+msgSentCount
+ |
+Total number of message sending times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+bytesSent
+ |
+bytesSent
+ |
+Total number of bytes sent
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
PahoSubscriber Monitoring
+This section describes the types, names, and meanings of PahoSubscriber metrics collected by APM.
+
+
Table 1 PahoSubscriber metricsCategory
+ |
+Metric
+ |
+Name
+ |
+Description
+ |
+Unit
+ |
+Data Type
+ |
+Default Aggregation Mode
+ |
+
|---|
+
+Monitoring of PUBLISH packets received by PahoSubscriber (message)
+ |
+uri
+ |
+uri
+ |
+URI of the MQTT server connected to PahoSubscriber
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+msgType
+ |
+msgType
+ |
+Type of the packet that is sent
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+concurrentMax
+ |
+concurrentMax
+ |
+Maximum concurrency
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+errorCount
+ |
+errorCount
+ |
+Number of errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+errorTraceId
+ |
+errorTraceId
+ |
+ID of the trace that encounters an error in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+slowTraceId
+ |
+slowTraceId
+ |
+ID of the slowest trace in a collection period
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Number of calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+lastError
+ |
+lastError
+ |
+Error message
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+maxTime
+ |
+maxTime
+ |
+Maximum response time
+ |
+-
+ |
+INT
+ |
+MAX
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range1
+ |
+range1
+ |
+Number of requests with 0–10 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range2
+ |
+range2
+ |
+Number of requests with 10–100 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range3
+ |
+range3
+ |
+Number of requests with 100–500 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range4
+ |
+range4
+ |
+Number of requests with 500–1000 ms response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range5
+ |
+range5
+ |
+Number of requests with 1–10s response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+range6
+ |
+range6
+ |
+Number of requests with response time longer than 10s
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Node-based monitoring of PUBLISH packets received by PahoSubscriber (uriMessage)
+ |
+uri
+ |
+uri
+ |
+URI of the MQTT server connected to PahoSubscriber
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+errorCount
+ |
+errorCount
+ |
+Errors
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+invokeCount
+ |
+invokeCount
+ |
+Calls
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+totalTime
+ |
+totalTime
+ |
+Total response time
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+Exception (exception: exception statistics of PahoSubscriber calls)
+ |
+exceptionType
+ |
+exceptionType
+ |
+Exception type
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+causeType
+ |
+causeType
+ |
+Exception class
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+count
+ |
+count
+ |
+Number of times the exception has occurred
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+message
+ |
+message
+ |
+Message returned when the exception occurred
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+stackTrace
+ |
+stackTrace
+ |
+Exception stack information
+ |
+-
+ |
+CLOB
+ |
+LAST
+ |
+
+PahoSubscriber topic-based monitoring (clientReceive)
+ |
+clientId
+ |
+clientId
+ |
+clientId
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+topic
+ |
+topic
+ |
+Topic
+ |
+-
+ |
+ENUM
+ |
+LAST
+ |
+
+msgReceivedCount
+ |
+msgReceivedCount
+ |
+Number of message receiving times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+bytesReceived
+ |
+bytesReceived
+ |
+Number of bytes received
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+PahoSubscriber version (version)
+ |
+version
+ |
+version
+ |
+Version
+ |
+-
+ |
+STRING
+ |
+LAST
+ |
+
+PahoSubscriber topic summary (total)
+ |
+msgReceivedCount
+ |
+msgReceivedCount
+ |
+Total number of message receiving times
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+bytesReceived
+ |
+bytesReceived
+ |
+Total number of bytes received
+ |
+-
+ |
+INT
+ |
+SUM
+ |
+
+
+
+
+
Java
+Supported Java Components and Frameworks
Currently, APM can connect to Java applications. APM supports multiple mainstream Java frameworks, web servers, communications protocols, and databases.
+
Table 1 Java components and frameworks supported by self-developed AgentsAgent Type
+ |
+Component
+ |
+JDK 1.8
+ |
+JDK 17
+ |
+
|---|
+
+Self-developed
+ |
+Dubbo
+ |
+2.6.x
+ |
+2.6.x
+ |
+
+Self-developed
+ |
+Jedis
+ |
+2.x.x-3.x.x
+ |
+2.x.x-3.x.x
+ |
+
+Self-developed
+ |
+Lettuce
+ |
+5.x.x
+ |
+5.x.x
+ |
+
+Self-developed
+ |
+ServiceComb
+ |
+2.x.x
+ |
+-
+ |
+
+Self-developed
+ |
+Log4j
+ |
+1.x.x
+ |
+1.x.x
+ |
+
+Self-developed
+ |
+Log4j2
+ |
+2.x.x
+ |
+2.x.x
+ |
+
+Self-developed
+ |
+HttpClient
+ |
+4.x.x
+ |
+4.x.x–5.3.x (5.x.x applies only to synchronization scenarios)
+ |
+
+Self-developed
+ |
+JDK HttpClient
+ |
+1.6–1.8
+ |
+17
+ |
+
+Self-developed
+ |
+MariaDB
+ |
+2.x.x
+ |
+2.x.x
+ |
+
+Self-developed
+ |
+MySQL
+ |
+5.x.x–8.x.x
+ |
+5.x.x–8.x.x
+ |
+
+Self-developed
+ |
+OkHttpClient
+ |
+3.x.x
+ |
+3.x.x
+ |
+
+Self-developed
+ |
+Tomcat
+ |
+6.x.x–9.x.x
+ |
+9.x.x
+ |
+
+Self-developed
+ |
+Jetty
+ |
+8.x.x–9.x.x
+ |
+9.x.x
+ |
+
+Self-developed
+ |
+gRPC
+ |
+1.x.x
+ |
+1.x.x
+ |
+
+Self-developed
+ |
+Reactor Netty
+ |
+1.x.x
+ |
+-
+ |
+
+Self-developed
+ |
+HBase
+ |
+2.x.x
+ |
+2.x.x
+ |
+
+Self-developed
+ |
+MongoDB
+ |
+3.x.x–4.x.x
+ |
+3.x.x–4.x.x
+ |
+
+Self-developed
+ |
+c3p0
+ |
+0.9.x
+ |
+0.9.x
+ |
+
+Self-developed
+ |
+Cassandra3
+ |
+3.x.x
+ |
+3.x.x
+ |
+
+Self-developed
+ |
+ClickHouse
+ |
+0.2.x
+ |
+0.2.x
+ |
+
+Self-developed
+ |
+DBCP
+ |
+2.x.x
+ |
+2.x.x
+ |
+
+Self-developed
+ |
+Druid
+ |
+1.x.x
+ |
+1.x.x
+ |
+
+Self-developed
+ |
+HttpAsyncClient
+ |
+4.x.x
+ |
+4.x.x
+ |
+
+Self-developed
+ |
+Jetty Client
+ |
+9.x.x
+ |
+9.x.x
+ |
+
+Self-developed
+ |
+MariaDB3
+ |
+3.x.x
+ |
+3.x.x
+ |
+
+Self-developed
+ |
+MyBatis
+ |
+3.x.x
+ |
+3.x.x
+ |
+
+Self-developed
+ |
+Netty
+ |
+4.x.x
+ |
+4.x.x
+ |
+
+Self-developed
+ |
+PostgreSQL
+ |
+42.x.x
+ |
+42.x.x
+ |
+
+Self-developed
+ |
+RabbitMQ
+ |
+5.x.x
+ |
+5.x.x
+ |
+
+Self-developed
+ |
+Undertow
+ |
+2.x.x
+ |
+2.x.x
+ |
+
+Self-developed
+ |
+WebSocket
+ |
+9.x.x
+ |
+9.x.x
+ |
+
+Self-developed
+ |
+Elasticsearch
+ |
+7.x.x
+ |
+7.x.x
+ |
+
+Self-developed
+ |
+Oracle
+ |
+10.x.x
+ |
+10.x.x
+ |
+
+Self-developed
+ |
+RocketMQ
+ |
+4.x.x
+ |
+4.x.x
+ |
+
+Self-developed
+ |
+Kafka
+ |
+2.x.x
+ |
+2.x.x
+ |
+
+
+
+
+
+
+
FAQs
+
+
+
+
+
diff --git a/docs/apm/umn/apm_02_0001.html b/docs/apm/umn/apm_02_0001.html
new file mode 100644
index 00000000..0155d1e9
--- /dev/null
+++ b/docs/apm/umn/apm_02_0001.html
@@ -0,0 +1,16 @@
+
+
+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.
+
- 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.
+
+
Monitoring Java Applications
+
+
+
diff --git a/docs/apm/umn/apm_02_0003.html b/docs/apm/umn/apm_02_0003.html
new file mode 100644
index 00000000..ccc7581b
--- /dev/null
+++ b/docs/apm/umn/apm_02_0003.html
@@ -0,0 +1,87 @@
+
+
+Connecting Agents
+Prerequisites
The network between your host and APM is normal.
+
You can run the Telnet command to check the network.
+
+
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
+ - 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
+
+Table 1 Parameter descriptionParameter
+ |
+Description
+ |
+Mandatory
+ |
+
|---|
+
+pwd
+ |
+Path where the apm-javaagent.jar package is located.
+ |
+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.
+ |
+Yes
+ |
+
+env
+ |
+Name of an environment where an application is deployed. A program can be deployed in different environments (such as the test or live network environment). Each environment is deployed in one region and has a unique region attribute. If this parameter is blank, the default environment will be used.
+ |
+No
+ |
+
+envTag
+ |
+Environment tag for filtering environments. Different environments may have the same tag. This parameter can be left blank.
+ |
+No
+ |
+
+business
+ |
+Name of an application that already exists (a global concept). If this parameter is left blank, the automatically created application will be used.
+ |
+No
+ |
+
+subBusiness
+ |
+Name of a sub-application (a global concept), which is similar to a folder. If it is left blank, resources will be mounted to the root application. There can be up to three layers of sub-applications. For example, for a/b/c, a, b, and c respectively represents a layer.
+ |
+No
+ |
+
+instanceName
+ |
+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.
+ |
+No
+ |
+
+
+
+
+
+
Manually Installing Agents for Java Applications
+Prerequisites
+
- 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
+
+
+
Procedure
- Download apm-javaagent to any directory of your host. For the download address, see JavaAgent Download Addresses.
Example command:
+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 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}
+If your enterprise has a large number of services, you can add more complex configurations. For example:
+java
-javaagent:/xxx/apm-javaagent/apm-javaagent.jar=appName=myApp,env=myEnv,envTag=myTag,business=myBusiness,subBusiness=mySub - The preceding parameters are built-in CMDB information of APM. For details, see CMDB Management.
- Due to historical reasons, the metadata of APM startup parameters conflicts with some CMDB concepts. The following shows the details.
Generally, the startup parameter is set to -javaagent:D:\javaagent-package\apm-javaagent\apm-javaagent.jar=appName=xxx,env=yyy,business=zzz,subBusiness=sss,envTag=xxx. appName indicates a component, business indicates an application, subBusiness indicates a sub-application, and envTag indicates an environment tag.
+If business is not set on the web page, the system reports an error when the JavaAgent is started. If other parameters (subBusiness, appName, env, and envTag) are not set, the system automatically creates them when the JavaAgent is started.
+Component names are unique under an application.
+
+
+
- Redeploy the application.
+
+
JavaAgent Download Addresses
+
+
Region
+ |
+Latest Version
+ |
+Earlier Version
+ |
+
|---|
+
+eu-de
+ |
+2.3.15
+sha256:fc547d5c9c62a80f079c5e67b2f999f0df2193f6f1a2e959bf5506b824ab7853
+ |
+-
+ |
+-
+ |
+-
+ |
+
+
+
+
+
Access Address (master.address)
+
+
Region
+ |
+Access Address (master.address)
+ |
+
|---|
+
+eu-de
+ |
+https://100.125.40.55:41333
+ |
+
+
+
+
+
Getting Started
+
+
+
diff --git a/docs/apm/umn/apm_03_0001.html b/docs/apm/umn/apm_03_0001.html
new file mode 100644
index 00000000..87bce21e
--- /dev/null
+++ b/docs/apm/umn/apm_03_0001.html
@@ -0,0 +1,11 @@
+
+
+Are APM Agents Compatible with Other Agents Such as Pinpoint?
+APM Agents are incompatible with other Agents. Generally, APM implements bytecode instrumentation based on the ASM framework. Installing two Agents means two instrumentation operations on your code. However, code instrumentation mechanisms vary according to products. If you install Agents of different products, code conflicts may occur, affecting performance.
+
What Is APM's Metric Data Sampling Policy?
+Metric data is collected periodically. The default collection period is 1 minute.
+
Why Does Metric Data Collection Fail?
+- You can view metric data several minutes after you connect Agents.
- If data collection is stopped, the possible causes are as follows:
- Instance level: Agents are stopped on the Instance tab page.
- Monitoring item level: Monitoring items are manually disabled on the Monitoring Item tab page.
- Global level: The Stop Collecting Data Through Bytecode Instrumentation option is enabled on the General Configuration page.
+
- If no data is collected for a long time, the possible causes are as follows:
- Java 9 prompts that the sql.time class cannot be found.
Cause analysis: Agents are developed using JDK 1.7. However, after Java 9 modularization, no SQL package is provided by default.
+Occurrence probability: This problem occurs under certain conditions.
+Workaround: Ensure that the component can proactively import java.sql to module-info.java.
+ - Java 11 prompts that "Caused by: java.lang.NoClassDefFoundError: sun/misc/Unsafe class cannot be found."
Cause analysis: Agents are developed using JDK 1.7, but the Java 11 Unsafe class is categorized to a different package.
+Occurrence probability: This problem occurs inevitably.
+Workaround: Ensure that the application can proactively import jdk.unsupported to module-info.java.
+ - Java 9 reports an illegal reflective access alarm. (This problem will be solved in versions later than Java 9.)
Workaround: Set --illegal-access to warn or delete this option.
+
+
+
Before You Start
+This document describes how to use Application Performance Management (APM).
+
+
Application List
+ |
+The Applications page displays information such as components, environments, Agent status, and supported operations.
+ |
+
+CMDB Management
+ |
+APM has built-in CMDB for managing the application structure and related configurations.
+ |
+
+Application Metric Monitoring
+ |
+APM can manage tags and monitor the metric data of JVM, GC, service calls, exceptions, external calls, database access, and middleware, helping you comprehensively monitor application running. Application metrics can be reported to the AOM console through Prometheus instances.
+ |
+
+Tracing
+ |
+Information such as the call status, duration, and API is displayed, helping you further locate fault causes.
+ |
+
+Application Topology
+ |
+The call and dependency relationships between applications are displayed, and abnormal instances can be automatically discovered.
+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.
+ |
+
+URL Tracing
+ |
+Through URL tracing, you can monitor the call relationships between important APIs and downstream services, and then detect problems more precisely.
+ |
+
+Alarm Management
+ |
+When an application connected to APM meets a preset alarm condition, an alarm is triggered and reported in a timely manner. In this way, you can quickly learn about service exceptions and rectify faults to prevent loss.
+ |
+
+Agent Management
+ |
+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.
+ |
+
+Configuration Management
+ |
+Configuration Management manages and displays the configurations supported by APM in a centralized manner. It consists of two parts:
+- Collection Center: displays collectors in a centralized manner. You can view and manage various collectors, metrics, and collection parameters supported by APM.
- Data Masking: You can set policies to mask the data reported using APM APIs.
+ |
+
+System Management
+ |
+System Management manages and displays system configurations in a centralized manner, including:
+- Access Keys: long-term identity credentials. They ensure that the requests are secret, complete, and correct.
- General Configuration: You can determine whether to collect data through bytecode instrumentation, specify the slow request threshold and maximum number of rows to collect, and set web monitoring aggregation.
- Agent Count: APM counts the number of Agents used by tenants.
+ |
+
+Permissions Management
+ |
+Enterprise Project Management Service (EPS) is used to control user access to APM resources.
+ |
+
+Learn more
+ |
+Permissions Management
+Create a user and grant permissions.
+Getting Started
+Learn how to connect applications to APM in different scenarios.
+ |
+
+
+
+
+
Application List
+Application List
The 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
+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.
+
+Status
+ |
+Description
+ |
+
|---|
+
+Enabled
+ |
+The Agent is running properly.
+ |
+
+Offline
+ |
+- The Agent is offline due to network problems. Check and restore the network.
- The Agent is offline if your process does not exist.
- The Agent is disabled and offline if the trial period expires.
+ |
+
+Disabled
+ |
+The Agent is manually or globally disabled. Contact technical support.
+ |
+
+
+
+
+
+
More Operations
Perform the operations listed in Table 1 if needed.
+
+
Table 1 Related operationsOperation
+ |
+Description
+ |
+
|---|
+
+Selecting an application
+ |
+Select an application from the Application drop-down list on the left of the page.
+ |
+
+Viewing the topology of an environment
+ |
+Click Topology in the Operation column of an environment.
+ |
+
+Setting a component or environment
+ |
+Click Configure in the Operation column. On the displayed Instance tab page, set the component or environment as required.
+ |
+
+Deleting an environment
+ |
+Click Delete in the Operation column of an environment.
+ |
+
+Searching for a component or environment
+ |
+Enter a component or environment keyword or name on the right.
+ |
+
+
+
+
+
+
Application Metric Monitoring
+
+
+
diff --git a/docs/apm/umn/apm_07_0004.html b/docs/apm/umn/apm_07_0004.html
new file mode 100644
index 00000000..f4a41077
--- /dev/null
+++ b/docs/apm/umn/apm_07_0004.html
@@ -0,0 +1,23 @@
+
+
+Overview
+APM Agents periodically collect performance metric data to measure the overall health status of applications. They can collect the metric data of JVM, GC, service calls, exceptions, external calls, database access, and middleware, helping you comprehensively monitor application running.
+
APM has strict definitions on metric data collection. Each type of data to be collected corresponds to a collector. For example, for JVM data of Java applications, a JVM collector is provided. A collector collects data of multiple metric sets. For details about collectors and metric sets, see Collection Center.
+
After collectors are deployed in the environment, monitoring items are generated. During data collection, the monitoring items determine data structures and collection behaviors.
+
- 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 Types
Agents 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.
+
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.
+
+
Monitoring Item Configuration
Collectors 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.
+
+
Monitoring Item Views
On the metric monitoring details page, a monitoring item corresponds to one or more tab views, and each view corresponds to a metric set. APM provides summary tables, trend graphs, latest data tables, and original tables. For details, see Monitoring Item Views.
+
+
Application Monitoring Details
+ The Metrics page displays only the involved monitoring item metrics of connected applications.
+
+
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
+ - 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.
+
+
Viewing URL Monitoring Data
URL summary
+
For common URL calls, the system collects the metrics of each URL. For details about the metrics, see Table 1.
+
Figure 4 URL summary under URL monitoring
+
+
Table 1 Parameters of the URL summaryMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+URL summary
+ |
+url
+ |
+URL
+ |
+
+method
+ |
+Request HTTP method
+ |
+
+Calls
+ |
+Number of times that the URL is called
+ |
+
+Avg RT (ms)
+ |
+Average response time of the URL in a collection period
+ |
+
+Errors
+ |
+Number of call errors of the URL
+ |
+
+Max Concurrency
+ |
+Maximum concurrency of the URL
+ |
+
+Max RT (ms)
+ |
+Maximum response time of the URL in a collection period
+ |
+
+Apdex
+ |
+Application performance index (Apdex), which indicates users' satisfaction. The value ranges from 0 to 1. The closer the value is to 1, the higher the satisfaction is.
+ |
+
+0 ms–10 ms
+ |
+Number of requests with 0 ms–10 ms response time
+ |
+
+10 ms–100 ms
+ |
+Number of requests with 10 ms–100 ms response time
+ |
+
+100 ms–500 ms
+ |
+Number of requests with 100 ms–500 ms response time
+ |
+
+500 ms–1s
+ |
+Number of requests with 500 ms–1s response time
+ |
+
+1s–10s
+ |
+Number of requests with 1s–10s response time
+ |
+
+10s–n
+ |
+Number of requests with response time longer than 10s
+ |
+
+
+
+
+
- URL invocation is the starting point of tracing. When you click a URL, the tracing page is displayed, showing the URL invocation condition in a certain period (default: 20 minutes).
- You can add a URL for tracing by referring to Configuring URL Tracing.
- Click a number in blue (such as those in the Calls or Avg RT (ms) column) to view more details.
+
Status code summary
+
APM supports status code-based summary. The system collects the metrics of each URL. For details about the metrics, see Table 2.
+
Figure 5 Status code summary under URL monitoring
+
+
Table 2 Parameters of status code summaryMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+Status code summary
+ |
+code
+ |
+Status code
+ |
+
+Count
+ |
+Number of times that the status code has occurred
+ |
+
+Latest URL
+ |
+Sample URL which returns the status code in a collection period
+ |
+
+
+
+
+
- Click a status code in the code column. The tracing page is displayed, showing the invocation condition of the status code of the selected instance in the environment in last 20 minutes (default).
- Click a number in the Count column to view the trend of the status code in a specified period.
- Click the latest URL to view the invocation details of the corresponding status code.
+
Cluster summary
+
APM can summarize metrics by cluster. For details about the metrics, see Table 3.
+
Figure 6 Cluster summary under URL monitoring
+
+
Table 3 Parameters of the cluster summaryMetric Set
+ |
+Parameter
+ |
+Description
+ |
+
|---|
+
+Cluster summary
+ |
+Cluster ID
+ |
+Cluster ID of the caller
+ |
+
+Calls
+ |
+Number of times the cluster is called
+ |
+
+Avg RT (ms)
+ |
+Average response time in a collection period
+ |
+
+Errors
+ |
+Number of times that the cluster fails to be called
+ |
+
+
+
+
+
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.
+
Figure 7 Overview under URL monitoring
+
+
Table 4 Overview metricsMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+Overview
+ |
+Total Requests
+ |
+Total number of URL requests
+ |
+
+Avg RT (ms)
+ |
+Average response time of the URL
+ |
+
+Errors
+ |
+Total number of URL errors
+ |
+
+Apdex
+ |
+Users' satisfaction towards the URL
+ |
+
+
+
+
+
+
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
+ - 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
+
+
+
Viewing JVM Information
On the JVM tab page, view the JVMInfo metrics of the corresponding instance. For details about the metrics, see Table 1.
+
Figure 4 Viewing JVM information
+
+
Table 1 JVMInfo metricsMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+JVMInfo
+ |
+JavaAgent Version
+ |
+Java Agent version
+ |
+
+Started
+ |
+JVM startup time
+ |
+
+Startup Parameter
+ |
+JVM startup parameter
+ |
+
+Java Class Library Path
+ |
+Java class library path
+ |
+
+Java Version
+ |
+Java version
+ |
+
+Java Specification Version
+ |
+Java specification version
+ |
+
+OS
+ |
+OS name
+ |
+
+OS Version
+ |
+OS version
+ |
+
+arch
+ |
+CPU architecture
+ |
+
+Processors
+ |
+Number of processors
+ |
+
+SDK Version
+ |
+SDK version
+ |
+
+
+
+
+
+
Viewing JVM Monitoring Data
APM 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
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+Thread
+ |
+Current Threads
+ |
+Number of current threads
+ |
+
+Deadlock Threads
+ |
+Number of deadlock threads
+ |
+
+Daemon Threads
+ |
+Number of daemon threads
+ |
+
+Started Threads
+ |
+Number of started threads
+ |
+
+Peak Threads
+ |
+Peak number of threads
+ |
+
+Thread Status
+ |
+Waiting Threads
+ |
+Number of waiting threads
+ |
+
+Terminated Threads
+ |
+Number of threads in the terminated state
+ |
+
+Runnable Threads
+ |
+Number of runnable threads
+ |
+
+Blocked Threads
+ |
+Number of blocked threads
+ |
+
+New Threads
+ |
+Number of new threads
+ |
+
+Timed Waiting Threads
+ |
+Number of threads that timed out
+ |
+
+Memory
+ |
+Used Non-Heap Memory
+ |
+Size of the used non-heap memory
+ |
+
+Used Heap Memory
+ |
+Size of the used heap memory
+ |
+
+Used Direct Memory
+ |
+Size of the used direct memory
+ |
+
+Class loading
+ |
+Current Classes
+ |
+Number of current classes
+ |
+
+Total Loaded Classes
+ |
+Total number of loaded classes
+ |
+
+Unloaded Classes
+ |
+Number of unloaded classes
+ |
+
+Memory pool
+ |
+committed(M)
+ |
+Size of available memory
+ |
+
+init(M)
+ |
+Size of the initialized memory
+ |
+
+max(M)
+ |
+Size of the maximum memory
+ |
+
+name
+ |
+Memory pool name
+ |
+
+used(M)
+ |
+Size of the used memory
+ |
+
+CPU
+ |
+CPU Usage
+ |
+CPU usage of the Java process
+ |
+
+
+
+
+
+
Viewing GC Information
APM monitors GC metrics. For details about the metrics, see Table 2.
+
Figure 6 Viewing GC information
+
+
Table 3 GC metricsMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+GC statistics
+ |
+Full GC (times)
+ |
+Number of full GC times in a collection period
+ |
+
+Full GC Duration (ms)
+ |
+Full GC duration in a collection period
+ |
+
+Young GC (times)
+ |
+Number of young GC times in a collection period
+ |
+
+Young GC Duration (ms)
+ |
+Young GC duration in a collection period
+ |
+
+GC Details
+ |
+GC Type
+ |
+GC type, which can be major or minor
+ |
+
+GC Cause
+ |
+GC cause
+ |
+
+Count
+ |
+Number of times that GC has occurred
+ |
+
+Total GC Duration (ms)
+ |
+GC duration
+ |
+
+Max GC Duration (ms)
+ |
+Time consumed by the slowest GC
+ |
+
+GC Recycler
+ |
+GC recycler name
+ |
+
+Slowest GC Details
+ |
+Details about the slowest GC
+ |
+
+
+
+
+
- Click the digits in blue (such as those in the Count, Total GC Duration (ms), or Max GC Duration (ms) column) to view the corresponding GC trend graph in a certain period (default: 20 minutes).
- On the GC details area, you can view the GC type, GC cause, count, total GC duration (ms), maximum GC duration (ms), GC recycler, and slowest GC details (details and history).
+
+
Viewing Threads
You can view the thread details of the corresponding instance on APM. For details, see Table 4.
+
Figure 7 Viewing threads
+
+
Table 4 Thread metricsMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+Thread details
+ |
+Thread Name
+ |
+Thread name
+ |
+
+Threads
+ |
+Number of threads
+ |
+
+CPU Time (ms)
+ |
+Thread CPU time
+ |
+
+Memory (MB)
+ |
+Memory (MB)
+ |
+
+Thread Stack
+ |
+Thread stack
+ |
+
+
+
+
+
- Click a number in the Threads column to view the trend of the thread in a specified period.
- Click Detail in the Thread Stack column to view the thread details.
- Click History in the Thread Stack column to view the historical thread stack list.
+
+
Viewing Java Methods
- By default, APM does not monitor Java methods. To monitor them, configure the JavaMethod monitoring item first.
- After the configuration is complete, the system monitors the methods and classes of JavaMethod.
- On the JVM page, select a target instance and JavaMethod to view details. For details, see Table 5.
+
Figure 8 Viewing Java methods
+
+
Table 5 JavaMethod metricsMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+JavaMethod
+ |
+Class
+ |
+Class
+ |
+
+Method
+ |
+Method
+ |
+
+Calls
+ |
+Number of times that the method is called
+ |
+
+Avg RT (ms)
+ |
+Average response time
+ |
+
+Errors
+ |
+Number of times that the method fails to be called
+ |
+
+Max Concurrency
+ |
+Maximum concurrency of the method
+ |
+
+Max RT (ms)
+ |
+Maximum response time of the method
+ |
+
+0 ms–10 ms
+ |
+Number of requests with 0 ms–10 ms response time
+ |
+
+10 ms–100 ms
+ |
+Number of requests with 10 ms–100 ms response time
+ |
+
+100 ms–500 ms
+ |
+Number of requests with 100 ms–500 ms response time
+ |
+
+500 ms–1s
+ |
+Number of requests with 500 ms–1s response time
+ |
+
+1s–10s
+ |
+Number of requests with 1s–10s response time
+ |
+
+10s–n
+ |
+Number of requests with response time longer than 10s
+ |
+
+
+
+
+
- Click a number (such as those in the Calls or Errors column) to view the trend of the thread in a specified period.
+
+
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
+
+Table 1 Exception and log parametersMetric Set
+ |
+Parameter
+ |
+Description
+ |
+
|---|
+
+Exception
+ |
+Class
+ |
+Exception class
+ |
+
+Exception Type
+ |
+Exception type
+ |
+
+Log Type
+ |
+Exception log type
+ |
+
+Total Exceptions
+ |
+Number of times that an exception has occurred
+ |
+
+Message
+ |
+Message returned when the exception has occurred
+ |
+
+Error Stack
+ |
+Error stack
+ |
+
+Log Version
+ |
+Log Type
+ |
+Log type
+ |
+
+Version
+ |
+Log version
+ |
+
+
+
+
- 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.
+ - 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.
+
+
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.
+
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.
+
+
Viewing HttpClient Monitoring Data
URL 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.
+
Figure 4 URL summary under HttpClient monitoring
+
+
Table 1 Parameters of URL summary under HttpClient monitoringMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+URL summary
+ |
+url
+ |
+Called URL
+ |
+
+method
+ |
+HTTP method of the URL
+ |
+
+Calls
+ |
+Number of times that the URL is called
+ |
+
+Avg RT (ms)
+ |
+Average response time of the called URL
+ |
+
+Errors
+ |
+Number of call errors of the URL
+ |
+
+Max Concurrency
+ |
+Maximum concurrency of the URL
+ |
+
+Max RT (ms)
+ |
+Maximum response time of the called URL
+ |
+
+0 ms–10 ms
+ |
+Number of requests with 0 ms–10 ms response time
+ |
+
+10 ms–100 ms
+ |
+Number of requests with 10 ms–100 ms response time
+ |
+
+100 ms–500 ms
+ |
+Number of requests with 100 ms–500 ms response time
+ |
+
+500 ms–1s
+ |
+Number of requests with 500 ms–1s response time
+ |
+
+1s–10s
+ |
+Number of requests with 1s–10s response time
+ |
+
+10s–n
+ |
+Number of requests with response time longer than 10s
+ |
+
+Error Trace
+ |
+ID of the trace that encounters an error in a collection period
+ |
+
+Slowest Trace
+ |
+ID of the slowest trace in a collection period
+ |
+
+
+
+
+
- Click a number in blue (such as those in the Calls or Avg RT (ms) column) to view more details.
- Click the text in blue (such as those in the Slowest Trace or Error Trace column) to view more details.
+
Cluster summary
+
APM can summarize external call metrics by cluster. For details about the metrics, see Table 2.
+
Figure 5 Cluster summary under HttpClient monitoring
+
+
Table 2 Parameters of cluster summary under HttpClient monitoringMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+Cluster summary
+ |
+envId
+ |
+Cluster ID of the called party
+ |
+
+Calls
+ |
+Number of times that the cluster URL is called
+ |
+
+Avg RT (ms)
+ |
+Average response time for calling the cluster URL
+ |
+
+Errors
+ |
+Number of call errors of the URL
+ |
+
+Max RT (ms)
+ |
+Maximum response time for calling the cluster URL
+ |
+
+hostUri
+ |
+URI of the host
+ |
+
+0 ms–10 ms
+ |
+Number of requests with 0 ms–10 ms response time
+ |
+
+10 ms–100 ms
+ |
+Number of requests with 10 ms–100 ms response time
+ |
+
+100 ms–500 ms
+ |
+Number of requests with 100 ms–500 ms response time
+ |
+
+500 ms–1s
+ |
+Number of requests with 500 ms–1s response time
+ |
+
+1s–10s
+ |
+Number of requests with 1s–10s response time
+ |
+
+10s–n
+ |
+Number of requests with response time longer than 10s
+ |
+
+
+
+
+
Click a number in blue (such as those in the Calls or Avg RT (ms) column) to view more details.
+
Status code summary
+
APM can summarize external call metrics by status code. For details about the metrics, see Table 3.
+
Figure 6 Status code summary under HttpClient monitoring
+
+
Table 3 Parameters of status code summary under HttpClient monitoringMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+Status code summary
+ |
+code
+ |
+Status code
+ |
+
+Count
+ |
+Number of times that the status code has occurred
+ |
+
+Latest URL
+ |
+URL that returns the status code
+ |
+
+
+
+
+
- Click a status code in the code column. The tracing page is displayed, showing the invocation condition of the status code of the selected instance in the environment in last 20 minutes (default).
- Click a number in the Count column to view the trend of the status code in a specified period.
- Click the latest URL to view the invocation details of the corresponding status code.
+
Exception
+
On the Exception tab page, view the exception statistics about HttpClient calls. For details about the metrics, see Table 4.
+
Figure 7 HttpClient monitoring exceptions
+
+
Table 4 Parameters of HttpClient monitoring exceptionsMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+Exception
+ |
+causeType
+ |
+Exception class
+ |
+
+exceptionType
+ |
+Exception type
+ |
+
+Count
+ |
+Number of times the exception has occurred
+ |
+
+Error Message
+ |
+Message returned when the exception has occurred
+ |
+
+Error Stack
+ |
+Exception stack information
+ |
+
+
+
+
+
- Click a number in blue in the Count column to view the trend of the thread in a specified period.
- Click the text in blue in the Error Message column to view message details.
- 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.
+
Overview
+
On the Overview tab page, view the metrics of the selected instance. For details about the metrics, see Table 5.
+
+
Figure 8 Overview under HttpClient monitoring
+
+
Table 5 Overview parameters of HttpClient monitoringMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+Overview
+ |
+Calls
+ |
+Total number of calls
+ |
+
+Avg RT (ms)
+ |
+Average response time
+ |
+
+Errors
+ |
+Total number of errors
+ |
+
+
+
+
+
+
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
+ - 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.
+
+
Viewing MySQL Database Monitoring Data
SQL 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.
+
Figure 4 SQL summary under MySQL database monitoring
+
+
Table 1 SQL summary parametersMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+SQL monitoring
+ |
+sql
+ |
+Unique ID of the SQL statement, which is used for alarm configuration
+ |
+
+SQL Statement
+ |
+SQL statement
+ |
+
+Calls
+ |
+Number of times that the SQL statement is called
+ |
+
+Avg RT (ms)
+ |
+Average response time (ms)
+ |
+
+Errors
+ |
+Number of errors that the SQL statement encounters
+ |
+
+Rows Read
+ |
+Number of read rows of the SQL statement
+ |
+
+Rows Updated
+ |
+Number of updated rows of the SQL statement
+ |
+
+Max Concurrency
+ |
+Maximum concurrency of the SQL statement
+ |
+
+Max RT (ms)
+ |
+Maximum response time of the SQL statement
+ |
+
+0 ms–10 ms
+ |
+Number of requests with 0 ms–10 ms response time
+ |
+
+10 ms–100 ms
+ |
+Number of requests with 10 ms–100 ms response time
+ |
+
+100 ms–200 ms
+ |
+Number of requests with 100 ms–200 ms response time
+ |
+
+200 ms–1s
+ |
+Number of requests with 200 ms–1s response time
+ |
+
+1s–10s
+ |
+Number of requests with 1s–10s response time
+ |
+
+10s–n
+ |
+Number of requests with response time longer than 10s
+ |
+
+Slowest Trace
+ |
+ID of the slowest trace in a collection period
+ |
+
+Error Trace
+ |
+ID of the trace that encounters an error in a collection period
+ |
+
+
+
+
+
- Click an SQL statement to view details.
- Click a number in blue (such as those in the Calls or Avg RT (ms) column) to view more details.
- Click a slow or an error trace to view its details.
+
Database summary
+
APM can summarize MySQL database metrics by database. For details about the metrics, see Table 2.
+
Figure 5 Database summary under MySQL database monitoring
+
+
Table 2 Database summary parametersMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+Database connections
+ |
+db
+ |
+Database name
+ |
+
+Connections Created
+ |
+Number of connections created by the database
+ |
+
+Connections Destroyed
+ |
+Number of the database's connections that have been destroyed
+ |
+
+Avg RT (ms)
+ |
+Average response time (ms)
+ |
+
+Calls
+ |
+Number of times that the database is called
+ |
+
+Errors
+ |
+Number of errors that the database encounters
+ |
+
+Rows Read
+ |
+Number of rows read from the database
+ |
+
+Rows Updated
+ |
+Number of rows updated in the database
+ |
+
+Max RT (ms)
+ |
+Maximum response time of the database
+ |
+
+0 ms–10 ms
+ |
+Number of requests with 0 ms–10 ms response time
+ |
+
+10 ms–100 ms
+ |
+Number of requests with 10 ms–100 ms response time
+ |
+
+100 ms–200 ms
+ |
+Number of requests with 100 ms–200 ms response time
+ |
+
+200 ms–1s
+ |
+Number of requests with 200 ms–1s response time
+ |
+
+1s–10s
+ |
+Number of requests with 1s–10s response time
+ |
+
+10s–n
+ |
+Number of requests with response time longer than 10s
+ |
+
+
+
+
+
Click a number in blue (such as those in the Calls or Avg RT (ms) column) to view more details.
+
Exception
+
On the Exception tab page, view exception statistics about SQL calls. For details about the metrics, see Table 3.
+
Figure 6 Viewing exception statistics about SQL calls
+
+
Table 3 Exception parametersMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+Exception
+
+ |
+causeType
+ |
+Exception class
+ |
+
+exceptionType
+ |
+Exception type
+ |
+
+Count
+ |
+Number of exceptions
+ |
+
+SQL
+ |
+SQL statement that encounters an exception
+ |
+
+Error Stack
+ |
+Exception stack information
+ |
+
+Message
+ |
+Error message
+ |
+
+
+
+
+
Overview
+
On the Overview tab page, view the call trend of the selected instance. For details about the metrics, see Table 4.
+
Figure 7 Overview
+
+
Table 4 Overview parametersMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+Overview
+ |
+Calls
+ |
+Total number of calls
+ |
+
+Rows Read
+ |
+Total number of read rows
+ |
+
+Avg RT (ms)
+ |
+Average response time (ms)
+ |
+
+Errors
+ |
+Total number of errors
+ |
+
+Rows Updated
+ |
+Number of rows updated in the database
+ |
+
+
+
+
+
Info
+
On the Info tab page, view the driver version information. Click the text in blue to view more details.
+
Figure 8 Info
+
+
Viewing Druid Connection Pool Monitoring Data
The Druid connection pool monitoring system collects data sources, connection details, additional configurations, and exception information. You can click 
in the upper right corner of the list to customize the columns you want to view. For details about the metrics, see Table 5.
+
+
Table 5 Druid connection pool parametersMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+Data source
+ |
+Connection Address
+ |
+Connection address
+ |
+
+Driver
+ |
+Driver name
+ |
+
+Initialized Connections
+ |
+Number of initialized connections
+ |
+
+Min Idle Connections in Pool
+ |
+Minimum of idle connections in a pool
+ |
+
+Max Idle Connections in Pool
+ |
+Maximum number of idle connections in a pool
+ |
+
+Max Connections in Pool
+ |
+Maximum number of connections in a pool
+ |
+
+Idle Connections
+ |
+Number of idle connections
+ |
+
+Max Idle Connections
+ |
+Maximum number of idle connections
+ |
+
+Active Connections
+ |
+Number of active connections
+ |
+
+Max Active Connections
+ |
+Maximum number of active connections
+ |
+
+Waiting Threads
+ |
+Number of waiting threads
+ |
+
+Max Waiting Threads
+ |
+Maximum number of waiting threads
+ |
+
+Upper Limit for Waiting Threads
+ |
+Upper limit for waiting threads
+ |
+
+Total Connections
+ |
+Total number of connections
+ |
+
+Connection details
+ |
+Connection Address
+ |
+Connection address
+ |
+
+Calls
+ |
+Number of calls
+ |
+
+Total RT (ms)
+ |
+Total response time (ms)
+ |
+
+Avg RT (ms)
+ |
+Average response time (ms)
+ |
+
+Errors
+ |
+Number of errors
+ |
+
+Max Concurrency
+ |
+Maximum number of concurrent connections
+ |
+
+Max RT (ms)
+ |
+Maximum response time
+ |
+
+0 ms–10 ms
+ |
+Number of requests with 0 ms–10 ms response time
+ |
+
+10 ms–100 ms
+ |
+Number of requests with 10 ms–100 ms response time
+ |
+
+100 ms–500 ms
+ |
+Number of requests with 100 ms–500 ms response time
+ |
+
+500 ms–1s
+ |
+Number of requests with 500 ms–1s response time
+ |
+
+1s–10s
+ |
+Number of requests with 1s–10s response time
+ |
+
+10s–n
+ |
+Number of requests with response time longer than 10s
+ |
+
+Additional configuration
+ |
+Connection Address
+ |
+Connection address
+ |
+
+Max Wait (ms)
+ |
+Maximum waiting time
+ |
+
+Test on Borrow
+ |
+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
+ |
+
+Test While Idle
+ |
+Whether to verify the validity of an idle connection when an application applies for it from the pool
+ |
+
+Remove Abandoned
+ |
+Whether to automatically reclaim timeout connections
+ |
+
+Remove Abandoned TimeoutMillis (ms)
+ |
+If a connection in the pool is not returned within the specified duration, the connection will be reclaimed.
+ |
+
+Remove Abandoned Count
+ |
+Number of timeout connection reclaims
+ |
+
+Min Evictable Idle TimeMillis (ms)
+ |
+Minimum idle time of a connection in the pool
+ |
+
+Time Between EvictionRunsMillis (ms)
+ |
+Interval for checking the validity of idle connections
+ |
+
+Exception
+ |
+causeType
+ |
+Exception class
+ |
+
+Exception Type
+ |
+Exception type
+ |
+
+Count
+ |
+Number of times the exception has occurred
+ |
+
+Error Message
+ |
+Message returned when the exception has occurred
+ |
+
+Error Stack
+ |
+Exception stack information
+ |
+
+Version
+ |
+Driver Version
+ |
+Driver version
+ |
+
+
+
+
+
- Click a number in blue (such as those in the Calls or Avg RT (ms) column) to view more details.
- Click the text in blue (such as those in the Driver or Driver Version column) to view more details.
+
Figure 9 Viewing Druid connection pool monitoring data
+
+
Application Monitoring Configuration
+
+
+
diff --git a/docs/apm/umn/apm_07_0012.html b/docs/apm/umn/apm_07_0012.html
new file mode 100644
index 00000000..09791db4
--- /dev/null
+++ b/docs/apm/umn/apm_07_0012.html
@@ -0,0 +1,27 @@
+
+
+Configuration Details
+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
+ - On the displayed page, edit the monitoring configuration. For details, see the corresponding section.
Figure 2 Editing the JVM monitoring configuration
+ - Click Yes.
+
+
Enabling or Disabling 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.
Figure 3 Enabling or disabling a monitoring item
+ - Locate the row that contains the target monitoring item and enable or disable it.
+
+
Configuring the MySQL Monitoring Item
+On the
Modify MySQL Monitoring Configuration page, set the following parameters:
- Collection Interval: The default value is 60s and cannot be changed.
- Collect Original SQL: This function is disabled by default. In that case, only SQL statements without values are collected, for example, select name from user where id=?. When this function is enabled, SQL statements with values are collected, for example, select name from user where id=1.
- shardTableName: specified when you need to aggregate multiple tables into one table. For example, there are two tables: UserTable_1 and UserTable_2. By default, two SQL statements (select name from UserTable_1 and select name from UserTable_2) are displayed on the SQL monitoring page. If you set shardTableName to UserTable, tables starting with UserTable are aggregated into the same table. Only one SQL statement (select name from UserTable) is displayed on the SQL monitoring page.
+
+
Figure 1 Configuring the MySQL monitoring item
+
Configuring the HttpClient Monitoring Item
+On the Modify HttpClient Monitoring Configuration page, set the following URL normalization parameters:
+
- Collection Interval: The default value is 60s and cannot be changed.
- URL normalization is used to aggregate URLs that meet the conditions you set. For example, http://localhost/rest/v1/test/123 and http://localhost/rest/v1/test/234 can be aggregated into http://localhost/rest/v1/test/{id}.
+
Figure 1 Configuring the HttpClient monitoring item
+
Normalization Methods
There are four normalization methods: Startwith, Endwith, Include, and Regex.
+
- Startwith: URLs starting with a certain expression are counted as normalized URLs. For example, URLs starting with http://127.0.0.1/v1 are aggregated into /v1/test/{id}, as shown in Figure 1.
- Endwith: URLs ending with a certain expression are counted as normalized URLs. For example, URLs ending with /test are aggregated into /{id}/test, as shown in Figure 1.
- Include: URLs containing a certain expression are counted as normalized URLs. For example, URLs containing test are aggregated into /test/{id}, as shown in Figure 1.
- Regex: URLs that meet the wildcard expression are counted as normalized URLs. For details about the wildcard rules, see Table 1.
+
Table 1 Wildcard descriptionWildcard
+ |
+Description
+ |
+
|---|
+
+?
+ |
+Matches any character.
+ |
+
+*
+ |
+Matches zero, one, or more characters.
+ |
+
+**
+ |
+Matches zero, one, or more directories.
+ |
+
+
+
+
+
+
Usage Example
The following is an example:
+
+
URL Path
+ |
+Description
+ |
+
|---|
+
+/app/p?ttern
+ |
+Matches files such as /app/pattern and /app/pAttern, excluding /app/pttern.
+ |
+
+/app/*.x
+ |
+Matches all .x files in the app directory.
+ |
+
+/**/example
+ |
+Matches /app/example, /app/foo/example, and /example.
+ |
+
+/app/**/dir/file.*
+ |
+Matches /app/dir/file.jsp, /app/foo/dir/file.htm, /app/foo/bar/dir/file.pdf, and /app/dir/file.c.
+ |
+
+/**/*.jsp
+ |
+Matches all .jsp files.
+ |
+
+
+
+
+
+
Configuring the URL Monitoring Item
+On the
Modify URL Monitoring Configuration page, set the following parameters:
For security purposes, do not contain sensitive data in headers, URL parameters, cookies, or other parameters.
+
+
+
Parameter
+ |
+Description
+ |
+Example
+ |
+
|---|
+
+Collection Interval
+ |
+The default value is 60s and cannot be changed.
+ |
+60s
+ |
+
+Key for Header Value Interception
+ |
+Key specified for collecting values in headers. The collected information can be seen in the trace parameters.
+ |
+Host
+ |
+
+Key for Parameter Value Interception
+ |
+Key specified for collecting values in URLs. The collected information can be seen in the trace parameters. Take http://127.0.0.1/test?param=123 as an example. If the key is set to param, value 123 can be seen in the trace parameters.
+ |
+param
+ |
+
+Key for Cookie Value Interception
+ |
+Key specified for collecting values in cookies. The collected information can be seen in the trace parameters.
+ |
+testKey
+ |
+
+URL Collection Configuration
+ |
+URLs that meet the conditions you set are aggregated. For example, /rest/v1/test/123 and /rest/v1/test/234 can be aggregated into /rest/v1/test/{id}. The configuration method is the same as that described in HttpClient URL Normalization.
+ |
+Figure 1
+ |
+
+Blocklist Configuration
+ |
+Data of URLs that meet the conditions you set will not be collected. The configuration method is the same as that described in HttpClient URL Normalization.
+ |
+Figure 1
+ |
+
+Service Code Length
+ |
+Maximum length of the response body to be parsed to prevent the performance from being affected. Content that beyond this limit will not be parsed, but corresponding service status codes are regarded as normal by default.
+ |
+-
+ |
+
+Key for Service Code Interception
+ |
+Key specified for collecting service status codes. If the custom API returned content is {"errorCode":500,"errorMsg":"error msg"}, set this parameter to errorCode.
+ |
+errorCode
+ |
+
+Normal Service Code
+ |
+If this status code is returned, traces are regarded as normal. If other codes are returned, traces are regarded as abnormal.
+ |
+-
+ |
+
+Slow Request Threshold
+ |
+Global response time threshold. The default value is 800. Requests with the response time longer than 800 ms are regarded as slow requests. The sampling ratio of slow requests will be increased.
+ |
+-
+ |
+
+URL Configuration
+ |
+Response time threshold separately set for a URL. If the response time of this URL exceeds the threshold, the sampling rate of this URL will be increased. If this parameter is not set, the global slow request threshold is used by default.
+ |
+Figure 1
+ |
+
+Error Code
+ |
+Options: 400 or greater and 500 or greater (default). By default, if status code 500 or greater occurs, the system regards that there is an error.
+ |
+-
+ |
+
+URL Automatic Normalization
+ |
+Example: There are three URL invocations:
+/get/xxx/a
+/get/xxx/b
+/get/xxx/b
+- If this parameter is set to Yes, URL automatic normalization is enabled.
After normalization:
+/get/xxx/a 1
+/get/xxx/b 2
+ - If this parameter is set to No, URL automatic normalization is disabled.
/get/xxx/{p} 3
+ - Use default value: The inherited tag value is preferentially used.
+ |
+-
+ |
+
+
+
+
+
+
Figure 1 Example
+
Configuring the JavaMethod Monitoring Item
+On the Modify JavaMethod Monitoring Configuration page, set method interception parameters.
+
- Collection Interval: The default value is 60s and cannot be changed.
- Method Interception Configuration: is used to collect specified service methods. The method data is displayed on the JavaMethod metric page and in traces.
- Intercepted Class: name of the fully-qualified class to be collected. Both the package name and class name need to be specified.
- Intercepted Method: name of the method to be collected. If multiple methods exist, separate them by commas (,), for example, testMethod1,testMethod2.
+
Figure 1 Configuring the JavaMethod monitoring item
+
Monitoring Item Views
+APM supports summary tables, trend graphs, latest data tables, and original data tables.
- Summary table: records the summary calculation results based on the primary key metric within a period. You can click a number or character string in the summary table to view the trend graph of the primary key metric.
- Trend graph: displays the trend of a primary key metric in a period. A trend graph may have breakpoints, indicating that no data is collected in this period. There are multiple reasons why data is not collected. For example, collectors do not collect the metrics with zero calls or the data may be lost.
- Original data table: For character strings, no trend graphs can be generated. Therefore, original data tables are used. Each row indicates the mapping between a time and a value.
- Latest data table: displays the latest data. You can click a data record to view its trend graph.
+
+
The view of each monitoring item is configured in the background and has not been opened. You can check views together with corresponding background metric sets. For details, see Metric Sets.
+
+
Tracing
+When the calls between enterprise microservices are complex, APM Agents sample some requests, and intercept corresponding requests and subsequent call information. For example, in the scenario where service A calls service B and then calls service C, after service A receives a request, APM determines whether to trace the request based on the intelligent sampling algorithm.
+
Intelligent Sampling Algorithm
APM uses the intelligent sampling algorithm to determine whether to trace requests.
+
- If a request needs to be traced, a trace ID is generated and details (events) about some important methods (generally the tree structure with the parent-child relationship) under service A are intercepted. At the same time, the trace ID is transparently transmitted to service B. The important methods under service B are also intercepted. The trace ID is also transparently transmitted to service C. Some methods under service C are intercepted in a similar way as those under services B and A. Each node respectively reports event information and an association relationship can be formed based on the trace ID. In this way, you can view the call details of the entire request based on the trace ID.
- If a request does not need to be traced, no trace ID is generated. Service B does not receive the trace ID and uses the same algorithm as service A to determine whether to perform tracing.
- After data is reported, APM stores not only all event details, but also the root event (called span) information of each service for subsequent trace search. Generally, you search for the span information and then obtain the overall trace details based on the trace ID in the span information.
- By default, the intelligent sampling policy is used. There are three types of URLs: error URLs, slow URLs (use the default 800 ms or customize a threshold), and normal URLs. The sampling ratio of each type of URL is calculated separately. For APM, statistics are collected and reported every minute. In the first collection period, all URLs are regarded as normal for sampling. In the second collection period, URLs are classified into error, slow, and normal URLs based on the statistics collected in the previous period.
- Sampling rate of error URLs: If the CPU usage is less than 30%, 100 records are collected per minute. If the CPU usage is greater than or equal to 30% but less than 60%, 50 records are collected per minute. If the CPU usage is greater than or equal to 60%, 10 records are collected per minute. At least two records are collected for each URL.
- Sampling rate of slow URLs: If the CPU usage is less than 30%, 100 records are collected per minute. If the CPU usage is greater than or equal to 30% but less than 60%, 50 records are collected per minute. If the CPU usage is greater than or equal to 60%, 10 records are collected per minute. At least two records are collected for each URL.
- Sampling rate of normal URLs: If the CPU usage is less than 30%, 20 records are collected per minute. If the CPU usage is greater than or equal to 30% but less than 60%, 10 records are collected per minute. If the CPU usage is greater than or equal to 60%, 5 records are collected per minute. At least one record is collected for each URL.
+
+
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 Search
This 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.
+
Table 1 Search criteria of tracesSearch Criterion
+ |
+Description
+ |
+Mandatory
+ |
+
|---|
+
+Application
+ |
+Application to which the trace belongs.
+ |
+Yes
+ |
+
+Region
+ |
+Region where the trace is located.
+ |
+Yes
+ |
+
+Component
+ |
+Component to which the trace belongs.
+ |
+No
+ |
+
+Environment
+ |
+Environment to which the trace belongs.
+ |
+No
+ |
+
+Instance
+ |
+Instance to which the trace belongs.
+ |
+No
+ |
+
+URL
+ |
+Trace URL, which can be a REST URL or real URL. A REST URL contains a variable name, for example, /apm/get/{id}. A real URL indicates an actual URL.
+ |
+No
+ |
+
+Exact Search
+ |
+Whether to perform exact match on URLs. If this option is selected, exact match is performed. If this option is not selected, fuzzy match is performed.
+ |
+No
+ |
+
+Call Method
+ |
+HTTP method of the trace.
+ |
+No
+ |
+
+Status Code
+ |
+HTTP status code returned by the trace.
+ |
+No
+ |
+
+Response Time
+ |
+Response time range of the trace. You can specify the minimum and maximum response time to search for the trace or leave them empty.
+ |
+No
+ |
+
+Exception or Not
+ |
+Whether to filter the traces that are regarded as exceptions.
+ |
+No
+ |
+
+Trace ID
+ |
+If you specify this parameter, other search criteria become invalid and the search will be performed based on the trace ID you specify.
+ |
+No
+ |
+
+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.
+For details about how to configure URL monitoring, see Configuring the URL Monitoring Item.
+ |
+No
+ |
+
+Global Trace ID
+ |
+Global ID of a trace. If you specify this parameter, other search criteria become invalid and the search will be performed based on the trace ID you specify.
+ |
+No
+ |
+
+Application Code
+ |
+If you have configured Service Code Length, Key for Service Code Interception, and Normal Service Code for URL monitoring, responses' application codes will be collected. You can search information based on application codes. Generally, the value of Application Code is the same as the value of Normal Service Code. For details about how to configure URL monitoring, see Configuring the URL Monitoring Item.
+ |
+No
+ |
+
+
+
+
+
+
Viewing Trace Details
Viewing Basic Information About the Trace Filtered Based on the Search Criteria
+
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:
+
- HTTP method of the trace.
- REST URL of the trace. A REST URL contains a variable name, for example, /apm/get/{id}. You can click the URL to go to the trace details page.
- Start time of the trace.
- HTTP status code returned by the trace.
- Response time of the trace.
- Trace ID.
- Component to which the trace belongs.
- Environment to which the trace belongs.
- Host of the instance to which the trace belongs.
- IP address of the instance to which the trace belongs.
- Actual URL of the trace.
+
You can also click a specific URL on the monitoring item view page, for example, the table view of the URL monitoring item. In this way, you can quickly search for required trace information based on preset search criteria.
+
Viewing the Complete Information About the Trace, Including Local Method Stacks and Remote Call Relationships
+
Click the name of a trace to view its details, as shown in the following figure.
+
- The upper part is the sequence diagram of the trace, which shows complete call relationships between components. This diagram contains the information about the client and server corresponding to each call. The lower the line is, the later a call occurs.
- The lower part lists the method stack details of the trace. Each line indicates a method call. You can view the detailed method call relationships of the trace. By default, only component methods supported by JavaAgents are displayed. To display application methods, configure the application methods to be intercepted during JavaMethod configuration.
+
+Figure 2 Call relationship
+Parameter description:
+
+
- Component and environment to which the called API belongs
- Response time (unit: ms) of the client. You can hover the mouse pointer over this digit to view more details.
- Response time (unit: ms) of the server.
- Key parameter of the method in the trace method stack. For example, for a Tomcat entry method, a real URL is displayed. For a MySQL call method, an executed SQL statement is displayed.
- Extended data of the trace method. Generally, parameters related to the method are displayed.
+
+
Application Topology
+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.
+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
+
+
+
Viewing the Global Topology
- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click an application. The application details page is displayed.
- Click the Global Topology tab to view the call and dependency relationships of all components under the application.
Click a line between components. The detailed data is displayed on the right.
+Use tags to filter calls or enable Display only calls between components to shield the calls of external components.
+Figure 2 Viewing the global topology
+
+
+
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.
+
Configuring URL Tracing
- 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 the environment that needs URL tracing. The environment details page is displayed. By default, the URL tab page is displayed.
- Move the mouse pointer to the target URL, click
, and add it for URL tracing.Figure 1 Configuring URL tracing
+
+
+
Checking the URL Tracing View
+
- On the URL Tracing Views tab page:
+
- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click an application. The application details page is displayed.
- Click the URL Tracing Views tab to check all URL tracing views of the application.
- Filter transaction views by region and environment.
- Click View in the Operation column of the row that contains the URL you want to view.
Figure 3 Checking the URL tracing view
+
+
+
Viewing the URL Tracing Configuration
The URL which has been added for tracing will be displayed in the URL tracing configuration list.
+
- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click an application. The application details page is displayed.
- Click the URL Tracing Configuration tab to check all URL tracing configurations of the application.
Figure 4 Viewing the URL tracing configuration list
+ - To delete a URL tracing configuration, click Delete in the Operation column.
Figure 5 Deleting a URL tracing configuration
+
+
+
Viewing Transactions
Transaction URLs are displayed in a list. By default, the system displays the invocation of all entries.
+
- In the navigation pane, choose Application Monitoring > Metrics.
- In the tree on the left, click an application. The application details page is displayed.
- Click the Transactions tab to view all transactions of the application.
Figure 6 Viewing transactions
+ - Click View the call chain in the Operation column of the target transaction. For operations related to call chains, see Tracing.
Figure 7 Viewing the call chain
+
+
+
Alarm Management
+
+
+
diff --git a/docs/apm/umn/apm_07_0022.html b/docs/apm/umn/apm_07_0022.html
new file mode 100644
index 00000000..625423fe
--- /dev/null
+++ b/docs/apm/umn/apm_07_0022.html
@@ -0,0 +1,24 @@
+
+
+Alarm List
+Alarms are reported by services connected to APM Agents when specified conditions are met. You can learn about service exceptions in a timely manner and quickly rectify faults to prevent service loss.
+
Alarm process
Figure 1 Alarm process
+
+
+
Alarm Policies
+You can configure alarm templates, create custom alarm policies, or use recommended alarm templates.
+
Configuring an Alarm Template
+APM allows you to configure alarm templates. You can create multiple alarm policies under a template and bind them to nodes.
+
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 an application. The metric details page of the application is displayed.
- Click the Alarm Templates tab.
Figure 1 Adding an alarm template
+ - Click Add Template to add an alarm template as prompted.
- Enter basic information and then click Next.
Template Name: Enter up to 64 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed.
+Remarks: Enter up to 512 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed.
+ - Click Add Alarm Policy to add an alarm policy.
- Basic information
Figure 2 Basic information
+
+Table 1 Basic information about an alarm policyParameter
+ |
+Description
+ |
+
|---|
+
+Policy Name
+ |
+Custom name, which cannot be left blank.
+Only letters, digits, underscores (_), and hyphens (-) are allowed. Enter up to 512 characters.
+ |
+
+Alarm Severity
+ |
+Severity of an alarm. Options: COMMON and CRITICAL.
+ |
+
+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.
+ |
+
+Monitoring Item
+ |
+Select a target monitoring item. The information about the selected item is displayed on the right.
+
+ |
+
+Metric Set
+ |
+Select a target metric set. The information about the selected metric set is displayed on the right.
+
+
+ |
+
+
+
+
- Alarm rule
Figure 3 Alarm rule
+
+Table 2 Alarm rule parametersParameter
+ |
+Description
+ |
+
|---|
+
+Dimension
+ |
+(Optional) A category of metrics.
+ |
+
+Metric
+ |
+Metric for which you want to define one or more alarm rules.
+Metric: a metric in the metric set. For example, if Monitoring Item is set to Url and Metric Set is set to total, you can select the errorCount metric.
+Operator: operation to be performed.
+Threshold: threshold of the metric.
+ |
+
+Alarm Condition
+ |
+Condition for triggering an alarm.
+A: the number of collection periods. Range: 1–10.
+B: the number of times the alarm is triggered. Range: 1–10. This value cannot be greater than that of A.
+C: period (in minutes) during which identical alarms will not be sent. This period cannot be shorter than 10 minutes.
+ |
+
+Recovery Policy
+ |
+Condition for clearing an alarm. For example, if this parameter is set to 3, the alarm status will change to "Cleared" if no alarm is generated within 3 minutes.
+ |
+
+Notification upon Recovery
+ |
+Whether to notify recipients of alarm clearance.
+ |
+
+Multi-Line Matching
+ |
+(Optional) Whether to define data in the alarm notification content line by line.
+ |
+
+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.
+
+ |
+
+
+
+
- Notification object
+Figure 4 Notification object
+
+Table 3 Alarm notification parametersParameter
+ |
+Description
+ |
+
|---|
+
+Use default settings
+ |
+- If this option is enabled, alarms will be sent to one or more default notification objects. For details about how to set notification objects, see Alarm Notification.
- After this option is enabled, you can no longer select notification objects from the Notification Object drop-down list.
- If all the values in the Default column of the Notifications page are No, no default notification objects have been set. In this case, the Use default settings option on the alarm policy creation page is dimmed and cannot be enabled.
+ |
+
+Notification Object
+ |
+Select a notification object from the drop-down list.
+Alarms will only be sent to the selected notification objects.
+ |
+
+
+
+
- Click Yes.
- Click Next. The Bind Node page is displayed.
- Click Bind Node to bind nodes by environment, environment tag, or region.
Figure 5 Binding nodes
+
+
Table 4 Node parametersParameter
+ |
+Description
+ |
+
|---|
+
+All
+ |
+All nodes (including those added subsequently) in all regions will be bound.
+ |
+
+Environment
+ |
+All nodes in the selected environment will be bound.
+ |
+
+Environment Tag
+ |
+All nodes with the same tag will be bound.
+ |
+
+Region
+ |
+All nodes in the selected region will be bound.
+ |
+
+
+
+
+
+ - Click Yes. The information about the bound nodes is displayed in the lower part of the page, including the environment, tag, and region names.
If there are multiple types of bound nodes, only information about the nodes with the same environment, tag, and region is displayed.
+
+ - Click Complete.
+
+
More Operations
After the alarm template is created, perform the operations listed in Table 5 if needed.
+
+
Table 5 Related operationsOperation
+ |
+Description
+ |
+
|---|
+
+Copying a template
+ |
+Click Copy in the Operation column in the row that contains the template you want to copy.
+ |
+
+Modifying a template
+ |
+Click Modify in the Operation column in the row that contains the template you want to modify.
+ |
+
+Deleting a template
+ |
+Click Delete in the Operation column in the row that contains the template you want to delete.
+ |
+
+Starting and stopping a template
+ |
+Turn on or off the button ( ) in the Operation column in the row that contains the template you want to start or stop.
+ |
+
+
+
+
+
+
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
+
+
+
More Operations
After the alarm policy is created, perform the operations listed in Table 1 if needed.
+
+
Table 1 Related operationsOperation
+ |
+Description
+ |
+
|---|
+
+Starting or stopping a policy
+ |
+In the custom alarm policy list, start ( in the Operation column) or stop the target policy.
+ |
+
+Modifying a policy
+ |
+Click Edit in the Operation column in the row that contains the policy you want to modify.
+ |
+
+Deleting a policy
+ |
+Click Delete in the Operation column in the row that contains the policy you want to delete.
+ |
+
+
+
+
+
+
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
+ - 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.
+
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.
+Figure 1 Viewing Agents
+
+
The following table describes the Agent statuses.
+
+
Status
+ |
+Description
+ |
+
|---|
+
+Enabled
+ |
+The Agent is running properly.
+ |
+
+Offline
+ |
+The Agent is abnormal due to a network error. Check and restore the network.
+ |
+
+Disabled
+ |
+The Agent is manually or globally disabled. Contact technical support.
+ |
+
+
+
+
+
+
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
+ - In the dialog box that is displayed, click Yes to disable, enable, or delete the Agents for the selected hosts.
Figure 4 Deleting Agents
+
+
+
Upgrading Agents
+Update Agent versions according to the following procedure.
+
+
+
Configuration Management
+
+
+
diff --git a/docs/apm/umn/apm_07_0031.html b/docs/apm/umn/apm_07_0031.html
new file mode 100644
index 00000000..87a107f4
--- /dev/null
+++ b/docs/apm/umn/apm_07_0031.html
@@ -0,0 +1,89 @@
+
+
+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
+ - 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.
+
+
+
+
Collector
A collector is a plug-in for collecting metric data. It consists of the collector description, metric set, and collection parameters. Collector description describes the data collected by a collector. Metric set is the data collected according to specifications. Collection parameters are the custom data to be collected.
+
- Data is collected by APM Agents. For example, Java performance data is collected by JavaAgents. The data collected by APM Agents must correspond to the data models of collectors' metric sets so that servers can process the data.
- The Agent of each language and framework defines its own collector.
- After a collector is added to an environment, it is instantiated as a monitoring item. This process is generally automated. APM Agents automatically discover collection plug-ins used by applications and add collectors to the environment to form monitoring items. For example, if a Java application connects to a database through the JDBC driver for MySQL, the MySQL collector is automatically added to the environment to form a monitoring item.
+
+
Collection Parameters
Collectors 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. For details about how to set collection parameters, see Application Monitoring Configuration.
+
+
Metric Sets
A collector collects data of multiple metric sets. For example, the URL collector collects URL details, overall call condition, and status statistics. Each type of statistics corresponds to a metric set. Each metric set contains multiple metrics. For example, the metric set of URL details contains metrics such as the URL, method, number of calls, number of errors, and slowest call. Each metric corresponds to a data type.
+
APM supports the following types of metric data:
+
Table 1 APM metric data typesData Type
+ |
+Description
+ |
+Remarks
+ |
+
|---|
+
+ENUM
+ |
+Enumeration
+ |
+Primary key type.
+In the example of URL monitoring, the URL and method metrics are primary keys, and other metrics such as the number of calls correspond to the URL and method.
+ |
+
+INT
+ |
+Integer
+ |
+Maximum size: 8 bytes
+ |
+
+DOUBLE
+ |
+Floating-point number
+ |
+8-byte floating-point number
+ |
+
+STRING
+ |
+Character string
+ |
+Maximum length: 1024 characters
+ |
+
+CLOB
+ |
+Large character string
+ |
+Maximum size: 1 MB
+ |
+
+DATETIME
+ |
+Time
+ |
+Time is automatically displayed on the page.
+ |
+
+
+
+
+
+
+
System Management
+
+
+
diff --git a/docs/apm/umn/apm_07_0034.html b/docs/apm/umn/apm_07_0034.html
new file mode 100644
index 00000000..b7e13f23
--- /dev/null
+++ b/docs/apm/umn/apm_07_0034.html
@@ -0,0 +1,37 @@
+
+
+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.
+
Precautions
A 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:
+
- Compile a Java class, for example, com.demo.DecryptDemo, and add a decryption method, for example, decrypt both the input and output to character strings.
- Compile the decryption method to decrypt the SK and return the decrypted value.
- Pack the com.demo.DecryptDemo class into a JAR package and place this JAR package and its dependent packages in the apm-javaagent/ext folder of JavaAgent.
- Add the following content to the apm.config file:
decrypt.className=com.demo.DecryptDemo
+decrypt.methodName=decrypt
+secret.key={Character string encrypted by users}
+
+
+
+
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
+ - 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.
+
+
+
Deleting an Access Key
- In the navigation pane, choose System Management > Access Keys.
- On the Access Keys page, locate the row that contains the target access key and click Delete in the Operation column.
- On the page that is displayed, click Yes to delete the access key.
+
+
Enabling or Disabling an Access Key
Each access key is enabled by default. To disable it, do as follows:
+
- In the navigation pane, choose System Management > Access Keys.
- On the Access Keys page, locate the row that contains the target access key and click Disable in the Operation column.
- On the page that is displayed, click Yes to disable the access key.
To enable it again, click Enable in the row that contains the access key. On the page that is displayed, click Yes.
+
+
+
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
+- Stop Collecting Data Through Bytecode Instrumentation
Enable or disable this function as required. Data such as JVM metrics will always be collected using MBeans. The default value is No.
+ When the Stop Collecting Data Through Bytecode Instrumentation option is enabled, data will no longer be collected through bytecode instrumentation. Data such as JVM, GC, and Tomcat thread metrics can still be collected using MBeans.
+
+ - Slow Request Threshold
If this threshold is reached, more samples will be collected during intelligent sampling. The default value is 800.
+ - Max. Collected Data Rows
If this value is reached, data will not be collected to prevent excessive memory usage. The default value is 499.
+
+
+
Permissions Management
+
+
+
diff --git a/docs/apm/umn/apm_07_0037.html b/docs/apm/umn/apm_07_0037.html
new file mode 100644
index 00000000..555abadb
--- /dev/null
+++ b/docs/apm/umn/apm_07_0037.html
@@ -0,0 +1,11 @@
+
+
+Authorizing Users and User Groups Using Enterprise Projects
+Enterprise Project Management Service (EPS) is used to control user access to APM resources. After creating IAM user groups for employees, you can create enterprise projects on the Enterprise Management console and grant permissions to the user groups in the enterprise projects to implement personnel authorization and permission control. You can create enterprise projects. Then you can manage resources across different regions by enterprise project, grant different permissions to user groups, and add them to enterprise projects.
+
Creating a User and Granting Permissions
+This chapter describes how to use IAM for fine-grained permissions control for your APM resources. With IAM, you can:
+
- Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing APM resources.
- Manage permissions on a principle of least permissions (PoLP) basis.
- Entrust an account or cloud service to perform efficient O&M on your APM resources.
+
If your account does not need individual IAM users, skip this chapter.
+
This section describes the procedure for granting permissions (see Figure 1).
+
Prerequisite
Learn about the permissions supported by APM and choose policies or roles based on your requirements. For details, see Permissions Management.
+
+
Process Flow
Supported Cloud Services
+
Figure 1 Process for granting APM permissions
+
- Creating a User Group and Assigning Permissions
Create a user group on the IAM console, and assign the APM ReadOnlyAccess policy to the group.
+ - Creating a User
Create a user on the IAM console and add the user to the group created in 1.
+ - Logging In as an IAM User and Verifying Permissions
Log in to the APM console using the created user, and verify that the user only has read permissions for APM.
+
+
+
Change History
+
+
Table 1 Change historyDate
+ |
+Description
+ |
+
|---|
+
+2024-06-30
+ |
+This issue is the first official release.
+ |
+
+
+
+
+
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
+- 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
+- Current Agent: number of Agents used by the current application.
- Historical Agent: number of Agents used in each hour of today, yesterday, or a custom day.
+
+
+
Configuring the EsRestClient Monitoring Item
+On the Modify EsRestClient Monitoring Configuration page, set the following parameter:
+
- Collection Interval: The default value is 60s and cannot be changed.
- Index Normalization Configuration: The system matches indexes based on a regular expression and then normalizes them.
+
Configuring the Tomcat Monitoring Item
+On the Modify Tomcat Monitoring Configuration page, set the following parameter:
+
Collection Interval: The default value is 60s and cannot be changed.
+
Configuring the ApacheHttpClient Monitoring Item
+On the Modify ApacheHttpClient Monitoring Configuration page, set the following parameter:
+
Collection Interval: The default value is 60s and cannot be changed.
+
Configuring the HBase Monitoring Item
+On the Modify HBase Monitoring Configuration page, set the following parameter:
+
Collection Interval: The default value is 60s and cannot be changed.
+
Configuring the Jedis Monitoring Item
+On the Modify Jedis Monitoring Configuration page, set the following parameter:
+
Collection Interval: The default value is 60s and cannot be changed.
+
Configuring the Redis Monitoring Item
+On the Modify Redis Monitoring Configuration page, set the following parameters:
+
- Collection Interval: The default value is 60s and cannot be changed.
- Parameter Parsing: The default value is No. If you select Use default value, the value of the inherited tag is preferentially used.
- Parameter Length: The default value is 1000. If you select Use default value, the value of the inherited tag is preferentially used.
- Distinguish Redis Ports: The default value is No. If you select Use default value, the value of the inherited tag is preferentially used.
+
Configuring the ApacheHttpAsyncClient Monitoring Item
+On the Modify ApacheHttpAsyncClient Monitoring Configuration page, set the following parameters:
+
- Collection Interval: The default value is 60s and cannot be changed.
+
Configuring the Druid Monitoring Item
+On the Modify Druid Monitoring Configuration page, set the following parameters:
+
- Collection Interval: The default value is 60s and cannot be changed.
- TraceReportTimeSpanThreshold(ms): threshold for reporting getConnection method traces. If the threshold is not exceeded, such traces will not be reported. The default value is 1. If you select Use default value, the value of the inherited tag is preferentially used.
- Get pool info when calling getConnection: specifies whether to obtain the pool information when calling the getConnection method. The default value is No. If you select Use default value, the value of the inherited tag is preferentially used.
+
Configuring the WebSocket Monitoring Item
+On the Modify WebSocket Monitoring Configuration page, set the following parameter:
+
Collection Interval: The default value is 60s and cannot be changed.
+
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.
+
Configuring the KafkaProducer Monitoring Item
+On the Modify KafkaProducer Monitoring Configuration page, set the following parameter:
+
Collection Interval: The default value is 60s and cannot be changed.
+
Configuring the Hikari Monitoring Item
+On the Modify Hikari Monitoring Configuration page, set the following parameters:
+
- Collection Interval: The default value is 60s and cannot be changed.
- TraceReportTimeSpanThreshold(ms): The default value is 1. If Use default value is selected, the value of the inherited tag is preferentially used.
- Get pool info when calling getConnection: The default value is No. If Use default value is selected, the value of the inherited tag is preferentially used.
+
Configuring the Exception Monitoring Item
+On the Modify Exception Monitoring Configuration page, set the following parameters:
+
- Collection Interval: The default value is 60s and cannot be changed.
- Determine Trace Exception upon Log Error Detection: The default value is Yes. If Use default value is selected, the value of the inherited tag is preferentially used.
+
Configuring the Thread Monitoring Item
+On the Modify Thread Monitoring Configuration page, set the following parameters:
+
- Collection Interval: The default value is 60s and cannot be changed.
+
Configuring the GC Monitoring Item
+On the Modify GC Monitoring Configuration page, set the following parameter:
+
Collection Interval: The default value is 60s and cannot be changed.
+
Configuring the JVMInfo Monitoring Item
+On the Modify JVMInfo Monitoring Configuration page, set the following parameter:
+
Collection Interval: The default value is 60s and cannot be changed.
+
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
+ - 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
+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
+
+Table 1 Tomcat monitoring parametersMetric Set
+ |
+Metric
+ |
+Description
+ |
+
|---|
+
+Tomcat port monitoring
+ |
+name
+ |
+Port name
+ |
+
+Current Threads
+ |
+Number of current threads on the port
+ |
+
+Busy Threads
+ |
+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
+ |
+
+Max Threads
+ |
+Maximum number of threads on the port
+ |
+
+Max Connections
+ |
+Maximum number of connections on the port
+ |
+
+Current Connections
+ |
+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
+ |
+
+Version
+ |
+Version
+ |
+Tomcat version
+ |
+
+
+
+
- Click a number in blue (such as those in the Current Threads, Busy Threads, or Peak Busy Threads column) to view the trend graph of the target web container in the specified period.
- Click a version in the Version column to view details.
+ - 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.
+
+
Configuring the JVMMonitor Monitoring Item
+On the Modify JVMMonitor Monitoring Configuration page, set the following parameters:
+
- Collection Interval: The default value is 60s and cannot be changed.
- Call Chain Stack Collection Threshold: When the request latency exceeds the threshold, the stack is automatically printed. The default value is 0 and the maximum value is 10000.
+
Configuring ProbeInfo Monitoring Item
+On the Modify ProbeInfo Monitoring Configuration page, set the following parameter:
+
Collection Interval: The default value is 60s and cannot be changed.
+
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
+ - 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
+ - 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
+
+
+
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
+ - In the displayed dialog box, set application parameters.
+
Table 1 Parameters for creating an applicationParameter
+ |
+Description
+ |
+
|---|
+
+Application Name
+ |
+Name of an application, which cannot be empty.
+Enter 1 to 128 characters and start with a letter. Only digits, letters, underscores (_), and hyphens (-) are allowed.
+ |
+
+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.
+ |
+
+Enterprise Project
+ |
+Select an enterprise project from the drop-down list.
+ |
+
+Description
+ |
+Description of the application. Enter up to 1000 characters.
+ |
+
+
+
+
- Click Confirm.
After an application is created, connect it to APM for monitoring.
+
+
+
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
+ - Configure the application and sub-application according to Table 1.
+
Table 1 Parameters for configuring the application and sub-applicationOperation
+ |
+Description
+ |
+
|---|
+
+Modify
+ |
+Click Modify. In the displayed dialog box, modify the information about the application or sub-application.
+ |
+
+Set as Default
+ |
+If you select Set as Default for an application, it will become the default application. When you log in to the system, the default application will be selected. This option is not available for sub-applications.
+ |
+
+Delete
+ |
+Click Delete.
+ |
+
+
+
+
- Click Yes.
+
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
+ - In the displayed dialog box, set sub-application parameters.
+
Table 1 Parameters for creating a sub-applicationParameter
+ |
+Description
+ |
+
|---|
+
+Sub-application Name
+ |
+Name of a sub-application, which cannot be empty.
+Enter 1 to 128 characters and start with a letter. Only digits, letters, underscores (_), and hyphens (-) are allowed.
+ |
+
+Display Name
+ |
+Display name of a sub-application, which cannot be empty.
+Enter 1 to 128 characters. Only digits, letters, underscores (_), hyphens (-), brackets, and periods (.) are allowed.
+ |
+
+Description
+ |
+Description of the sub-application. Enter up to 1000 characters.
+ |
+
+
+
+
- Click Yes.
A maximum of three layers of sub-applications can be created.
+
+
+
Managing Tags
+You can add tags for different environments and applications for easy management.
+
Tag management covers tags and global tags.
+
A tag is used to set a collector corresponding to the monitoring item under one or more environments of an application.
+
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
+ - On the page that is displayed, set Tag and Description, and select the environment to be associated.
+
Table 1 Tag parametersParameter
+ |
+Description
+ |
+
|---|
+
+Tag
+ |
+Enter 1 to 128 characters. Only digits, letters, underscores (_), hyphens (-), brackets, and periods (.) are allowed.
+ |
+
+Description
+ |
+Enter up to 1000 characters. Only digits, letters, underscores (_), hyphens (-), brackets, and periods (.) are allowed.
+ |
+
+Bind Environment
+ |
+- Search by component, environment, or application name is supported.
- You can select one or more environments.
+ |
+
+
+
+
- Click Yes.
+
+
Modifying a Tag
- In the navigation pane, choose Application Monitoring > Metrics.
- In the navigation tree, select a target application.
- Click the Tags tab.
- Locate the row that contains the tag to be modified and click Collector Configuration in the Operation column. In the dialog box that is displayed, select your desired collector from the drop-down list and click Yes.
Locate the row that contains the tag to be modified and click Change Environment in the Operation column. In the dialog box that is displayed, select your desired environment and click Yes.
+Locate the row that contains the tag to be modified and click Modify Tag in the Operation column. In the dialog box that is displayed, modify the tag and description.
+Figure 2 Modifying a tag
+
+
+
Deleting a Tag
- In the navigation pane, choose Application Monitoring > Metrics.
- In the navigation tree, select a target application.
- Click the Tags tab.
- Locate the row that contains the target tag and click Delete in the Operation column. Alternatively, select the tags to delete and click Delete above the tag list.
Figure 3 Deleting a tag
+ - In the dialog box that is displayed, click Yes.
+
+
Global Tag Collector Configuration
- In the navigation pane, choose Application Monitoring > Metrics.
- In the navigation tree, select a target application.
- Click the Tags tab.
- Click Global tag collector configuration.
Figure 4 Global tag collector configuration
+ - Select a collector from the drop-down list and click Yes. For details about how to configure monitoring items, see Application Monitoring Configuration.
+
+
Data Masking
+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
+
+
+
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
+ |
+Description
+ |
+
|---|
+
+Configuration Name
+ |
+Used to identify a data masking configuration. This parameter cannot be empty. Enter up to 30 characters. Only letters, digits, and special characters are allowed.
+ |
+
+Configuration Description
+ |
+Used to describe the data masking configuration. This parameter cannot be empty. Enter up to 1000 characters. Only letters, digits, and special characters are allowed.
+ |
+
+Configuration Items
+ |
+- Enter up to 32 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed.
- The configuration item cannot be empty. By default, an empty configuration item is displayed. If you select Token, content will be replaced with a globally unique random character string. If you select Mask, content will be replaced with a fixed number of asterisks (*). By default, Mask is selected.
- Click the plus sign (+) to add a configuration item, or click the minus sign (–) to delete one.
- Each configuration can contain up to 20 configuration items.
- The httpMethod, remoteAddr, exceptionType, content-type, charset, api_address, url, method, requestBody, responseBody, exceptionMsg, cookie, and Cookie fields have special functions in APM traces and do not support masking.
- If you use one of these fields as a key, the system will display a message indicating that an invalid name exists.
+ |
+
+
+
+
+
- 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
+ - 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
+
+
+
