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.

Other related questions:
Why Are the Network Traffic Metrics in CES Different from Those Detected in ECS?

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.

Database Instances Fail to Be Displayed
1.Restart OceanStor BCManager Agent after checking and configuring the Oracle or DB2 production environment. NOTE: For details about how to start OceanStor BCManager Agent, see Command for Starting OceanStor BCManager Agent. 2.After OceanStor BCManager Agent is started, Recreate database protected groups.

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