ApsaraDB for Memcache monitoring

Last Updated: Jul 05, 2017

Overview

CloudMonitor provides seven ApsaraDB for Memcache metrics, including used cache and read hit rate, to help you monitor the status of the service. You can set alert policies for these metrics. After you buy the Memcache service, CloudMonitor will automatically collect data on the metrics listed above.

Monitoring service

Metric descriptions

Metric Definition Dimension Units Minimum monitoring granularity
Used cache Amount of cache in use. Instance Bytes 1 minute
Read hit rate The probability that key values (KVs) are read successfully. Instance Percentage 1 minute
QPS Total times KVs are read per second. Instance Count 1 minute
Record count Total number of KVs in the current measurement period. Instance Count 1 minute
Cache inbound bandwidth Traffic generated during access to the cache. Instance Bps 1 minute
Cache outbound bandwidth Traffic generated during read operations on the cache. Instance Bps 1 minute
Eviction Number of KVs evicted per second. Instance KVs per second 1 minute

Note:

  • Metric data are saved for up to 31 days.

  • You can view metric data for up to 14 consecutive days.

View metric data

  1. Log on to the CloudMonitor console.

  2. Go to the ApsaraDB for Memcache Monitoring instance list under Cloud Service Monitoring.

  3. Click an instance name in the product instance list or click Metric Chart in the Action column to access the instance monitoring details page and view various indicators.

  4. Click a Time Range shortcut on the top of the page or use the specific selection function.

  5. Click the Zoom In button in the top-right corner of the metric chart to enlarge the graph.

Alert service

CloudMonitor provides alert services for all Memcache metrics. After setting an alert policy for an important metric, you will receive an alert notification if the metric data exceeds the set threshold value. This allows for rapid troubleshooting and reduces the probability of faults.

Parameter descriptions

  • Metrics: The monitoring indicators provided by ECS for Redis.

  • Statistical cycle: The alert system checks whether your monitoring data has exceeded the alert threshold value based on the statistical cycle. For example, if the statistical cycle of the alert policy for memory usage is set to one minute, the system checks whether the memory usage has exceeded the threshold value every other minute.

  • Statistic: This sets the method used to determine if the data exceeds the threshold. You can set Average, Maximum, Minimum, and Sum in Statistic.

    • Average: The average value of metric data within a statistical cycle. The statistical result is the average of all metric data collected within 15 minutes. An average value of over 80% is deemed to exceed the threshold.

    • Maximum: The maximum value of metric data within a statistical cycle. When the maximum value of the metric data collected within the statistical cycle is over 80%, the value exceeds the threshold.

    • Minimum: The minimum value of metric data within a statistical cycle. When the minimum value of the metric data collected within the statistical cycle is larger than 80%, the value exceeds the threshold.

    • Sum: The sum of metric data within a statistical cycle. When the sum of the metric data collected within the statistical cycle is over 80%, it exceeds the threshold. The above statistical methods are needed for traffic-based indicators.

  • Consecutive times: Refers to an alert which is triggered when the value of the metric continuously exceeds the threshold value in several consecutive statistical cycles.

    For example, you may set the alert to go off when the CPU usage rate exceeds 80% within a 5-minute statistical cycle after the threshold value is exceeded for three times. If the CPU usage rate is found to exceed 80% for the first time, no warning notification is sent. No alert is reported if the CPU usage rate exceeds 80% only twice in a row. An alert is reported only if the CPU usage rate exceeds 80% for a third time. That is, from the first time when the actual data exceeds the threshold to the time when the alert policy is triggered, the minimum time consumed is Statistical cycle*(the quantity of consecutive detection times-1) = 5*(3-1) = 10 minutes.

Set an individual alert policy

  1. Log on to the CloudMonitor console.

  2. Go to the ApsaraDB for Memcache Monitoring instance list under Cloud Service Monitoring.

  3. Click an instance name in the product instance list or click Metric Chart in the Action column to access the instance monitoring details page.

  4. Click the Bell button in the top-right corner of the metric chart to set an alert for the corresponding metric for this instance.

Batch set alert policies

  1. Log on to the CloudMonitor console.

  2. Go to the ApsaraDB for Memcache Monitoring instance list under Cloud Service Monitoring.

  3. Select the appropriate instance on the instance list page. Then, click Set Alert Policies at the bottom of the page to add multiple alert policies.

Thank you! We've received your feedback.