Integrate applications and components with ARMS through the Integration Center or individual sub-service consoles.
Integration Center
The Integration Center is the unified entry point for ARMS. It supports 100+ component integrations across Application Monitoring, Managed Service for OpenTelemetry, Browser Monitoring, container monitoring, MySQL, Kafka, and other Alibaba Cloud services.
Services are organized into six categories: Infrastructure (11), Server-side Application (16), Front-end Application (20), Database (18), Middleware (36), and Artificial Intelligence (4). Use the search bar to find specific services.
The following example demonstrates how to integrate MySQL through the Integration Center.
Integrate a self-managed MySQL instance
Integration steps vary by deployment environment.
ACK environment
Log on to the ARMS console.
-
In the left-side navigation pane, click Access Center. In the Database section, click the MySQL card.
-
On the Start Integration tab, select Container Service Environment.
-
Select the Container Service for Kubernetes (ACK) cluster where your MySQL instance is deployed.
-
In the Configuration Information section, configure the required parameters, and then click OK.
Parameter
Description
MySQL instance endpoint
Endpoint of the MySQL instance in the ACK cluster.
MySQL instance port
Port of the MySQL instance. Example: 3306.
MySQL account
Username and password of the MySQL account.
ImportantTo avoid security risks, do not use an administrator account. Instead, create a dedicated MySQL account for
mysqld_exporterand grant it only the minimum required permissions. Create a MySQL access account for Prometheus.MySQL password
-
After installation, view your integrated applications and components on the Integration Management page.
Click a cluster name to view basic information, integrated components, and collected metrics. You can also explore metrics and configure agents.
ECS environment
Log on to the ARMS console.
-
In the left-side navigation pane, click Access Center. In the Database section, click the MySQL card.
-
On the Start Integration tab, select ECS (VPC).
-
Select the ECS instance where your MySQL instance is deployed.
-
In the Configuration Information section, configure the required parameters, and then click OK.
Parameter
Description
MySQL instance endpoint
Endpoint of the MySQL instance on the ECS instance.
MySQL instance port
Port of the MySQL instance. Example: 3306.
MySQL account
Username and password of the MySQL account.
ImportantTo avoid security risks, do not use an administrator account. Instead, create a dedicated MySQL account for
mysqld_exporterand grant it only the minimum required permissions. Create a MySQL access account for Prometheus.MySQL password
-
After installation, view your integrated clusters or components on the Integration Management page.
Click a cluster name to view basic information, integrated components, and collected metrics. You can also explore metrics and configure agents.
Integrate an ApsaraDB RDS instance
Method 1:
Log on to the ARMS console.
-
In the left-side navigation pane, click Access Center. In the Database section, click the MySQL card.
-
On the Start Integration tab, select Container Service Environment.
Method 2:
Log on to the ARMS console.
-
In the left-side navigation pane, click Access Center. In the Database section, click the ApsaraDB RDS card.
Integrate the ApsaraDB RDS instance:
-
Select the region of the ApsaraDB RDS instance. ARMS integrates it automatically.
-
After integration, view your integrated applications and components on the Integration Management page.
Click a cluster name to view basic information, integrated components, and collected metrics. You can also explore metrics and configure agents.
Preview
On the Access Center page, you can preview monitoring dashboards, collected metrics, and alert rule templates for each component.
Preview
Click a component card, then click the Preview tab.
The Preview tab shows the MySQL Overview dashboard with metric cards (Uptime, Current QPS, InnoDB Buffer Pool Size) and time-series charts: MySQL Connections, MySQL Client Thread Activity, Table Locks, MySQL Questions, MySQL Thread Cache, MySQL Temporary Objects, MySQL Select Types, and Sorts.
Collected metrics
Click a component card, then click the Collected Metrics tab to view metrics ARMS collects for each environment.
Switch between Container Service Environment, ECS (VPC), and Cloud Service to view the corresponding metrics table with columns for metric name, description, group, type, and unit.
Alert rule templates
Click a component card, then click the Alert Rule Template tab to view alert rule templates for each environment.
For MySQL in a Container Service Environment, eight default alert rules are provided: MySQLNotReady, MySQLOutOfSync, MySQLDonorFallingBehind, MySQLReplicationNotRunning, MySQLReplicationLag, MySQLHeartbeatLag, MySQLInnoDBLogWaits, and MySQLDown. The list shows Severity, Alert Rule Name/ID, Alert Group, and Template columns. Most rules belong to the Common alert group, using variables such as {{$labels.job}}, {{$labels.instance}}, and {{$value}}.
Sub-service consoles
You can also integrate applications and components directly from each ARMS sub-service console.
|
ARMS sub-service |
Monitoring object |
Documentation |
|
Application Monitoring |
Java application |
|
|
Managed Service for OpenTelemetry |
Java application |
|
|
PHP application |
Report trace data from PHP applications through OpenTelemetry |
|
|
Go application |
|
|
|
Python application |
|
|
|
Node.js application |
|
|
|
.NET application |
|
|
|
C++ application |
|
|
|
Ruby application |
|
|
|
Swift application |
|
|
|
Android application |
|
|
|
Rust application |
|
|
|
Browser Monitoring |
Web & H5 |
|
|
Weex |
||
|
Mini program |
||
|
User Experience Monitoring |
Web & H5 |
|
|
Mini program |
||
|
App |
||
|
Managed Service for Prometheus |
Container Service for Kubernetes (ACK) |
|
|
Alibaba Cloud services, for example:
|
||
|
ECS host |
||
|
self-managed Kubernetes |
Monitor multi-cloud container clusters using Alibaba Cloud registered clusters and Prometheus |
|
|
custom metrics |
||
|
Application Security |
Application protection |
|
|
Synthetic Monitoring |
Website |
|
|
Application Monitoring eBPF Edition |
Kubernetes cluster |
|
|
Managed Service for Grafana |
Alibaba Cloud data source |
|
|
third-party data source |
What's next
After integration, you can create dashboards and configure alert rules based on the collected metrics. For more information, see Tutorials.