Cloud monitoring 7 monitors by monitoring the used cache, read hit ratio, and so on for cloud database memcache Edition Service instances item, helps the user monitor the running status of the instance and supports the user to set alarm rules on the monitoring item. User purchases After the memcache service, cloud monitoring automatically collects data for the above monitoring items.

Monitoring Services

  • Monitoring item description
    Monitoring items Meaning Dimensions Unit Minimum monitor Granularity
    Cache used The amount of cache that has been used Instance Bytes 1 minute
    Read hit rate Read down the probability of Kv success Instance Percentage 1 minute
    QPS Total number of read kV per second Instance Number 1 minute
    Record count The total number of current kV Instance Number 1 minute
    Cache input bandwidth Traffic generated by accessing the cache Instance BPS 1 minute
    Cache output bandwidth Traffic generated by reading the cache Instance BPS 1 minute
    Eviction The number of Kv evict per second Instance Number per second 1 minute
    Note
    • Monitor Data is saved for up to 31 days.

    • Users can view monitoring data for up to 14 days in a row.

  • Viewing Monitoring Data
    1. Log in to the cloud monitoring console.
    2. Go to cloud database memcache monitored by cloud services Release List of monitoring instances.
    3. Click the Instance name or the monitor chart in the operation to go To the instance monitoring details page to view the metrics.
    4. Click the time range quick select button or the exact select function above the page.
    5. Click the zoom in button in the upper-right corner of the monitor MAP to view the monitor larger image.

Alarm service

Cloud monitor for memcache The alarm service is provided by all monitoring items, after the user sets the alarm rules for the important monitoring items, you can receive alarm notifications in time after monitoring data exceeds the threshold, so you can process it quickly, reduce the possibility of failure.

  • Parameter descriptions
    • Monitoring items: Monitoring metrics provided by the redis edition of the cloud server.
    • Statistical Cycle: the alarm system checks if your monitoring data exceeds the alarm threshold for this cycle. For example, to set a memory usage alarm rule, the statistics cycle is 1 minute, an interval of 1 minute checks if memory usage exceeds the threshold.
    • Statistical Methods: Statistical Methods refer to settings that exceed the threshold range. You can set the average, maximum, minimum, count, and value in a statistical method.
      • Average: the average of the monitored data during the statistical cycle. The statistic 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 the monitor data during the statistics cycle. The maximum value of monitoring data collected during the statistical cycle exceeds the threshold of 80.
      • Minimum: the minimum value of the monitored data during the statistics cycle. The minimum value for monitoring data collected during the statistical cycle exceeds the threshold of 80.
      • Value: Sum of monitoring data during the statistics cycle. When the sum of the metric data collected within the period is over 80%, it exceeds the threshold. Such statistical methods are required for traffic-class metrics.
    • Continuous number of times: refers to the continuous number of statistical cycle monitoring items that continue to exceed the threshold value to trigger the alarm.

      Example: Set CPU usage to more than 80% alarm, statistical cycle to 5 minutes, 3 consecutive The alarm after the threshold is exceeded, the first time the detection CPU usage exceeds 80%, the alarm notification is not issued. The second time in 5 minutes to detect CPU usage exceeds 80% and no alarm will be issued. The third probe still exceeds 80% Alarm notification will be issued only when. That is, from the first time the actual data exceeds the threshold to the final alarm rule, the minimum time required is statistical cycle X (number of consecutive probes-1) = 5 x (3-1) = 10 minutes.

  • Set single alarm rule
    1. Log on to the CloudMonitor console.
    2. Go to cloud database memcache monitored by cloud services Release List of monitoring instances.
    3. Click the Instance name or the monitor chart in the operation to enter the instance monitoring details page.
    4. Click the bell button in the upper-right corner of the monitor chart to set alarm rules for the monitoring items corresponding to the instance.
  • Set up bulk alarm rules
    1. Log on to the CloudMonitor console.
    2. Go to cloud database memcache monitored by cloud services Release List of monitoring instances.
    3. When the instance list page selects the desired instance, under the page, click set alarm rule, you can add alarm rules in bulk.