You can integrate services or components into Application Real-Time Monitoring Service (ARMS) by using the integration center or instance details pages. This topic describes how to integrate services or components.
Integration center
As a unified access portal for ARMS, the integration center supports the integration and monitoring of more than 100 services or components, including Java applications, Managed Service for OpenTelemetry, Browser Monitoring, MySQL, Kafka, and various Alibaba Cloud services. By using the integration center, you can quickly preview available components and integrate components into ARMS based on your business requirements.
In this topic, the MySQL component is used to show how to integrate a service or component to ARMS and view metrics.
Integrate a self-managed MySQL instance
The operations required for integration vary with the environment.
ACK cluster
- Log on to the ARMS console.
In the left-side navigation pane, click Integration Center. In the Database section, click MySQL.
On the Start Integration tab in the panel that appears, select Container Service Environment as the environment type.
Select the Container Service for Kubernetes (ACK) cluster where the MySQL instance resides.
In the Configuration Information section, set the parameters and click OK.
Parameter
Description
Instance Endpoint
The endpoint of the MySQL instance.
Instance Port
The port number of the MySQL instance. Example: 3306.
Instance Account
The username and password of the MySQL instance.
ImportantWe recommend that you do not use an administrator account to avoid data breach risks. Create a MySQL account for mysqld_exporter and grant minimum permissions to the account. For more information, see Permissions required for mysqld_exporter to access a MySQL database.
Instance Password
After the MySQL component is installed, you can view all services and components that are integrated into ARMS on the Integration Management page.
On the Integration Management page, click a cluster name to view the basic information, integrated components, and metrics of the cluster. You can also explore metrics or configure the ARMS agent.
ECS instance
- Log on to the ARMS console.
In the left-side navigation pane, click Integration Center. In the Database section, click MySQL.
On the Start Integration tab in the panel that appears, select ECS (VPC) as the environment type.
Select the ECS instance where the MySQL instance resides.
In the Configuration Information section, set the parameters and click OK.
Parameter
Description
Instance Endpoint
The endpoint of the MySQL instance.
Instance Port
The port number of the MySQL instance. Example: 3306.
Instance Account
The username and password of the MySQL instance.
ImportantWe recommend that you do not use an administrator account to avoid data breach risks. Create a MySQL account for mysqld_exporter and grant minimum permissions to the account. For more information, see Permissions required for mysqld_exporter to access a MySQL database.
Instance Password
After the MySQL component is installed, you can view all services and components that are integrated into ARMS on the Integration Management page.
On the Integration Management page, click a VPC ID to view the basic information, integrated components, and metrics of the corresponding ECS instance. You can also explore metrics or configure the ARMS agent.
Integrate an ApsaraDB RDS for MySQL instance
Method 1:
- Log on to the ARMS console.
In the left-side navigation pane, click Integration Center. In the Database section, click MySQL.
On the Start Integration tab in the panel that appears, select Cloud Services as the environment type.
Method 2:
- Log on to the ARMS console.
In the left-side navigation pane, click Integration Center. In the Database section, click ApsaraDB RDS.
Integrate an ApsaraDB RDS for MySQL instance:
Select the region where the ApsaraDB RDS for MySQL instance resides. ARMS will automatically install the instance.
After the ApsaraDB RDS component is installed, you can view all services and components that are integrated into ARMS on the Integration Management page.
On the Integration Management page, click the ApsaraDB RDS component to view the basic information and metrics of the RDS instance. You can also explore metrics or configure the ARMS agent.
Preview the result
On the Integration Center page, you can preview all services and components, and view the collected metrics and alert rule templates.
Preview
On the Integration Center page, click a service or component. In the panel that appears, click the Preview tab.
Collect Metrics
On the Integration Center page, click a service or component. In the panel that appears, click the Collect Metrics tab to view metrics of different environments.
Alert Rule Template
On the Integration Center page, click a service or component. In the panel that appears, click the Alert Rule Template tab to view alert rule templates of different environments.
Use the console of each ARMS sub-service
In addition to the integration center of the ARMS console, you can also integrate services and components in the console of each ARMS sub-service.
Backend applications
ARMS sub-service | Language | References |
Application Monitoring | Java | |
Managed Service for OpenTelemetry | Java | |
PHP | Use OpenTelemetry to report the trace data of PHP applications | |
Go | ||
Python | ||
Node.js | ||
.NET | ||
C++ | ||
Ruby | Use OpenTelemetry to submit the trace data of Ruby applications | |
Swift | Use OpenTelemetry to submit the trace data of Swift applications | |
Android | Use OpenTelemetry to report the trace data of Android applications | |
Rust | Use SkyWalking to submit the trace data of Rust applications |
Frontend, mobile, and client applications
Scenario | References |
Web & H5 | |
Weex | |
DingTalk mini program | |
WeChat mini program | |
Alipay mini program | |
OpenTelemetry for iOS | Use OpenTelemetry to submit the trace data of Swift applications |
OpenTelemetry for Android | Use OpenTelemetry to report the trace data of Android applications |
Application components
Runtime environments
Environment | References |
ACK cluster | |
ECS instance (VPC) |
Cloud services
Service | References |
AnalyticDB | |
API Gateway | |
ApsaraDB for HBase | |
Network Load Balancer (NLB) | |
AnalyticDB for PostgreSQL | |
Function Compute | |
Graph Database | |
VPN Gateway | |
ApsaraDB for OceanBase | |
Anti-DDoS | |
Anti-DDoS Pro | |
Anti-DDoS Premium | |
Alibaba Cloud ECS | |
ApsaraDB for Redis | |
ApsaraDB RDS for MySQL | |
ApsaraDB RDS for SQL Server | |
ApsaraDB RDS for PostgreSQL | |
Object Storage Service (OSS) | |
NAT Gateway | |
Server Load Balancer (SLB) | |
Application Load Balancer (ALB) | |
Elastic IP Address (EIP) | |
Elasticsearch | |
PolarDB for Xscale | |
PolarDB | |
Logstash | |
E-MapReduce (EMR) | |
Data Transmission Service (DTS) | |
Hologres | |
Cloud Enterprise Network (CEN) | |
Alibaba Cloud Connector | |
Alibaba Cloud CDN | |
Dynamic Route for CDN | |
Web Application Firewall (WAF) | |
Simple Log Service | |
Machine Learning Platform for AI - Elastic Algorithm Service (EAS) | |
Internet Shared Bandwidth | |
Serverless App Engine (SAE) | |
Microservices Engine | |
ApsaraMQ for RocketMQ | |
Lindorm | |
ApsaraMQ for Kafka | |
ApsaraDB for ClickHouse | |
ApsaraMQ for RabbitMQ | |
ApsaraDB for MongoDB instance | |
TSDB for InfluxDB connector | |
Cloud-native gateways of Microservices Engine (MSE) | |
Enterprise Distributed Application Service (EDAS) | |
Application High Availability Service (AHAS) | |
Performance Testing (PTS) | |
Intelligent Computing LINGJUN |
Open source monitoring systems
References
After you integrate a service or component to ARMS, you can create dashboards and alert rules for the metrics. For more information, see Best practices.