Merge remote-tracking branch 'origin/main' into HEAD

Reviewed-by: otcbot <otcbot@t-systems.com>
Co-authored-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-committed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>

docs/apm/umn/PARAMETERS.txt

@@ -0,0 +1,3 @@
+version=""
+language="en-us"
+type=""

docs/apm/umn/apm_01_0001.html

@@ -0,0 +1,29 @@
+<a name="apm_01_0001"></a><a name="apm_01_0001"></a>
+
+<h1 class="topictitle1">Service Overview</h1>
+<div id="body39451090"></div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="apm_01_0002.html">What Is APM</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0003.html">Functions</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0004.html">Application Scenarios</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0005.html">Basic Concepts</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0006.html">Edition Differences</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0007.html">Permissions Management</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0013.html">Metric Overview</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0008.html">Privacy and Sensitive Information Protection Statement</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0009.html">Data Collection</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0010.html">Usage Restrictions</a></strong><br>
+</li>
+</ul>
+</div>
+

docs/apm/umn/apm_01_0002.html

@@ -0,0 +1,70 @@
+<a name="apm_01_0002"></a><a name="apm_01_0002"></a>
+
+<h1 class="topictitle1">What Is APM</h1>
+<div id="body8662426"><div class="section" id="apm_01_0002__en-us_topic_0000001195565132_section89968509512"><h4 class="sectiontitle">O&amp;M Challenges</h4><p id="apm_01_0002__en-us_topic_0000001195565132_p117588488414">In the cloud era, applications in the microservice architecture are increasingly diversified, bringing many application exceptions. Application O&amp;M faces the following challenges:</p>
+<ul id="apm_01_0002__en-us_topic_0000001195565132_ul637951781412"><li id="apm_01_0002__en-us_topic_0000001195565132_li19522015191816">Distributed applications have complex relationships. As a result, it is hard to ensure normal application running, and quickly locate faults and performance bottlenecks.</li><li id="apm_01_0002__en-us_topic_0000001195565132_li585013711538">Users choose to leave due to poor experience. If O&amp;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.</li><li id="apm_01_0002__en-us_topic_0000001195565132_li761712732216">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&amp;M costs and improve O&amp;M efficiency.</li></ul>
+</div>
+<div class="section" id="apm_01_0002__en-us_topic_0000001195565132_section1421813348523"><h4 class="sectiontitle">Introduction to APM</h4><p id="apm_01_0002__en-us_topic_0000001195565132_p19619245135220">Application Performance Management (APM) helps O&amp;M personnel quickly identify application performance bottlenecks and locate root causes of faults, ensuring user experience.</p>
+<p id="apm_01_0002__en-us_topic_0000001195565132_p06185421439">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.</p>
+<div class="note" id="apm_01_0002__en-us_topic_0000001195565132_note63914352294"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="apm_01_0002__en-us_topic_0000001195565132_p1622762118134">APM is short for Application Performance Management. <strong id="apm_01_0002__en-us_topic_0000001195565132_b1828125417304">apm2</strong> is the registered endpoint address.</p>
+</div></div>
+
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="apm_01_0002__en-us_topic_0000001195565132_table17517155912448" frame="border" border="1" rules="all"><caption><b>Table 1 </b>APM monitoring capabilities</caption><thead align="left"><tr id="apm_01_0002__en-us_topic_0000001195565132_row6979359164416"><th align="left" class="cellrowborder" valign="top" width="24.83%" id="mcps1.3.2.5.2.3.1.1"><p id="apm_01_0002__en-us_topic_0000001195565132_p158141511483">Capability</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="75.17%" id="mcps1.3.2.5.2.3.1.2"><p id="apm_01_0002__en-us_topic_0000001195565132_p1890511910115">Description</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="apm_01_0002__en-us_topic_0000001195565132_row11231288911"><td class="cellrowborder" valign="top" width="24.83%" headers="mcps1.3.2.5.2.3.1.1 "><p id="apm_01_0002__en-us_topic_0000001195565132_p1897918771517">Non-intrusive collection of application performance data</p>
+</td>
+<td class="cellrowborder" valign="top" width="75.17%" headers="mcps1.3.2.5.2.3.1.2 "><p id="apm_01_0002__en-us_topic_0000001195565132_p2980777150">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.</p>
+</td>
+</tr>
+<tr id="apm_01_0002__en-us_topic_0000001195565132_row13979559104412"><td class="cellrowborder" valign="top" width="24.83%" headers="mcps1.3.2.5.2.3.1.1 "><p id="apm_01_0002__en-us_topic_0000001195565132_p81731205536">Application metric monitoring</p>
+</td>
+<td class="cellrowborder" valign="top" width="75.17%" headers="mcps1.3.2.5.2.3.1.2 "><p id="apm_01_0002__en-us_topic_0000001195565132_p1517330105313">APM automatically monitors application metrics, such as JVM, JavaMethod, URL, Exception, Tomcat, HttpClient, MySQL, Redis, and Kafka.</p>
+</td>
+</tr>
+<tr id="apm_01_0002__en-us_topic_0000001195565132_row3985115914449"><td class="cellrowborder" valign="top" width="24.83%" headers="mcps1.3.2.5.2.3.1.1 "><p id="apm_01_0002__en-us_topic_0000001195565132_p139051519151120">Application topology</p>
+</td>
+<td class="cellrowborder" valign="top" width="75.17%" headers="mcps1.3.2.5.2.3.1.2 "><p id="apm_01_0002__en-us_topic_0000001195565132_p1190521971119">APM automatically generates call relationships between distributed applications based on dynamic analysis and intelligent computing of remote procedure call (RPC) information.</p>
+</td>
+</tr>
+<tr id="apm_01_0002__en-us_topic_0000001195565132_row3991115954410"><td class="cellrowborder" valign="top" width="24.83%" headers="mcps1.3.2.5.2.3.1.1 "><p id="apm_01_0002__en-us_topic_0000001195565132_p184169364143">Tracing</p>
+</td>
+<td class="cellrowborder" valign="top" width="75.17%" headers="mcps1.3.2.5.2.3.1.2 "><p id="apm_01_0002__en-us_topic_0000001195565132_p1541663621416">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.</p>
+</td>
+</tr>
+<tr id="apm_01_0002__en-us_topic_0000001195565132_row99911599446"><td class="cellrowborder" valign="top" width="24.83%" headers="mcps1.3.2.5.2.3.1.1 "><p id="apm_01_0002__en-us_topic_0000001195565132_p12905101917116">Metric drill-down analysis</p>
+</td>
+<td class="cellrowborder" valign="top" width="75.17%" headers="mcps1.3.2.5.2.3.1.2 "><p id="apm_01_0002__en-us_topic_0000001195565132_p1090516192117">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.</p>
+</td>
+</tr>
+<tr id="apm_01_0002__en-us_topic_0000001195565132_row199563155114"><td class="cellrowborder" valign="top" width="24.83%" headers="mcps1.3.2.5.2.3.1.1 "><p id="apm_01_0002__en-us_topic_0000001195565132_p164711437182619">Error or slow URL tracing</p>
+</td>
+<td class="cellrowborder" valign="top" width="75.17%" headers="mcps1.3.2.5.2.3.1.2 "><p id="apm_01_0002__en-us_topic_0000001195565132_p447116378268">APM identifies error or slow URLs based on URL tracing, and automatically associates them with corresponding APIs, such as SQL and MQ APIs.</p>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+<ol id="apm_01_0002__en-us_topic_0000001195565132_ol20487111016266"><li id="apm_01_0002__en-us_topic_0000001195565132_li11487171062616">Access to APM: Applications need to implement AK/SK authentication to connect to APM.</li><li id="apm_01_0002__en-us_topic_0000001195565132_li348714108269">O&amp;M data collection: APM can collect data about applications, basic resources, and user experience from Agents in non-intrusive mode.</li><li id="apm_01_0002__en-us_topic_0000001195565132_li13335281588">Service implementation: APM supports application metric monitoring, application topology, tracing, and intelligent alarm reporting.</li><li id="apm_01_0002__en-us_topic_0000001195565132_li11487181012612">Service expansion:<ul id="apm_01_0002__en-us_topic_0000001195565132_ul539681181414"><li id="apm_01_0002__en-us_topic_0000001195565132_li839619110147">You can quickly diagnose application performance exceptions based on the application topology and tracing of APM, and make judgments based on the application O&amp;M metrics of Application Operations Management (AOM).</li><li id="apm_01_0002__en-us_topic_0000001195565132_li919713571510">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.</li></ul>
+</li></ol>
+</div>
+<div class="section" id="apm_01_0002__en-us_topic_0000001195565132_section890022319284"><h4 class="sectiontitle">Advantages</h4><p id="apm_01_0002__en-us_topic_0000001195565132_p690022316288"><span><img id="apm_01_0002__en-us_topic_0000001195565132_image7234016175415" src="en-us_image_0000001278522953.png"></span></p>
+<p id="apm_01_0002__en-us_topic_0000001195565132_p69002023112819">Connects to applications without having to modify code, and collects data in a non-intrusive mode.</p>
+<ul id="apm_01_0002__en-us_topic_0000001195565132_ul1238928174017"><li id="apm_01_0002__en-us_topic_0000001195565132_li1078792411227">APM Agents collect service call, service inventory, and call KPI data.</li></ul>
+<p id="apm_01_0002__en-us_topic_0000001195565132_p1190082322816"><span><img id="apm_01_0002__en-us_topic_0000001195565132_image3344204185518" src="en-us_image_0000001278405305.png"></span></p>
+<p id="apm_01_0002__en-us_topic_0000001195565132_p29001323182814">Delivers high throughput (hundreds of millions of API calls), ensuring premium experience.</p>
+<p id="apm_01_0002__en-us_topic_0000001195565132_p1190002317281"><span><img id="apm_01_0002__en-us_topic_0000001195565132_image17372854145513" src="en-us_image_0000001234565280.png"></span></p>
+<p id="apm_01_0002__en-us_topic_0000001195565132_p49006237281">Provides open APIs to query O&amp;M data, offers collection standards, and supports independent development.</p>
+<p id="apm_01_0002__en-us_topic_0000001195565132_p582243217711"><span><img id="apm_01_0002__en-us_topic_0000001195565132_image477910515563" src="en-us_image_0000001278805009.png"></span></p>
+<p id="apm_01_0002__en-us_topic_0000001195565132_p16379202174111">Reports alarms using Artificial Intelligence (AI) threshold detection and machine learning based on historical baseline data, and supports root cause analysis.</p>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0001.html">Service Overview</a></div>
+</div>
+</div>
+

