Integrate Tair (Redis OSS-compatible)-Cloud Monitor(CMS)-阿里云帮助中心

Prerequisites

To integrate metrics, you must activate Prometheus Service and Hybrid Cloud Monitoring.
Only Community or Enterprise (Performance-enhanced) instances running Redis 4.0 or later with the latest minor version are supported.

Limitations

If you use a RAM user to set up the integration, grant the AliyunCloudMonitorFullAccess system policy to the RAM user.
You cannot write other data to the dedicated Logstore, modify or delete its index, or change its properties. Queries, statistics, and alerts are fully supported.
You cannot change the data retention period for a dedicated Logstore in the Simple Log Service console or by using an API or SDK. You can change it in the ApsaraDB for Redis console.
Simple Log Service must be active and have no overdue payments. Otherwise, the full-log analysis feature is suspended.

Billing

Metric integration incurs real-time export fees for Hybrid Cloud Monitoring and usage fees for Prometheus Service. Integrating second-level metrics incurs second-level monitoring fees for Hybrid Cloud Monitoring.
Tair (Redis OSS-compatible) audit logs incur pay-as-you-go fees based on storage space and retention period. Pricing varies by region. For details, see Billing items.
Writing, storing, or querying slow query logs and running logs is free of charge.
If the Logstore uses the pay-by-function billing mode, sending Redis logs to Simple Log Service incurs charges for data transformation, data shipping, and outbound traffic. You incur outbound traffic fees when you stream data from a public endpoint. For more information, see Billing items for the pay-by-function mode.
If the Logstore uses the pay-by-data-volume billing mode, sending Redis logs to Simple Log Service incurs charges based on factors such as the volume of raw data written. For more information, see Billing items for the pay-by-data-volume mode.

Integrate data

Log on to the CloudMonitor 2.0 console. Select the target workspace and, in the left-side navigation pane, click Integration Center. Click Tair (Redis OSS-compatible) to start the integration.
Create or select a Policy Name. Select the Entity Scope for the integration.

Select the observable data to integrate, and then click OK.

Observable data	Configuration
Tair metrics	Tag Keys: Specify instance tag keys to enrich your metrics. The tag key-value pairs are automatically injected into the metric labels. Second-level monitoring: Integrates second-level metrics from the cloud service. Enabled by default.

After the integration is complete, view the integrated entities and observability data in Entity Explorer or Database Observability.

Storage policy

When you integrate Tair, CloudMonitor 2.0 automatically creates a Simple Log Service Logstore and a Prometheus instance to store observability data.

Type	Default storage location	Notes
Metrics	Prometheus instance: RegionShare:{{workspaceName}}:{{regionId}}	None
Audit log	SLS Project:nosql-{{userId}}-{{regionId}} SLS Logstore:redis_audit_log_standard	Stores ApsaraDB for Redis audit logs for operational review and security compliance. These logs help security auditors identify who modified data and when, detecting internal risks such as permission abuse or non-compliant command execution. These logs help your business systems meet security regulation audit requirements.
Slow query log and running log	SLS Project:nosql-{{userId}}-{{regionId}} SLS Logstore:redis_slow_run_log	Stores slow query logs and running logs from Tair (Redis OSS-compatible). Slow query logs record requests that exceed a specified execution threshold, helping you identify performance bottlenecks and optimize queries. Running logs record the lifecycle status of a Redis instance, helping you troubleshoot O&M issues.

Delete or modify an integration policy

To cancel the Tair (Redis OSS-compatible) integration, go to the Integration Management page in the Integration Center. Find the integration policy and click Edit or Delete.