Why Are the Network Traffic Metrics in CES Different from Those Detected in ECS?

8



The sample data collection interval in the CES is different from that used by the metric monitoring tool in the ECS.


The CES collects ECS and EVS data at a four-minute interval. However, the metric monitoring tool in the ECS collects the data at a one-second interval.


A longer data collection interval causes distortion of data generated during a short period of time. Therefore, CES is suitable for long-term website monitoring and monitoring of applications running on ECSs.


Furthermore, you can configure alarm thresholds so that alarms can be generated in the event of resource exceptions or insufficiency, improving resource reliability.



Other related questions:
Reason why the timeslots occupied by GE services on the LOM board are different from those on other boards
The LOM board is specially designed to map client-side services to STM-64 signals and then encapsulate the services into OTU2 signals. STM-64 is divided into eight timeslots, and the bandwidth of each timeslot is 1.24 Gbit/s. Therefore, only one timeslot is required for the GE service. In contrast, the bandwidth of each timeslot on other boards is 155 Mbit/s, and 7 timeslots are required for the GE service.

Differences between timeslots occupied by GE services on LOM boards and those on other boards
Different from other boards, a LOM board maps a client service into an STM-64 signal and then multiplexes the STM-64 signal into an OTU2.An STM-64 signal is divided into 8 timeslots, each of which occupies 1.24 Gbit/s bandwidth. Therefore, a GE service on a LOM board occupies one timeslot. On other boards, each timeslot occupies 155 Mbit/s bandwidth. Therefore, a GE service on another board occupies seven timeslots.

Why is the actual suppression value different from the configured traffic suppression value
The traffic suppression supported by AR series routers is a type of granularity-based suppression. -The AR1200 series use the committed information rate (CIR) mode. If the traffic suppression value is between 64 kbit/s and 1000 kbit/s, the granularity is 64 kbit/s. For example, if the traffic suppression value is set to 65 kbit/s, the effective traffic suppression value is 64 kbit/s. If the traffic suppression value is set to 200 kbit/s, the effective traffic suppression value is 128 kbit/s, and so on. If the traffic suppression value is between 1000 kbit/s and 100,000 kbit/s, the granularity is 1000 kbit/s. For example, if the traffic suppression value is set to 1001 kbit/s, the effective traffic suppression value is 1000 kbit/s. If the traffic suppression value is set to 2999 kbit/s, the effective traffic suppression value is 2000 kbit/s, and so on. -The AR2200 , AR3200 and AR3600 series use the packet mode. The granularity is 125 packets per second (pps). If the traffic suppression value is set to 10 pps, the effective traffic suppression value is 0 pps. If the traffic suppression value is set to 126 pps, the effective traffic suppression value is 125 pps, and so on. Therefore, if the traffic suppression value is not set to a multiple of the granularity, the actual suppression value is different from the traffic suppression value that is set. Within a specified granularity range, all suppression values are correct.

Why Are ECS Instances Displayed in the Monitoring Diagram Different from Those Displayed in the Table on the Basic Information Page of an AS Group?
Abnormal are replaced during health check. When the AS group is disabled, the health status of ECSs will still be checked, but abnormal ECSs state will not be replaced. Therefore, the quantity of ECS instances displayed on the AS group monitoring page is different from the actual quantity in the AS group.

Issue 2:

The monitoring diagram on the Basic Information page records the quantity of available ECSs in the AS group, which is reported by AS to CES periodically, while the table provides scaling action logs of the AS group. AS may fail to report the data to CES due to network failure or other causes. This may affect correctness of data on the diagram.

Handling Method

Issue 1:

  1. Go to the Instance tab page and check for ECSs whose health status is Abnormal in the instance list.
  2. Enable the AS group again. Abnormal ECSs will be replaced during health check, and the quantity of ECS instances displayed on the AS group monitoring page will be the same as the actual instance.

Issue 2:

  1. Use the data in the table when the data in the monitoring diagram is inconsistent with that in the table or some details are missing on the diagram, because scaling action logs provided in the table record instance changes before and after each scaling action.
  2. Contact the administrator for handling.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top