docs/apm/umn/apm_01_0003.html

@@ -0,0 +1,36 @@
+<a name="apm_01_0003"></a><a name="apm_01_0003"></a>
+
+<h1 class="topictitle1">Functions</h1>
+<div id="body8662426"><p id="apm_01_0003__en-us_topic_0000001195725120_a29547e649dec42d0aa22f42b2a46e98f">APM manages cloud application performance. It provides application metric monitoring, tracing, application topology, URL tracing, intelligent alarm reporting, and tag/Agent/configuration/system management.</p>
+<div class="section" id="apm_01_0003__en-us_topic_0000001195725120_section87847237262"><h4 class="sectiontitle">Application Metric Monitoring</h4><p id="apm_01_0003__en-us_topic_0000001195725120_p18561034192613">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.</p>
+</div>
+<div class="section" id="apm_01_0003__en-us_topic_0000001195725120_s8fe70ad540db459e961007661d2e6f9b"><h4 class="sectiontitle">Tracing</h4><p id="apm_01_0003__en-us_topic_0000001195725120_p735211153458">APM comprehensively monitors calls and displays service execution traces and statuses, helping you quickly locate performance bottlenecks and faults.</p>
+<ul id="apm_01_0003__en-us_topic_0000001195725120_ul8448181744511"><li id="apm_01_0003__en-us_topic_0000001195725120_li3826119144514">In the displayed trace list, click the target trace to view its basic information.</li><li id="apm_01_0003__en-us_topic_0000001195725120_li16448141704516">On the trace details page, you can view the trace's complete information, including the local method stack and remote call relationships.</li></ul>
+</div>
+<div class="section" id="apm_01_0003__en-us_topic_0000001195725120_s8afb4805418f43babf479007542d1263"><h4 class="sectiontitle">Application Topology</h4><p id="apm_01_0003__en-us_topic_0000001195725120_p169421337185614">There are two types of application topologies:</p>
+<ul id="apm_01_0003__en-us_topic_0000001195725120_ul136411410115710"><li id="apm_01_0003__en-us_topic_0000001195725120_li1641161055713">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.</li><li id="apm_01_0003__en-us_topic_0000001195725120_li166821213635">Global application topology: topology of some or all components under an application.</li></ul>
+<p id="apm_01_0003__en-us_topic_0000001195725120_p1178410198319">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.</p>
+</div>
+<div class="section" id="apm_01_0003__en-us_topic_0000001195725120_section1756183611472"><h4 class="sectiontitle">URL Tracing</h4><p id="apm_01_0003__en-us_topic_0000001195725120_p1769751115459">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.</p>
+</div>
+<div class="section" id="apm_01_0003__en-us_topic_0000001195725120_section16710105815235"><h4 class="sectiontitle">Tag Management</h4><p id="apm_01_0003__en-us_topic_0000001195725120_p7379144520242">You can add tags for different environments and applications for easy management.</p>
+</div>
+<div class="section" id="apm_01_0003__en-us_topic_0000001195725120_section736516214504"><h4 class="sectiontitle">Intelligent Alarm Reporting</h4><p id="apm_01_0003__en-us_topic_0000001195725120_p33651528508">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.</p>
+<p id="apm_01_0003__en-us_topic_0000001195725120_p56995325529">APM allows you to configure alarm templates. You can create multiple alarm policies under a template and bind them to nodes.</p>
+<p id="apm_01_0003__en-us_topic_0000001195725120_p107521323247">With intelligent alarm reporting, you can receive alarms by SMS, email, or function.</p>
+</div>
+<div class="section" id="apm_01_0003__en-us_topic_0000001195725120_section8445935142417"><h4 class="sectiontitle">Agent Management</h4><p id="apm_01_0003__en-us_topic_0000001195725120_p10708145182415">You can view the deployment and running statuses of the Agents that are connected to APM, and to stop, start, or delete them.</p>
+</div>
+<div class="section" id="apm_01_0003__en-us_topic_0000001195725120_section167672023113"><h4 class="sectiontitle">Configuration Management</h4><p id="apm_01_0003__en-us_topic_0000001195725120_p13398849103114"><strong id="apm_01_0003__en-us_topic_0000001195725120_b1174162164317">Configuration Management</strong> consists of <strong id="apm_01_0003__en-us_topic_0000001195725120_b1793801717434">Collection Center</strong> and <strong id="apm_01_0003__en-us_topic_0000001195725120_b14375121584320">Data Masking</strong>.</p>
+<ul id="apm_01_0003__en-us_topic_0000001195725120_ul1296918498331"><li id="apm_01_0003__en-us_topic_0000001195725120_li1396934912334"><strong id="apm_01_0003__en-us_topic_0000001195725120_b14543143604315">Collection Center</strong>: displays collectors in a centralized manner. You can view and manage various collectors, metrics, and collection parameters supported by APM.</li><li id="apm_01_0003__en-us_topic_0000001195725120_li1783117531334"><strong id="apm_01_0003__en-us_topic_0000001195725120_b1768316142530">Data Masking</strong>: You can set policies to mask the data reported using APM APIs.</li></ul>
+</div>
+<div class="section" id="apm_01_0003__en-us_topic_0000001195725120_section203313236354"><h4 class="sectiontitle">System Management</h4><p id="apm_01_0003__en-us_topic_0000001195725120_p19109203310353"><strong id="apm_01_0003__en-us_topic_0000001195725120_b91771133204619">System Management</strong> consists of <strong id="apm_01_0003__en-us_topic_0000001195725120_b18784144244618">Access Keys</strong>, <strong id="apm_01_0003__en-us_topic_0000001195725120_b1993620493462">General Configuration</strong>, and <strong id="apm_01_0003__en-us_topic_0000001195725120_b83811657144611">Agent Count</strong>.</p>
+<ul id="apm_01_0003__en-us_topic_0000001195725120_ul114621013103614"><li id="apm_01_0003__en-us_topic_0000001195725120_li164621313163619"><strong id="apm_01_0003__en-us_topic_0000001195725120_b8511827152619">Access Keys</strong>: 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.</li><li id="apm_01_0003__en-us_topic_0000001195725120_li2650161912363"><strong id="apm_01_0003__en-us_topic_0000001195725120_b5911392529">General Configuration</strong>: You can determine whether to collect data through bytecode instrumentation, and specify the slow request threshold and maximum number of rows to collect.</li><li id="apm_01_0003__en-us_topic_0000001195725120_li10409182419361"><strong id="apm_01_0003__en-us_topic_0000001195725120_b328716012527">Agent Count</strong>: APM can count the Agents used by tenants. You can view the number of Agents by time, region, or Agent type.</li></ul>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0001.html">Service Overview</a></div>
+</div>
+</div>
+

