CDN monitoring

Last Updated: Jul 07, 2017

Overview

CloudMonitor displays the usage of CDN based on nine metrics, including Queries Per Second (QPS), Bytes Per Second (BPS), and bytes hit rate. After you add a CDN domain, CloudMonitor automatically monitors the domain.

You can access the CDN monitoring page to view the metric data. You can configure alert policies for metrics so that an alert is generated when a data exception occurs.

Monitoring service

Metric descriptions

Metric Definition Dimension Units Minimum monitoring granularity
QPS Total access requests in a specific time interval/Time interval. Instance Quantity 5 minutes
Peak bandwidth BPS The maximum network traffic per unit time. Instance bit/s 5 minutes
Hit rate The probability that request bytes hit the cache in a specific time interval (Bytes = Number of requests x Traffic). The bytes hit rate directly reflects the back-to-source traffic. Instance Percentage 5 minutes
Internet outbound traffic CDN Internet outbound traffic. Instance Bytes 5 minutes
HTTP Return Code 4xx percentage Percentage of HTTP Return Code 4xx in a specific time interval. Instance Percentage 5 minutes
HTTP Return Code 5xx percentage Percentage of HTTP Return Code 5xx in a specific time interval. Instance Percentage 5 minutes

View metric data

  1. Log on to the CloudMonitor console.

  2. Go to the CDN 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. (Optional) Click the Chart Size button to switch to large chart display mode.

Alert service

Parameter description

  • Metrics: The monitoring indicators provided by CDN.

  • 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 the 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.

  • Trigger Alert After Threshold Value Is Exceeded Several Times: This 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 alert policy

  1. Log on to the CloudMonitor console.

  2. Go to the CDN instance list under Cloud Service Monitoring.

  3. Click Alert Policies in instance list Action to access the instance’s alert policies page.

  4. Click Create Alert Policy at the bottom of the alert policies page to create an alert policy based on the entered parameters.

Thank you! We've received your feedback.