ApsaraDB for Redis supports a variety of performance metrics. You can query the monitoring data of an ApsaraDB for Redis instance during a specified period of time in the previous month. This help you gain insights into the status of the ApsaraDB for Redis instance and troubleshoot issues.

Metric granularity

To avoid adversely affecting the operation of the instance and ensure the effect of trend charts, metrics are collected at different frequencies and within different time ranges.

Supported time range Data collection interval
10 minutes or less 5 seconds
More than 10 minutes and less than or equal to one day 1 minute
More than one day and less than or equal to seven days 1 hour
Note
  • ApsaraDB for Redis allows you to query the monitoring data of the previous month. The maximum time range that you can specify for a query is seven days. For example, if the current day is March 10, 2021, you can query the monitoring data from February 10 to March 10. If you set the start time to February 10, the latest end time is February 17.
  • If a cluster or read/write splitting instance has 32 or more data nodes, the time range that you can specify for all data nodes on the All tab cannot exceed 1 hour. The monitoring data is collected at intervals of 1 minute.

Procedure

  1. Log on to the ApsaraDB for Redis console and go to the Instances page. In the top navigation bar, select the region in which the instance is deployed. Then, find the instance and click the instance ID.
  2. In the left-side navigation pane, click Performance Monitor.
  3. Perform the following operations based on the architecture of the ApsaraDB for Redis instance.
    Note You can query the monitoring data of the previous month. The maximum time range that you can specify for a query is seven days. For example, if the current day is March 10, 2021, you can query the monitoring data from February 10 to March 10. If you set the start time to February 10, the latest end time is February 17.
    Architecture Procedure
    Standard Specify a time range.
    Figure 1. View the monitoring data of a standard instance
    View the monitoring data of a standard instance

    Cluster

    Read/write splitting

    		 Select a node type and specify a time range. Click one of the following tabs:
    • All: displays the average values of metrics for all data nodes or proxy nodes. The following figure shows the average CPU utilization of all data nodes.
    • Data Node or Proxy Node: displays the trend chart of a specified node.
    Figure 2. View the monitoring data of a cluster instance or read/write splitting instance
    View the monitoring data of a cluster instance or read/write splitting instance
  4. To view the trend of a metric within a specified time period, you can perform the following operations on the current page.
    Figure 3. Trend chart of a metric
    Trend chart of a metric
    • On the right side of View, you can select the number of trend charts displayed per row. Up to three trend charts can be displayed per row.
    • To display the trend chart of a specific metric group, click the name of the metric group on the right side of the page.
    • To view the description of a metric, move the pointer over the Info icon icon in the upper-left corner of the trend chart.
    • A metric contains multiple subordinate metrics. In this following example, Key Statistics is used. If you move the pointer over the trend chart, the values of subordinate metrics at a point in time are displayed.
    • If you click the name of a performance metric below the trend chart, the performance metric is not displayed in the trend chart. To reset the metric, click the name again.
    Note For more information about metrics, see Monitoring metrics.

Related API operations

Operation Description
DescribeHistoryMonitorValues Queries the monitoring data of an ApsaraDB for Redis instance.
Note When you call this operation, you must use the MonitorKeys parameter to specify the metrics that you want to monitor and then retrieve the corresponding monitoring data. For more information about the MonitorKeys parameter, see MonitorKeys.