You need to enable JavaScript to run this app.
Application Performance Management Plus

Application Performance Management Plus

Copy page
Download PDF
Best practices
APMPlus end-to-end tracing
Copy page
Download PDF
APMPlus end-to-end tracing
APMPlus provides enterprise-level users with an end-to-end tracing solution covering clients such as apps, Web, and mini programs, as well as servers including Java, Go, and Python. With the distributed tracing technology, it enables full-process visualization and performance analysis of user behaviors, network requests, service calls, and dependent components such as databases and message queues. This helps enterprises quickly identify root causes of anomalies, optimize system performance, improve user experience, and support data-driven business decisions.​
Background​
APMPlus now fully supports end-to-end connectivity from user terminals to AI and middleware. The complete link includes: User terminals (e.g., Android/iOS/Web/mini programs) → Gateways (e.g., API Gateway/Ingress/Nginx) → Backend services (e.g., Java/Go/Python) → AI and middleware (e.g., Large Language Models, Databases, Caches, Message Queues).​
Prerequisites​
Before using the end-to-end tracing solution, ensure that the client SDK version meets the following requirements.​
​
SDK​
Version requirements​
Android SDK​
Use the Android SDK apm_insight version 1.5.16.cn or later.​
iOS SDK​
Use iOS SDK version 5.1.10 or later.​
WebPro SDK​
Use WebPro SDK version 2.10.0 or later.​
Mini Pro SDK​
Use Mini Pro SDK version 0.4.0 or later.​
​
Procedure​
Step 1: Integrate the client application​
Based on your actual requirements, select the appropriate client type and integrate your application with APMPlus client monitoring via SDK. The following 4 integration methods for client applications are provided:​
​
Android monitoring
iOS monitoring
WebPro Monitoring
Mini Pro Monitoring
​
  1. See the description in Integrating Android SDK to obtain the appropriate SDK package and initialize the SDK.​
  1. Add the following sample code to start the SDK and enable data collection and end-to-end monitoring.​
​
ApmInsightInitConfig.Builder builder = ApmInsightInitConfig.builder();​
// Controls whether network monitoring is enabled. To enable it, the apm-plugin add-on must be configured simultaneously.​
builder.netMonitor(true);​
// Controls whether end-to-end monitoring is enabled. The server-side APMPlus must be integrated simultaneously.​
builder.enableNetTrace(true);​
ApmInsight.getInstance().start(builder.build());​
​
  1. After integrating your application with the Android SDK, see the instructions in Verifying Data Reporting to verify data reporting.​
​
Step 2: Integrate the server-side application​
End-to-end tracing relies on the OpenTelemetry SDK that has been properly integrated with the server-side applications. The SDK can help identify HTTP requests from App, Web, or mini program clients and convert the relevant header fields into trace attributes to be reported to the APMPlus server. Integration methods vary by language. The following integration methods for 4 languages are provided; you can choose the appropriate one based on the language used by your server-side application.​
​
Java
Go
Python
Nodejs
​
  1. To integrate a Java application via OpenTelemetry, see the detailed instructions at Integrating Java applications.​
  1. Configure automatic injection based on different integration methods.​
  • If you install the apmplus-opentelemetry-collector add-on via the Addons in the VKE console, automatic injection is supported by default, and no configuration changes are required.​
  • If you integrate via the community-provided SDK or Agent, you need to add the following environment variables:​
​
OTEL_JAVA_EXPERIMENTAL_SPAN_ATTRIBUTES_COPY_FROM_BAGGAGE_INCLUDE:apmplus.app_id,apmplus.origin,apmplus.client_domain​
​
​
​
Step 3: End-to-end distributed tracing​
​
App end-to-end
Web end-to-end
Mini Pro end-to-end
​
After both the client applications (e.g., Android, iOS) and server-side applications are properly integrated, requests initiated from the clients will be sent to the server-side applications. You can go to the Trace details page of the APMPlus console to view the spans of client app requests, and you can also jump to the App monitoring page in client monitoring to view more information.​
  1. Log in to the APMPlus console. ​
  1. Search for the target service, click the service name, and go to the management page of the target service.​
  1. In the left navigation pane, select Trace analysis to go to the Trace analysis page.​
  1. Based on your actual requirements, filter target traces by conditions such as time, tags, Span attributes, Trace ID, Span type, and service name. Click the target TraceID to go to the Single trace details page.​
  1. Click Jump to mobile client to view in the target app request to navigate to the app page in Client monitoring for more information.​
Additionally, from the app page in Client monitoring, you can navigate back to the Trace details page of APMPlus.​
  1. Click the target application service name, and on the application management page, click Use service under App monitoring to go to the App monitoring page.​
  1. In the left navigation pane, select All functions > Network analysis > HTTP to go to the network overview page.​
  1. Select analysis metrics on the left and analysis dimensions on the right, then click Network details to go to the Log search page and view more detailed information.​
  1. In the details section of the Log search page, click the link under end-to-end Trace to jump to the server-side single trace query page to view more information.​
​
​
Last updated: 2026.08.12 17:19:16