docs/apm/umn/apm_01_0004.html

@@ -0,0 +1,31 @@
+<a name="apm_01_0004"></a><a name="apm_01_0004"></a>
+
+<h1 class="topictitle1">Application Scenarios</h1>
+<div id="body8662426"><p id="apm_01_0004__en-us_topic_0000001195245194_p172477203500">APM is widely used. The following lists some typical scenarios.</p>
+<div class="section" id="apm_01_0004__en-us_topic_0000001195245194_section53112724911"><h4 class="sectiontitle">Diagnosis of Application Exceptions</h4><p id="apm_01_0004__en-us_topic_0000001195245194_p19512737151010"><strong id="apm_01_0004__en-us_topic_0000001195245194_b19197131571919">Pain Points</strong></p>
+<p id="apm_01_0004__en-us_topic_0000001195245194_p29559161434">In the distributed microservice architecture, enterprises can develop diverse applications efficiently, but face great challenges in traditional O&amp;M and diagnosis. An e-commerce application may face the following problems:</p>
+<ul id="apm_01_0004__en-us_topic_0000001195245194_ul4628204913326"><li id="apm_01_0004__en-us_topic_0000001195245194_li274142118173">Difficult fault locating<p id="apm_01_0004__en-us_topic_0000001195245194_p87411021121716"><a name="apm_01_0004__en-us_topic_0000001195245194_li274142118173"></a><a name="en-us_topic_0000001195245194_li274142118173"></a>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&amp;M personnel need to repeatedly view logs on multiple hosts to locate the fault. Even for simple problems, troubleshooting requires cooperation from multiple teams.</p>
+</li><li id="apm_01_0004__en-us_topic_0000001195245194_li1762804910323">Difficult architecture sort-out<p id="apm_01_0004__en-us_topic_0000001195245194_p1562815499325"><a name="apm_01_0004__en-us_topic_0000001195245194_li1762804910323"></a><a name="en-us_topic_0000001195245194_li1762804910323"></a>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.</p>
+</li></ul>
+<p id="apm_01_0004__en-us_topic_0000001195245194_p1573712541215"><strong id="apm_01_0004__en-us_topic_0000001195245194_b8537151992312">Service Implementation</strong></p>
+<p id="apm_01_0004__en-us_topic_0000001195245194_p8497354144915">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.</p>
+<ul id="apm_01_0004__en-us_topic_0000001195245194_ul109109683114"><li id="apm_01_0004__en-us_topic_0000001195245194_li0828659144">Visible topology: Abnormal application instances can be automatically discovered on the topology.</li><li id="apm_01_0004__en-us_topic_0000001195245194_li546112010474">Tracing: You can locate root causes in code through drill-downs after identifying abnormal applications.</li><li id="apm_01_0004__en-us_topic_0000001195245194_li291117623113">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.</li></ul>
+</div>
+<div class="section" id="apm_01_0004__en-us_topic_0000001195245194_section64215411461"><h4 class="sectiontitle">User Experience Management</h4><p id="apm_01_0004__en-us_topic_0000001195245194_p17611458254"><strong id="apm_01_0004__en-us_topic_0000001195245194_b17502175614333">Pain Points</strong></p>
+<p id="apm_01_0004__en-us_topic_0000001195245194_p045155818452">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?</p>
+<p id="apm_01_0004__en-us_topic_0000001195245194_p6489314914"><strong id="apm_01_0004__en-us_topic_0000001195245194_b7953115173414">Service Implementation</strong></p>
+<p id="apm_01_0004__en-us_topic_0000001195245194_p15463832219">APM analyzes the complete process (user request &gt; server &gt; database &gt; server &gt; 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.</p>
+<ul id="apm_01_0004__en-us_topic_0000001195245194_ul1133410518119"><li id="apm_01_0004__en-us_topic_0000001195245194_li858953565317">Application KPI analysis: KPIs such as throughput, latency, and call success rate are displayed, so that you can monitor user experience easily.</li><li id="apm_01_0004__en-us_topic_0000001195245194_li43344571117">Full-link performance tracing: Web services, caches, and databases are traced, so that you can detect performance bottlenecks quickly.</li></ul>
+</div>
+<div class="section" id="apm_01_0004__en-us_topic_0000001195245194_section783054361111"><h4 class="sectiontitle">Intelligent Diagnosis</h4><p id="apm_01_0004__en-us_topic_0000001195245194_p252912155333"><strong id="apm_01_0004__en-us_topic_0000001195245194_b94213285195">Pain Points</strong></p>
+<p id="apm_01_0004__en-us_topic_0000001195245194_p4866112414200">Massive services bring abundant but unassociated application O&amp;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&amp;M experience library?</p>
+<p id="apm_01_0004__en-us_topic_0000001195245194_p241910016123"><strong id="apm_01_0004__en-us_topic_0000001195245194_b14989343161911">Service Implementation</strong></p>
+<p id="apm_01_0004__en-us_topic_0000001195245194_p2859131461912">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.</p>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0001.html">Service Overview</a></div>
+</div>
+</div>
+

docs/apm/umn/apm_01_0005.html

@@ -0,0 +1,43 @@
+<a name="apm_01_0005"></a><a name="apm_01_0005"></a>
+
+<h1 class="topictitle1">Basic Concepts</h1>
+<div id="body8662426"><div class="section" id="apm_01_0005__en-us_topic_0000001240325091_section017712413327"><h4 class="sectiontitle">Application Topology</h4><p id="apm_01_0005__en-us_topic_0000001240325091_p61773245323">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.</p>
+<div class="note" id="apm_01_0005__en-us_topic_0000001240325091_note1581113382512"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="apm_01_0005__en-us_topic_0000001240325091_ul17581539132716"><li id="apm_01_0005__en-us_topic_0000001240325091_li7581939192712">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.</li><li id="apm_01_0005__en-us_topic_0000001240325091_li1795843172912">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.</li><li id="apm_01_0005__en-us_topic_0000001240325091_li28604818302">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.</li><li id="apm_01_0005__en-us_topic_0000001240325091_li66212286321">If the number of errors is greater than 0, the value turns red.</li></ul>
+</div></div>
+<div class="fignone" id="apm_01_0005__en-us_topic_0000001240325091_fig132997340565"><span class="figcap"><b>Figure 1 </b>Application topology</span><br><span><img id="apm_01_0005__en-us_topic_0000001240325091_image7544114217216" src="en-us_image_0000001196297610.png" title="Click to enlarge" class="imgResize"></span></div>
+</div>
+<div class="section" id="apm_01_0005__en-us_topic_0000001240325091_section20177124123214"><h4 class="sectiontitle">Tracing</h4><p id="apm_01_0005__en-us_topic_0000001240325091_p101771824173215">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.</p>
+</div>
+<div class="section" id="apm_01_0005__en-us_topic_0000001240325091_section517782414326"><h4 class="sectiontitle">APM Agent</h4><p id="apm_01_0005__en-us_topic_0000001240325091_p1457815120180">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 <a href="apm_01_0009.html#apm_01_0009">Data Collection</a>. Before using APM, ensure that APM Agents have been installed.</p>
+</div>
+<div class="section" id="apm_01_0005__en-us_topic_0000001240325091_section1178933417381"><h4 class="sectiontitle">URL Tracing</h4><p id="apm_01_0005__en-us_topic_0000001240325091_p8733175163212">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 &gt; web server &gt; database &gt; web server &gt; user request."</p>
+<p id="apm_01_0005__en-us_topic_0000001240325091_p1985842103619">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.</p>
+</div>
+<div class="section" id="apm_01_0005__en-us_topic_0000001240325091_section36775205019"><h4 class="sectiontitle">Apdex</h4><p id="apm_01_0005__en-us_topic_0000001240325091_p1311119291900">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.</p>
+<ul id="apm_01_0005__en-us_topic_0000001240325091_ul4111529507"><li id="apm_01_0005__en-us_topic_0000001240325091_li911132920017">Apdex principle</li></ul>
+<p id="apm_01_0005__en-us_topic_0000001240325091_p01111229408">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:</p>
+<p id="apm_01_0005__en-us_topic_0000001240325091_p19111629903">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.</p>
+<p id="apm_01_0005__en-us_topic_0000001240325091_p12111329903">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.</p>
+<p id="apm_01_0005__en-us_topic_0000001240325091_p13111529609">Frustrated: indicates that the actual response time is greater than "4T".</p>
+<p id="apm_01_0005__en-us_topic_0000001240325091_p996685814112"><span><img id="apm_01_0005__en-us_topic_0000001240325091_image1796619587119" src="en-us_image_0000001470571029.png" title="Click to enlarge" class="imgResize"></span></p>
+<ul id="apm_01_0005__en-us_topic_0000001240325091_u54a25ba7f7e14c82bfeafea0b9542326"><li id="apm_01_0005__en-us_topic_0000001240325091_lcb51cdb40a5145a89547372b5510bd20">Apdex calculation<p id="apm_01_0005__en-us_topic_0000001240325091_p175737195817"><a name="apm_01_0005__en-us_topic_0000001240325091_lcb51cdb40a5145a89547372b5510bd20"></a><a name="en-us_topic_0000001240325091_lcb51cdb40a5145a89547372b5510bd20"></a>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:</p>
+<p id="apm_01_0005__en-us_topic_0000001240325091_abec33f3a317f41309e045b8b17da695f">Apdex = (Number of satisfied samples + Number of tolerable samples x 0.5)/Total number of samples</p>
+</li></ul>
+</div>
+<div class="section" id="apm_01_0005__en-us_topic_0000001240325091_section9978123211385"><h4 class="sectiontitle">CMDB</h4><p id="apm_01_0005__en-us_topic_0000001240325091_p8060118">Configuration Management Database (CMDB) structures and displays application resource configuration, so that you can better monitor and manage applications. It consists of:</p>
+<ul id="apm_01_0005__en-us_topic_0000001240325091_ul383211528436"><li id="apm_01_0005__en-us_topic_0000001240325091_li178321252164318"><strong id="apm_01_0005__en-us_topic_0000001240325091_b147191727265">Application</strong> (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.</li><li id="apm_01_0005__en-us_topic_0000001240325091_li1665717446596"><strong id="apm_01_0005__en-us_topic_0000001240325091_b126826161014">Sub-application</strong> (global concept): similar to a folder. You can create up to three layers of sub-applications under an application.</li><li id="apm_01_0005__en-us_topic_0000001240325091_li137561421104610"><strong id="apm_01_0005__en-us_topic_0000001240325091_b419733815427">Component</strong> (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.</li><li id="apm_01_0005__en-us_topic_0000001240325091_li13153278466"><strong id="apm_01_0005__en-us_topic_0000001240325091_b16641144755813">Environment</strong>: 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.</li><li id="apm_01_0005__en-us_topic_0000001240325091_li20832155224312"><strong id="apm_01_0005__en-us_topic_0000001240325091_b6745239567">Instance</strong>: 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.</li><li id="apm_01_0005__en-us_topic_0000001240325091_li14833175224314"><strong id="apm_01_0005__en-us_topic_0000001240325091_b183916421962">Environment tag</strong>: 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.</li></ul>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0001.html">Service Overview</a></div>
+</div>
+</div>
+
+
+<script language="JavaScript">
+<!--
+image_size('.imgResize');
+var msg_imageMax = "view original image";
+var msg_imageClose = "close";
+//--></script>

docs/apm/umn/apm_01_0006.html

@@ -0,0 +1,91 @@
+<a name="apm_01_0006"></a><a name="apm_01_0006"></a>
+
+<h1 class="topictitle1">Edition Differences</h1>
+<div id="body8662426"><p id="apm_01_0006__en-us_topic_0000001214780600_p3614104624614">APM provides basic and enterprise editions and supports interconnection with Java applications. The following table lists the functions supported by each edition.</p>
+
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="apm_01_0006__en-us_topic_0000001214780600_table145191551298" frame="border" border="1" rules="all"><thead align="left"><tr id="apm_01_0006__en-us_topic_0000001214780600_row155491558292"><th align="left" class="cellrowborder" valign="top" width="28.01%" id="mcps1.3.2.1.4.1.1"><p id="apm_01_0006__en-us_topic_0000001214780600_p16554165102919">Edition</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="40.38%" id="mcps1.3.2.1.4.1.2"><p id="apm_01_0006__en-us_topic_0000001214780600_p1955910514291">Free</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="31.61%" id="mcps1.3.2.1.4.1.3"><p id="apm_01_0006__en-us_topic_0000001214780600_p1656955132911">Enterprise</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="apm_01_0006__en-us_topic_0000001214780600_row119279582918"><td class="cellrowborder" valign="top" width="28.01%" headers="mcps1.3.2.1.4.1.1 "><p id="apm_01_0006__en-us_topic_0000001214780600_p14905342136">Description</p>
+</td>
+<td class="cellrowborder" valign="top" width="40.38%" headers="mcps1.3.2.1.4.1.2 "><p id="apm_01_0006__en-us_topic_0000001214780600_p7662183324816">Free of charge. Up to 10 Agents can be connected. Reactivate them every 15 days.</p>
+</td>
+<td class="cellrowborder" valign="top" width="31.61%" headers="mcps1.3.2.1.4.1.3 "><p id="apm_01_0006__en-us_topic_0000001214780600_p995055132912">All functions are open.</p>
+</td>
+</tr>
+<tr id="apm_01_0006__en-us_topic_0000001214780600_row295918512295"><td class="cellrowborder" valign="top" width="28.01%" headers="mcps1.3.2.1.4.1.1 "><p id="apm_01_0006__en-us_topic_0000001214780600_p59624519296">Data storage duration</p>
+</td>
+<td class="cellrowborder" valign="top" width="40.38%" headers="mcps1.3.2.1.4.1.2 "><p id="apm_01_0006__en-us_topic_0000001214780600_p4966155122918">7 days</p>
+</td>
+<td class="cellrowborder" valign="top" width="31.61%" headers="mcps1.3.2.1.4.1.3 "><p id="apm_01_0006__en-us_topic_0000001214780600_p129751514295">30 days</p>
+</td>
+</tr>
+<tr id="apm_01_0006__en-us_topic_0000001214780600_row1098111519295"><td class="cellrowborder" valign="top" width="28.01%" headers="mcps1.3.2.1.4.1.1 "><p id="apm_01_0006__en-us_topic_0000001214780600_p1698616512918">Application topology</p>
+</td>
+<td class="cellrowborder" valign="top" width="40.38%" headers="mcps1.3.2.1.4.1.2 "><p id="apm_01_0006__en-us_topic_0000001214780600_p2993155132916">√</p>
+</td>
+<td class="cellrowborder" valign="top" width="31.61%" headers="mcps1.3.2.1.4.1.3 "><p id="apm_01_0006__en-us_topic_0000001214780600_p16813672915">√</p>
+</td>
+</tr>
+<tr id="apm_01_0006__en-us_topic_0000001214780600_row13196617295"><td class="cellrowborder" valign="top" width="28.01%" headers="mcps1.3.2.1.4.1.1 "><p id="apm_01_0006__en-us_topic_0000001214780600_p16242672910">Tracing</p>
+</td>
+<td class="cellrowborder" valign="top" width="40.38%" headers="mcps1.3.2.1.4.1.2 "><p id="apm_01_0006__en-us_topic_0000001214780600_p18307612911">√</p>
+</td>
+<td class="cellrowborder" valign="top" width="31.61%" headers="mcps1.3.2.1.4.1.3 "><p id="apm_01_0006__en-us_topic_0000001214780600_p845156182915">√</p>
+</td>
+</tr>
+<tr id="apm_01_0006__en-us_topic_0000001214780600_row478534812116"><td class="cellrowborder" valign="top" width="28.01%" headers="mcps1.3.2.1.4.1.1 "><p id="apm_01_0006__en-us_topic_0000001214780600_p1778510481411">Cross-region tracing</p>
+</td>
+<td class="cellrowborder" valign="top" width="40.38%" headers="mcps1.3.2.1.4.1.2 "><p id="apm_01_0006__en-us_topic_0000001214780600_p137311865218">√</p>
+</td>
+<td class="cellrowborder" valign="top" width="31.61%" headers="mcps1.3.2.1.4.1.3 "><p id="apm_01_0006__en-us_topic_0000001214780600_p2731561424">√</p>
+</td>
+</tr>
+<tr id="apm_01_0006__en-us_topic_0000001214780600_row778110835811"><td class="cellrowborder" valign="top" width="28.01%" headers="mcps1.3.2.1.4.1.1 "><p id="apm_01_0006__en-us_topic_0000001214780600_p2078213885812">Metric monitoring</p>
+</td>
+<td class="cellrowborder" valign="top" width="40.38%" headers="mcps1.3.2.1.4.1.2 "><p id="apm_01_0006__en-us_topic_0000001214780600_p10241155045817">√</p>
+</td>
+<td class="cellrowborder" valign="top" width="31.61%" headers="mcps1.3.2.1.4.1.3 "><p id="apm_01_0006__en-us_topic_0000001214780600_p1424255014582">√</p>
+</td>
+</tr>
+<tr id="apm_01_0006__en-us_topic_0000001214780600_row155818632920"><td class="cellrowborder" valign="top" width="28.01%" headers="mcps1.3.2.1.4.1.1 "><p id="apm_01_0006__en-us_topic_0000001214780600_p56510614293">URL tracing analysis</p>
+</td>
+<td class="cellrowborder" valign="top" width="40.38%" headers="mcps1.3.2.1.4.1.2 "><p id="apm_01_0006__en-us_topic_0000001214780600_p16701265298">√</p>
+</td>
+<td class="cellrowborder" valign="top" width="31.61%" headers="mcps1.3.2.1.4.1.3 "><p id="apm_01_0006__en-us_topic_0000001214780600_p38416662910">√</p>
+</td>
+</tr>
+<tr id="apm_01_0006__en-us_topic_0000001214780600_row61341267294"><td class="cellrowborder" valign="top" width="28.01%" headers="mcps1.3.2.1.4.1.1 "><p id="apm_01_0006__en-us_topic_0000001214780600_p17140196112910">Alarm</p>
+</td>
+<td class="cellrowborder" valign="top" width="40.38%" headers="mcps1.3.2.1.4.1.2 "><p id="apm_01_0006__en-us_topic_0000001214780600_p141481569296">√</p>
+</td>
+<td class="cellrowborder" valign="top" width="31.61%" headers="mcps1.3.2.1.4.1.3 "><p id="apm_01_0006__en-us_topic_0000001214780600_p1915815615296">√</p>
+</td>
+</tr>
+<tr id="apm_01_0006__en-us_topic_0000001214780600_row14206567295"><td class="cellrowborder" valign="top" width="28.01%" headers="mcps1.3.2.1.4.1.1 "><p id="apm_01_0006__en-us_topic_0000001214780600_p19211569294">CMDB</p>
+</td>
+<td class="cellrowborder" valign="top" width="40.38%" headers="mcps1.3.2.1.4.1.2 "><p id="apm_01_0006__en-us_topic_0000001214780600_p1321813622915">√</p>
+</td>
+<td class="cellrowborder" valign="top" width="31.61%" headers="mcps1.3.2.1.4.1.3 "><p id="apm_01_0006__en-us_topic_0000001214780600_p1522720672919">√</p>
+</td>
+</tr>
+<tr id="apm_01_0006__en-us_topic_0000001214780600_row6289160292"><td class="cellrowborder" colspan="3" valign="top" headers="mcps1.3.2.1.4.1.1 mcps1.3.2.1.4.1.2 mcps1.3.2.1.4.1.3 "><p id="apm_01_0006__en-us_topic_0000001214780600_p1229317692915">Note: <strong id="apm_01_0006__en-us_topic_0000001214780600_b11324172211153">√</strong> indicates supported, and <strong id="apm_01_0006__en-us_topic_0000001214780600_b18330102251512">x</strong> indicates not supported.</p>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="note" id="apm_01_0006__en-us_topic_0000001214780600_note1655317110448"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="apm_01_0006__en-us_topic_0000001214780600_p855391194414">The enterprise edition cannot be downgraded back to the free edition (basic edition).</p>
+</div></div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0001.html">Service Overview</a></div>
+</div>
+</div>
+

docs/apm/umn/apm_01_0008.html

@@ -0,0 +1,11 @@
+<a name="apm_01_0008"></a><a name="apm_01_0008"></a>
+
+<h1 class="topictitle1">Privacy and Sensitive Information Protection Statement</h1>
+<div id="body8662426"><p id="apm_01_0008__en-us_topic_0000001240565041_p169792472518">All O&amp;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.</p>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0001.html">Service Overview</a></div>
+</div>
+</div>
+

docs/apm/umn/apm_01_0010.html

@@ -0,0 +1,15 @@
+<a name="apm_01_0010"></a><a name="apm_01_0010"></a>
+
+<h1 class="topictitle1">Usage Restrictions</h1>
+<div id="body8662426"></div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="apm_01_0094.html">Java</a></strong><br>
+</li>
+</ul>
+
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0001.html">Service Overview</a></div>
+</div>
+</div>
+

docs/apm/umn/apm_01_0013.html

@@ -0,0 +1,40 @@
+<a name="apm_01_0013"></a><a name="apm_01_0013"></a>
+
+<h1 class="topictitle1">Metric Overview</h1>
+<div id="body8662426"><p id="apm_01_0013__en-us_topic_0000001537318145_p8060118">A metric describes resource performance data or status. It consists of the metric type, name, and description, data type, and default aggregation mode.</p>
+<div class="note" id="apm_01_0013__en-us_topic_0000001537318145_note4481205163916"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="apm_01_0013__en-us_topic_0000001537318145_p10482145114397">For the default aggregation mode, <strong id="apm_01_0013__en-us_topic_0000001537318145_b079719565402">LAST</strong> indicates the value of the latest metric collected. <strong id="apm_01_0013__en-us_topic_0000001537318145_b10825182520419">SUM</strong> indicates the sum of collected metrics. <strong id="apm_01_0013__en-us_topic_0000001537318145_b2528932134110">MAX</strong> indicates the maximum value of collected metrics. <strong id="apm_01_0013__en-us_topic_0000001537318145_b75486381415">AVG</strong> indicates the average value of collected metrics.</p>
+</div></div>
+</div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="apm_01_0015.html">Exception</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0016.html">Basic Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0017.html">Databases</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0018.html">URLs</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0019.html">External Calls</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0020.html">Cache</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0021.html">Agent Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0022.html">Tomcat Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0023.html">Message Queues</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0024.html">RPC</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0025.html">IoT</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0026.html">Communication Protocol</a></strong><br>
+</li>
+</ul>
+
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0001.html">Service Overview</a></div>
+</div>
+</div>
+

docs/apm/umn/apm_01_0016.html

@@ -0,0 +1,26 @@
+<a name="apm_01_0016"></a><a name="apm_01_0016"></a>
+
+<h1 class="topictitle1">Basic Monitoring</h1>
+<div id="body8662426"><p id="apm_01_0016__en-us_topic_0000001536878349_p1525510267506">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.</p>
+</div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="apm_01_0027.html">GC Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0028.html">JavaMethod</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0029.html">JVM Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0030.html">JVMInfo</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0031.html">Netty Memory</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0032.html">Threads</a></strong><br>
+</li>
+</ul>
+
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0013.html">Metric Overview</a></div>
+</div>
+</div>
+

docs/apm/umn/apm_01_0017.html

@@ -0,0 +1,44 @@
+<a name="apm_01_0017"></a><a name="apm_01_0017"></a>
+
+<h1 class="topictitle1">Databases</h1>
+<div id="body8662426"><p id="apm_01_0017__en-us_topic_0000001537038233_p8060118">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.</p>
+</div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="apm_01_0033.html">C3P0 Connection Pool Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0034.html">Cassandra Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0035.html">ClickHouse Database</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0036.html">DBCP Connection Pool Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0037.html">Druid Connection Pool Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0038.html">EsRestClient Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0039.html">GaussDB Database</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0040.html">HBase Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0041.html">Hikari Connection Pool Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0042.html">Jetcd Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0043.html">MongoDB Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0044.html">MySQL Database</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0045.html">ObsClient Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0046.html">Oracle Database</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0047.html">PostgreSQL Database</a></strong><br>
+</li>
+</ul>
+
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0013.html">Metric Overview</a></div>
+</div>
+</div>
+

docs/apm/umn/apm_01_0018.html

@@ -0,0 +1,22 @@
+<a name="apm_01_0018"></a><a name="apm_01_0018"></a>
+
+<h1 class="topictitle1">URLs</h1>
+<div id="body8662426"><p id="apm_01_0018__en-us_topic_0000001537158329_p8060118">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.</p>
+</div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="apm_01_0048.html">CSEProvider Cluster Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0049.html">DubboProvider Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0050.html">FunctionGraph Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0052.html">URL Monitoring</a></strong><br>
+</li>
+</ul>
+
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0013.html">Metric Overview</a></div>
+</div>
+</div>
+

docs/apm/umn/apm_01_0019.html

@@ -0,0 +1,24 @@
+<a name="apm_01_0019"></a><a name="apm_01_0019"></a>
+
+<h1 class="topictitle1">External Calls</h1>
+<div id="body8662426"><p id="apm_01_0019__en-us_topic_0000001486158224_p8060118">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.</p>
+</div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="apm_01_0053.html">ApacheHttpAsyncClient Connection Pool</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0054.html">ApacheHttpClient Connection Pool</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0055.html">CSEConsumer Cluster Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0056.html">DubboConsumer Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0051.html">HttpClient Monitoring</a></strong><br>
+</li>
+</ul>
+
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0013.html">Metric Overview</a></div>
+</div>
+</div>
+

docs/apm/umn/apm_01_0020.html

@@ -0,0 +1,20 @@
+<a name="apm_01_0020"></a><a name="apm_01_0020"></a>
+
+<h1 class="topictitle1">Cache</h1>
+<div id="body8662426"><p id="apm_01_0020__en-us_topic_0000001486318164_p82449313156">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.</p>
+</div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="apm_01_0057.html">Redis Method Call</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0058.html">Jedis Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0059.html">Lettuce Client</a></strong><br>
+</li>
+</ul>
+
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0013.html">Metric Overview</a></div>
+</div>
+</div>
+

docs/apm/umn/apm_01_0023.html

@@ -0,0 +1,28 @@
+<a name="apm_01_0023"></a><a name="apm_01_0023"></a>
+
+<h1 class="topictitle1">Message Queues</h1>
+<div id="body8662426"><p id="apm_01_0023__en-us_topic_0000001485998332_p8060118">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.</p>
+</div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="apm_01_0061.html">KafkaConsumer Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0062.html">KafkaProducer Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0063.html">RabbitMqCommon Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0064.html">RabbitMqConsumer Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0065.html">RabbitMqProducer Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0066.html">RocketMqConsumer Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0067.html">RocketMqProducer Monitoring</a></strong><br>
+</li>
+</ul>
+
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0013.html">Metric Overview</a></div>
+</div>
+</div>
+

docs/apm/umn/apm_01_0024.html

@@ -0,0 +1,18 @@
+<a name="apm_01_0024"></a><a name="apm_01_0024"></a>
+
+<h1 class="topictitle1">RPC</h1>
+<div id="body8662426"><p id="apm_01_0024__en-us_topic_0000001536878353_p8060118">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.</p>
+</div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="apm_01_0068.html">GRPCClient Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0069.html">GRPCServer Monitoring</a></strong><br>
+</li>
+</ul>
+
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0013.html">Metric Overview</a></div>
+</div>
+</div>
+

docs/apm/umn/apm_01_0025.html

@@ -0,0 +1,24 @@
+<a name="apm_01_0025"></a><a name="apm_01_0025"></a>
+
+<h1 class="topictitle1">IoT</h1>
+<div id="body8662426"><p id="apm_01_0025__en-us_topic_0000001537038237_p1075712719227">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.</p>
+</div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="apm_01_0070.html">CoapClient Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0071.html">CoapServer Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0072.html">MoquetteBroker Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0073.html">PahoPublisher Monitoring</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="apm_01_0074.html">PahoSubscriber Monitoring</a></strong><br>
+</li>
+</ul>
+
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="apm_01_0013.html">Metric Overview</a></div>
+</div>
+</div>
+