The Unified Full-Stack Observability Data Integration Center (Integration Center) of Application Real-Time Monitoring Service (ARMS) provides out-of-the-box observability capabilities for most monitoring targets in the cloud, including infrastructure, server-side applications, frontend applications, databases, middleware, AI services, and big data platforms. Each integration bundles metric collection, data visualization, and alerting for a specific target.
To open the Integration Center, log on to the Managed Service for Prometheus console and click Integration Center in the left-side navigation pane.
Key concepts
Environments
An environment defines where and how metric data is collected. By default, each environment is associated with a Prometheus instance that stores the collected metrics.
| Environment type | Description | Typical use |
|---|---|---|
| Container | Monitors containers with automatic trace management to help you intelligently install agents and process data. | Kubernetes clusters, Docker containers |
| VPC | Pulls Elastic Compute Service (ECS) instance data through virtual private clouds (VPCs). We recommend that you configure a separate environment for each VPC. ARMS collects data through VPCs first to minimize the number of agents installed in ECS instances. | Self-managed services on ECS |
| Cloud service | Integrates the monitoring data of an Alibaba Cloud service. One cloud service environment per region. | Managed cloud services (RDS, SLB, OSS, and others) |
For ARMS sub-services such as Application Monitoring and Managed Service for OpenTelemetry, not all metric data can be stored in the associated Prometheus instance.
Components
A component is a pre-built integration that monitors a specific infrastructure target or service. Each component handles metric collection, data visualization, and alerting.
Supported integrations
The following sections list all available components grouped by category. The environment type columns show which deployment models each component supports.
Infrastructure
Server-side applications
Tracing
Tracing components support one or more protocols. The table below shows supported protocols for each language and framework.
| Component | References | OpenTelemetry | SkyWalking | Zipkin | Jaeger |
|---|---|---|---|---|---|
| Java Tracing Analysis | Monitor Java applications | Yes | Yes | Yes | Yes |
| Go Tracing Analysis | Monitor Go applications | Yes | Yes | Yes | Yes |
| LLM Application Tracing for DashScope | Integrate services or components | Yes | - | - | - |
| LangChain Tracing Analysis | Integrate services or components | Yes | - | - | - |
| LlamaIndex Tracing Analysis | Integrate services or components | Yes | - | - | - |
| OpenAI Tracing Analysis | Integrate services or components | Yes | - | - | - |
| Python Tracing Analysis | Monitor Python applications | Yes | Yes | - | Yes |
| PHP Tracing Analysis | Monitor PHP applications | Yes | - | - | - |
| Node.js Tracing Analysis | Monitor Node.js applications | Yes | Yes | - | Yes |
| C++ Tracing Analysis | Monitor C++ applications | Yes | - | - | Yes |
| .NET Tracing Analysis | Monitor .NET applications | Yes | Yes | - | - |
| Rust Tracing Analysis | Monitor Rust applications | - | Yes | - | - |
| Ruby Tracing Analysis | Monitor Ruby applications | Yes | - | - | - |
| OpenTelemetry | Integrate services or components | Yes | - | - | - |
| SkyWalking | Integrate services or components | - | Yes | - | - |
| Jaeger | Integrate services or components | - | - | - | Yes |
| Zipkin | Integrate services or components | - | - | Yes | - |
Application monitoring
| Component | References | Container | VPC | Cloud service |
|---|---|---|---|---|
| Java Application Monitor | Monitor Java applications | Yes (manual) | - | - |
| eBPF Application Monitor | Manually integrate an application in an ACK cluster to Application Monitoring eBPF Edition | Yes | - | - |
Frontend applications
| Component | References |
|---|---|
| Android | Integrate an Android app |
| iOS | Integrate an iOS app into RUM |
| Web & H5 | Integrate a web or HTML5 application |
| Mini APP | Integrate a mini program |
Databases
Middleware
AI
| Component | References | Container | VPC | Cloud service |
|---|---|---|---|---|
| Kubernetes GPU | Monitor GPU resources in a Kubernetes cluster | Yes | Yes | - |
| Alibaba Cloud FC | Monitor an Alibaba Cloud service | - | - | Yes |
| Aliyun PAI-EAS | Monitor an Alibaba Cloud service | - | - | Yes |
| Alibaba Cloud PAI-Interactive Modeling (DSW) | Monitor an Alibaba Cloud service | - | - | Yes |
| Aliyun PAI-Quota | Monitor an Alibaba Cloud service | - | - | Yes |
| Aliyun PAI-DLC | Monitor an Alibaba Cloud service | - | - | Yes |
| Alibaba Cloud PAI EAS Resource Group | Monitor an Alibaba Cloud service | - | - | Yes |
| Alibaba Cloud Intelligence Compute Eflo | Monitor an Alibaba Cloud service | - | - | Yes |
| Ray | Use Integration Center to integrate monitoring data | Yes | - | - |
| Fluid | Enable Managed Service for Prometheus for Fluid | Yes | - | - |
Big data
| Component | References | Container | VPC | Cloud service |
|---|---|---|---|---|
| Alibaba Cloud E-MapReduce | Monitor an Alibaba Cloud service | - | - | Yes |
| Aliyun Elasticsearch Cloud Monitoring | Monitor an Elasticsearch instance | - | - | Yes |
| Alibaba Cloud HBase | Monitor an Alibaba Cloud service | - | - | Yes |
| Aliyun Hologres (Legacy) | Monitor an Alibaba Cloud service | - | - | Yes |
| Alibaba Cloud Logstash | Monitor an Alibaba Cloud service | - | - | Yes |
| Alibaba Cloud MaxCompute Service | Monitor an Alibaba Cloud service | - | - | Yes |
| Aliyun Hologres (Follower Instance) Real-time Warehouse Monitoring | Monitor an Alibaba Cloud service | - | - | Yes |
| Aliyun Hologres (Lakehouse Acceleration) | Monitor an Alibaba Cloud service | - | - | Yes |
| Cloud Native Hologres (Computing Cluster) | Monitor an Alibaba Cloud service | - | - | Yes |
| Aliyun Hologres (Universal) | Monitor an Alibaba Cloud service | - | - | Yes |
| Fluid | Enable Managed Service for Prometheus for Fluid | Yes | - | - |