The Top Key Delivery feature in the operations service delivers real-time metrics for hot keys and big keys from your Redis instances to Cloud Monitor. You can then configure alert rules based on these metrics to quickly identify and address potential performance issues.
Prerequisites
You must meet the following prerequisites to enable this feature:
-
The DAS operations service must be enabled.
-
The instance must be in one of the following supported regions: China (Beijing), China (Zhangjiakou), China (Shanghai), Germany (Frankfurt), Singapore, US (Virginia), or Japan (Tokyo).
Billing
-
Fees incurred for enabling the operations service for an instance.
-
Fees for data storage in Log Service (SLS).
Procedure
Log on to the DAS console.
-
In the left-side navigation pane, click .
Find the target instance and click the instance ID to open the instance details page.
-
In the left-side navigation pane, click Top Key Statistics. On the Key Analysis page, click TOP KEY Delivery in the upper-right corner.
NoteIf the operations service is not enabled for the instance, this feature is unavailable and the button is grayed out. You must first enable the operations service for the instance.
-
In the Top Key Delivery dialog box, click Enable, and then click Confirm.
After you enable this feature, charges will apply for using Cloud Monitor. The default delivery destination is Cloud Monitor. Top key metrics are delivered to Cloud Monitor in real time, enabling you to set alert rules.
-
After you enable this feature, the system automatically delivers top key metrics to Log Service (SLS) in your account. The system also automatically creates a Project and a corresponding time series store based on the following naming rules:
-
Target Project:
-
Naming format:
nosql-{your-alibaba-cloud-account-id}-{region} -
Example:
nosql-176498472******-cn-hangzhou
-
-
Target time series store:
-
Fixed name:
redis_top_key_log
-
NoteBy default, data in
redis_top_key_logis stored for 30 days. You can change this period by modifying the Data Retention Period. -
Metrics
The delivered monitoring data includes five core metrics and nine dimensions for filtering.
|
Metric name |
Description |
Example value |
|
Metrics |
||
|
|
Access frequency of the hot key. |
|
|
|
Inbound traffic for the hot key, in bytes. |
|
|
|
Outbound traffic for the hot key, in bytes. |
|
|
|
Number of elements in the big key. |
|
|
|
Memory used by the big key, in bytes. |
|
|
Dimensions |
||
|
|
The account ID. |
|
|
|
The instance ID. |
|
|
|
The node ID. |
|
|
|
The ID of the data shard node. |
This ID is used to distinguish the primary node from read-only nodes in a read/write splitting instance that uses cloud disks. Example: |
|
|
The ID of the database where the key is stored. |
|
|
|
The key name. |
|
|
|
The data type of the key. |
|
|
|
The basic category of the top key. |
• Hot key: |
|
|
The detailed category of the top key. |
• Hot key (by QPS): |