EIP monitoring

Last Updated: Nov 15, 2017

CloudMonitor provides four Elastic IP Address (EIP) metrics (outbound traffic, inbound traffic, outgoing packet count, and incoming packet count), to help you monitor the service status. You can set alarm rules for these metrics. Once you buy the EIP service, CloudMonitor automatically collects data on the following four metrics:

Monitoring service

Metrics description

Metric

Definition

Dimension

Units

Minimum monitoring granularity

Inbound traffic

The volume of traffic per second that passes through the EIP to an ECS instance.

Instance

Bits/s

1 minute

Outbound traffic

The volume of traffic per second that passes through the EIP from an ECS instance.

Instance

Bits/s

1 minute

Incoming packet count

The number of packets per second that pass through the EIP to an ECS instance.

Instance

Packages/s

1 minute

Outgoing packet count

The number of packets per second that pass through the EIP from an ECS instance.

View metric data

Go to the Elastic IP Address instance list under Cloud Service Monitoring.

Click an instance name in the product instance list and click Monitoring Charts from the Actions column to access the instance monitoring details page.

(Optional). Click the Chart Size button to switch to large chart display mode.

Alarm rule service

Parameter description

Metrics: The monitoring indicators provided by EIP.

Statistical cycle: The alarm rule system checks whether your monitoring data has exceeded the alarm threshold value based on the statistical cycle. For example, if the statistical cycle of the alarm rule for memory usage is set to one minute, the system checks whether the memory usage has exceeded the threshold value after every 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 preceding statistical methods are required for traffic-based indicators.

Trigger an alarm after the threshold value has exceeded several times: This refers to an alarm 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 alarm to go off when the CPU usage rate exceeds 80% within a 5-minute statistical cycle after the threshold value is exceeded three times. If the CPU usage rate is found to exceed 80% for the first time, no warning notification is sent. No alarm is reported if the CPU usage rate exceeds 80% only twice in a row. An alarm is reported only if the CPU usage rate exceeds 80% for the third time. That is, from the first time when the actual data exceeds the threshold to the time when the alarm rule is triggered, the minimum time consumed is the statistical cycle* (the quantity of consecutive detection times - 1) = 5*(3-1) = 10 minutes.