Alibaba Cloud Network Analysis and Monitoring integrates with Managed Service for OpenTelemetry to provide comprehensive end-to-end tracing capabilities. This integration enables seamless connection between detection data and backend traces, preserving key information such as nodes traversed by requests, call stacks, and response times. This helps you quickly locate issues and improve diagnostic efficiency.
Background information
Tracing provides developers of distributed applications with tools for complete trace restoration, request volume statistics, trace topology, and application dependency analysis. These tools help developers quickly analyze and diagnose performance bottlenecks in distributed application architectures.
Network Analysis and Monitoring supports tracing. By enabling the tracing feature, you can integrate detection requests with Alibaba Cloud Managed Service for OpenTelemetry. For more information, see What is Managed Service for OpenTelemetry.
Trace data records the processing information about each request, including service calls and response time.
Each trace contains an entry of trace data. In most cases, a trace represents the execution of a transaction or process in a distributed system. A trace is a directed acyclic graph (DAG) composed of multiple spans, where each span represents a named and timed continuous execution segment in the trace. For more information about traces, see Terms.
Billing
Network Analysis and Monitoring does not charge for tracing. If you enable Managed Service for OpenTelemetry, Managed Service for OpenTelemetry charges you based on your usage.
Operation guide
In Network Analysis and Monitoring, you can enable tracing only when you create a site monitoring (scheduled detection) task with the detection point type set to PC or Mobile and the protocol type set to HTTP(S). To enable tracing, you need to confirm the region for trace data reporting and the tracing protocol. Network Analysis and Monitoring has integrated OpenTelemetry W3C, Zipkin B3, and Jaeger protocols.
The following table lists the regions in which tracing is supported by Network Analysis and Monitoring.
Area | Region |
China | China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), and China (Hong Kong) |
Asia Pacific | Singapore, Malaysia (Kuala Lumpur), Japan (Tokyo), and Indonesia (Jakarta) |
Europe & Americas | UK (London), Germany (Frankfurt), US (Virginia), and US (Silicon Valley) |
To connect detection data with backend data, you need to match the region and protocol for detection data reporting with the region and protocol for backend data reporting. The following table lists the tracing protocols supported by different types of backend components.
Category | Component | Integration guide | Supported protocols |
Gateway | MSE | W3C, B3, and SkyWalking | |
ACK Ingress | W3C, B3, and Jaeger | ||
ALB | B3 | ||
ASM | W3C and B3 | ||
API Gateway | B3 | ||
Backend applications | Java, Go, and Python (self-developed) | W3C, B3, Jaeger, SkyWalking, and EagleEye | |
.NET, Node.js, and other multi-language applications (open source) | W3C, B3, Jaeger, SkyWalking | ||
Cloud Service | Alibaba Cloud Model Studio | W3C | |
Dependent components | More than 100 components are supported, covering various types including remote procedure call (RPC), message queues, databases, and task scheduling. | ||
View traces
On the detection records list page of your site monitoring task, click Details in the Actions column of the detection record.
Select the End-to-end Calls tab to view the trace corresponding to the detection request. Click the trace to view the detailed backend trace for the detection request. For more information about trace data, see Analyze traces.