From d75e2754914705d52524a1c80e18745508f3d8de Mon Sep 17 00:00:00 2001 From: "Yang, Tong" Date: Tue, 22 Oct 2024 11:17:42 +0000 Subject: [PATCH] CES API 20241015 version Reviewed-by: Bobkova, Natalia Co-authored-by: Yang, Tong Co-committed-by: Yang, Tong --- docs/ces/api-ref/ALL_META.TXT.json | 2 +- docs/ces/api-ref/CLASS.TXT.json | 2 +- docs/ces/api-ref/ErrorCode.html | 2 +- docs/ces/api-ref/ces_01_0054.html | 4076 ++++++++++++++--- docs/ces/api-ref/ces_03_0001.html | 2 +- docs/ces/api-ref/ces_03_0023.html | 4 +- docs/ces/api-ref/ces_03_0027.html | 4 +- docs/ces/api-ref/ces_03_0028.html | 2 +- docs/ces/api-ref/ces_03_0031.html | 10 +- docs/ces/api-ref/ces_03_0033.html | 14 +- docs/ces/api-ref/ces_03_0034.html | 176 +- docs/ces/api-ref/ces_03_0035.html | 6 +- docs/ces/api-ref/ces_03_0057.html | 11 +- docs/ces/api-ref/ces_03_0059.html | 236 +- docs/ces/api-ref/ces_03_0060.html | 12 +- docs/ces/api-ref/en-us_topic_0032831274.html | 3 +- .../public_sys-resources/imageclose.gif | Bin 0 -> 1238 bytes .../public_sys-resources/imageclosehover.gif | Bin 0 -> 1172 bytes .../api-ref/public_sys-resources/imagemax.gif | Bin 0 -> 1267 bytes .../public_sys-resources/imagemaxhover.gif | Bin 0 -> 1199 bytes .../public_sys-resources/macFFBgHack.png | Bin 0 -> 1014 bytes value | 0 with | 0 23 files changed, 3765 insertions(+), 797 deletions(-) create mode 100644 docs/ces/api-ref/public_sys-resources/imageclose.gif create mode 100644 docs/ces/api-ref/public_sys-resources/imageclosehover.gif create mode 100644 docs/ces/api-ref/public_sys-resources/imagemax.gif create mode 100644 docs/ces/api-ref/public_sys-resources/imagemaxhover.gif create mode 100644 docs/ces/api-ref/public_sys-resources/macFFBgHack.png create mode 100644 value create mode 100644 with diff --git a/docs/ces/api-ref/ALL_META.TXT.json b/docs/ces/api-ref/ALL_META.TXT.json index 7dd58b78..1dc6e25b 100644 --- a/docs/ces/api-ref/ALL_META.TXT.json +++ b/docs/ces/api-ref/ALL_META.TXT.json @@ -277,7 +277,7 @@ "node_id":"en-us_topic_0032831274.xml", "product_code":"ces", "code":"16", - "des":"This API is used to add one or more pieces of custom metric monitoring data to solve the problem that the system metrics cannot meet specific service requirements.POST /V", + "des":"This API is used to add one or more pieces of custom metric monitoring data to solve the problem that the system metrics cannot meet specific service requirements.For det", "doc_type":"api", "kw":"Adding Monitoring Data,Monitoring Data,API Reference", "search_title":"", diff --git a/docs/ces/api-ref/CLASS.TXT.json b/docs/ces/api-ref/CLASS.TXT.json index f179c2f8..5908c2fa 100644 --- a/docs/ces/api-ref/CLASS.TXT.json +++ b/docs/ces/api-ref/CLASS.TXT.json @@ -135,7 +135,7 @@ "code":"15" }, { - "desc":"This API is used to add one or more pieces of custom metric monitoring data to solve the problem that the system metrics cannot meet specific service requirements.POST /V", + "desc":"This API is used to add one or more pieces of custom metric monitoring data to solve the problem that the system metrics cannot meet specific service requirements.For det", "product_code":"ces", "title":"Adding Monitoring Data", "uri":"en-us_topic_0032831274.html", diff --git a/docs/ces/api-ref/ErrorCode.html b/docs/ces/api-ref/ErrorCode.html index 8c7f1505..79f0d28e 100644 --- a/docs/ces/api-ref/ErrorCode.html +++ b/docs/ces/api-ref/ErrorCode.html @@ -172,7 +172,7 @@

ces.0014

-

Some content in the message body is correct.

+

Some content in the message body is incorrect.

Some content in message body is not correct.

diff --git a/docs/ces/api-ref/ces_01_0054.html b/docs/ces/api-ref/ces_01_0054.html index e529ca3e..af0647e2 100644 --- a/docs/ces/api-ref/ces_01_0054.html +++ b/docs/ces/api-ref/ces_01_0054.html @@ -65,7 +65,7 @@

Services are interrupted.

-

Restart triggered due to hardware fault

+

Restart triggered due to system faults

startAutoRecovery

@@ -78,7 +78,7 @@

Services may be interrupted.

-

Restart completed due to hardware failure

+

Restart completed due to system faults

endAutoRecovery

@@ -163,998 +163,3932 @@

Once a physical host running ECSs breaks down, the ECSs are automatically migrated to a functional physical host. During the migration, the ECSs will be restarted.

-
Table 2 Advanced Anti-DDoS (AAD)

Event Source

+
- - - - - - + - - - - - - - + - - - - - - - - - - - - - - - - - - + + + + + + +
Table 2 Advanced Anti-DDoS (AAD)

Event Source

Event Name

+

Namespace

Event ID

+

Event Name

Event Severity

+

Event ID

Description

+

Event Severity

Solution

+

Description

Impact

+

Solution

+

Impact

AAD

+

AAD

+

DDoS Attack Events

+

SYS.DDOS

ddosAttackEvents

+

DDoS Attack Events

Major

+

ddosAttackEvents

A DDoS attack occurs in the AAD protected lines.

+

Major

Judge the impact on services based on the attack traffic and attack type. If the attack traffic exceeds your purchased elastic bandwidth, change to another line or increase your bandwidth.

+

A DDoS attack occurs in the AAD protected lines.

Services may be interrupted.

+

Judge the impact on services based on the attack traffic and attack type. If the attack traffic exceeds your purchased elastic bandwidth, change to another line or increase your bandwidth.

+

Services may be interrupted.

Domain name scheduling event

+

Domain name scheduling event

domainNameDispatchEvents

+

domainNameDispatchEvents

Major

+

Major

The high-defense CNAME corresponding to the domain name is scheduled, and the domain name is resolved to another high-defense IP address.

+

The high-defense CNAME corresponding to the domain name is scheduled, and the domain name is resolved to another high-defense IP address.

Pay attention to the workloads involving the domain name.

+

Pay attention to the workloads involving the domain name.

Services are not affected.

+

Services are not affected.

Blackhole event

+

Blackhole event

blackHoleEvents

+

blackHoleEvents

Major

+

Major

The attack traffic exceeds the purchased AAD protection threshold.

+

The attack traffic exceeds the purchased AAD protection threshold.

A blackhole is canceled after 30 minutes by default. The actual blackhole duration is related to the blackhole triggering times and peak attack traffic on the current day. The maximum duration is 24 hours. If you need to permit access before a blackhole becomes ineffective, contact technical support.

+

A blackhole is canceled after 30 minutes by default. The actual blackhole duration is related to the blackhole triggering times and peak attack traffic on the current day. The maximum duration is 24 hours. If you need to permit access before a blackhole becomes ineffective, contact technical support.

Services may be interrupted.

+

Services may be interrupted.

Cancel Blackhole

+

Cancel Blackhole

cancelBlackHole

+

cancelBlackHole

Informational

+

Informational

The customer's AAD instance recovers from the black hole state.

+

The customer's AAD instance recovers from the black hole state.

This is only a prompt and no action is required.

+

This is only a prompt and no action is required.

Customer services recover.

+

Customer services recover.

+

IP address scheduling triggered

+

ipDispatchEvents

+

Major

+

IP route changed

+

Check the workloads of the IP address.

+

Services are not affected.
-
Table 3 Cloud Backup and Recovery (CBR)

Event Source

+
- - - - - - + - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 3 Elastic Load Balance (ELB)

Event Source

Event Name

+

Namespace

Event ID

+

Event Name

Event Severity

+

Event ID

Description

+

Event Severity

Solution

+

Description

Impact

+

Solution

+

Impact

CBR

+

ELB

Failed to create the backup.

+

SYS.ELB

backupFailed

+

The backend servers are unhealthy.

Critical

+

healthCheckUnhealthy

The backup failed to be created.

+

Major

Manually create a backup or contact customer service.

+

Generally, this problem occurs because backend server services are offline. This event will not be reported after it is reported for several times.

Data loss may occur.

+

Ensure that the backend servers are running properly.

+

ELB does not forward requests to unhealthy backend servers. If all backend servers in the backend server group are detected unhealthy, services will be interrupted.

Failed to restore the resource using a backup.

+

The backend server is detected healthy.

restorationFailed

+

healthCheckRecovery

Critical

+

Minor

The resource failed to be restored using a backup.

+

The backend server is detected healthy.

Restore the resource using another backup or contact customer service.

+

No further action is required.

Data loss may occur.

-

Failed to delete the backup.

-

backupDeleteFailed

-

Critical

-

The backup failed to be deleted.

-

Try again later or contact customer service.

-

Charging may be abnormal.

-

Failed to delete the vault.

-

vaultDeleteFailed

-

Critical

-

The vault failed to be deleted.

-

Try again later or contact technical support.

-

Charging may be abnormal.

-

Replication failure

-

replicationFailed

-

Critical

-

The backup failed to be replicated.

-

Try again later or contact technical support.

-

Data loss may occur.

-

The backup is created successfully.

-

backupSucceeded

-

Major

-

The backup was created.

-

None

-

None

-

Resource restoration using a backup succeeded.

-

restorationSucceeded

-

Major

-

The resource was restored using a backup.

-

Check whether the data is successfully restored.

-

None

-

The backup is deleted successfully.

-

backupDeletionSucceeded

-

Major

-

The backup was deleted.

-

None

-

None

-

The vault is deleted successfully.

-

vaultDeletionSucceeded

-

Major

-

The vault was deleted.

-

None

-

None

-

Replication success

-

replicationSucceeded

-

Major

-

The backup was replicated successfully.

-

None

-

None

+

The load balancer can properly route requests to the backend server.
-
Table 4 Relational Database Service (RDS) — resource exception

Event Source

+
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + +
Table 4 Cloud Backup and Recovery (CBR)

Event Source

Event Name

+

Event Name

Event ID

+

Event ID

Event Severity

+

Event Severity

Description

+

Description

Solution

+

Solution

Impact

+

Impact

RDS

+

CBR

Full backup failure

+

Failed to create the backup.

fullBackupFailed

+

backupFailed

Major

+

Critical

A single full backup failure does not affect the files that have been successfully backed up, but prolong the incremental backup time during the point-in-time restore (PITR).

+

The backup failed to be created.

Create a manual backup again.

+

Manually create a backup or contact customer service.

Backup failed.

+

Data loss may occur.

Primary/standby switchover or failover

+

Failed to restore the resource using a backup.

PrimaryStandbySwitched

+

restorationFailed

Major

+

Critical

This event is reported when a primary/standby switchover or a failover is triggered.

+

The resource failed to be restored using a backup.

  1. After the switchover or failover is complete, check whether workloads are restored. If workloads are not restored, contact SRE engineers.
  2. Ignore the event if you have performed a switchover.
  3. If the failover is triggered by a node fault, contact the SRE engineers.
+

Restore the resource using another backup or contact customer service.

Downtime occurs during the switchover.

+

Data loss may occur.

Replication status abnormal

+

Failed to delete the backup.

abnormalReplicationStatus

+

backupDeleteFailed

Major

+

Critical

The possible causes are as follows:

-

The replication delay between the primary instance and the standby instance or a read replica is too long, which usually occurs when a large amount of data is being written to databases or a large transaction is being processed. During peak hours, data may be blocked.

-

The network between the primary instance and the standby instance or a read replica is disconnected.

+

The backup failed to be deleted.

Submit a service ticket.

+

Try again later or contact customer service.

Your applications are not affected because this event does not interrupt data read and write.

+

Charging may be abnormal.

Replication status recovered

+

Failed to delete the vault.

replicationStatusRecovered

+

vaultDeleteFailed

Major

+

Critical

The replication delay between the primary and standby instances is within the normal range, or the network connection between them has restored.

+

The vault failed to be deleted.

No action is required.

+

Try again later or contact technical support.

None

+

Charging may be abnormal.

DB instance faulty

+

Replication failure

faultyDBInstance

+

replicationFailed

Major

+

Critical

A single or primary DB instance was faulty due to a disaster or a server failure.

+

The backup failed to be replicated.

Check whether an automated backup policy has been configured for the DB instance and submit a service ticket.

+

Try again later or contact technical support.

The database service may be unavailable.

+

Data loss may occur.

DB instance recovered

+

The backup is created successfully.

DBInstanceRecovered

+

backupSucceeded

Major

+

Major

RDS rebuilds the standby DB instance with its high availability. After the instance is rebuilt, this event will be reported.

+

The backup was created.

No action is required.

+

None

None

+

None

Failure of changing single DB instance to primary/standby

+

Resource restoration using a backup succeeded.

singleToHaFailed

+

restorationSucceeded

Major

+

Major

A fault occurs when RDS is creating the standby DB instance or configuring replication between the primary and standby DB instances. The fault may occur because resources are insufficient in the data center where the standby DB instance is located.

+

The resource was restored using a backup.

Submit a service ticket.

+

Check whether the data is successfully restored.

Your applications are not affected because this event does not interrupt data read and write of the DB instance.

+

None

Database process restarted

+

The backup is deleted successfully.

DatabaseProcessRestarted

+

backupDeletionSucceeded

Major

+

Major

The database process is stopped due to insufficient memory or high load.

+

The backup was deleted.

Log in to the Cloud Eye console. Check whether the memory usage increases sharply, the CPU usage is too high for a long time, or the storage space is insufficient. You can increase the CPU and memory specifications or optimize the service logic.

+

None

When the process exits abnormally, workloads are interrupted. In this case, RDS automatically restarts the database process and attempts to recover the workloads.

+

None

Instance storage full

+

The vault is deleted successfully.

instanceDiskFull

+

vaultDeletionSucceeded

Major

+

Major

Generally, the cause is that the data space usage is too high.

+

The vault was deleted.

Scale up the instance.

+

None

The DB instance becomes read-only because the storage space is full, and data cannot be written to the database.

+

None

Instance storage full recovered

+

Replication success

instanceDiskFullRecovered

+

replicationSucceeded

Major

+

Major

The instance disk is recovered.

+

The backup was replicated successfully.

No action is required.

+

None

Cancel the read-only state of the instance and resume write operations.

+

None

Read replica promotion failure

+

Client offline

activeStandBySwitchFailed

+

agentOffline

Major

+

Critical

The read replica fails to be promoted to the primary DB instance due to network or server failures. The original primary DB instance takes over workloads quickly.

+

The backup client was offline.

Submit a service ticket.

+

Ensure that the Agent status is normal and the backup client can be connected to .

The read replica fails to be promoted to the primary DB instance.

+

Backup tasks may fail.

+

Client online

+

agentOnline

+

Major

+

The backup client was online.

+

None

+

None
-
Table 5 GaussDB(for MySQL)

Event Source

+
- - - - - - + - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 5 Relational Database Service (RDS) — resource exception

Event Source

Event Name

+

Namespace

Event ID

+

Event Name

Event Severity

+

Event ID

Description

+

Event Severity

Solution

+

Description

Impact

+

Solution

+

Impact

GaussDB(for MySQL)

+

RDS

Incremental backup failure

+

SYS.RDS

TaurusIncrementalBackupInstanceFailed

+

DB instance creation failure

Major

+

createInstanceFailed

The network between the instance and the management plane (or the OBS) is disconnected, or the backup environment created for the instance is abnormal.

+

Major

Submit a service ticket.

+

Generally, the cause is that the number of disks is insufficient due to quota limits, or underlying resources are exhausted.

Backup jobs fail.

+

The selected resource specifications are insufficient. Select other available specifications and try again.

+

DB instances cannot be created.

Read replica creation failure

+

Full backup failure

addReadonlyNodesFailed

+

fullBackupFailed

Major

+

Major

The quota is insufficient or underlying resources are exhausted.

+

A single full backup failure does not affect the files that have been successfully backed up, but prolong the incremental backup time during the point-in-time restore (PITR).

Check the read replica quota. Release resources and create read replicas again.

+

Try again.

Read replicas fail to be created.

+

Restoration using backups will be affected.

DB instance creation failure

+

Read replica promotion failure

createInstanceFailed

+

activeStandBySwitchFailed

Major

+

Major

The instance quota or underlying resources are insufficient.

+

The standby DB instance does not take over workloads from the primary DB instance due to network or server failures. The original primary DB instance continues to provide services within a short time.

Check the instance quota. Release resources and create instances again.

+

Perform the operation again during off-peak hours.

DB instances fail to be created.

+

Read replica promotion failed.

Read replica promotion failure

+

Replication status abnormal

activeStandBySwitchFailed

+

abnormalReplicationStatus

Major

+

Major

The read replica fails to be promoted to the primary node due to network or server failures. The original primary node takes over services quickly.

+

The possible causes are as follows:

+

The replication delay between the primary instance and the standby instance or a read replica is too long, which usually occurs when a large amount of data is being written to databases or a large transaction is being processed. During peak hours, data may be blocked.

+

The network between the primary instance and the standby instance or a read replica is disconnected.

Submit a service ticket.

+

The issue is being fixed. Please wait for our notifications.

The read replica fails to be promoted to the primary node.

+

The replication status is abnormal.

Instance specifications change failure

+

Replication status recovered

flavorAlterationFailed

+

replicationStatusRecovered

Major

+

Major

The quota is insufficient or underlying resources are exhausted.

+

The replication delay between the primary and standby instances is within the normal range, or the network connection between them has restored.

Submit a service ticket.

+

Check whether services are running properly.

Instance specifications fail to be changed.

+

Replication status is recovered.

Faulty DB instance

+

DB instance faulty

TaurusInstanceRunningStatusAbnormal

+

faultyDBInstance

Major

+

Major

The instance process is faulty or the communications between the instance and the DFV storage are abnormal.

+

A single or primary DB instance was faulty due to a catastrophic failure, for example, server failure.

Submit a service ticket.

+

The issue is being fixed. Please wait for our notifications.

Services may be affected.

+

The instance status is abnormal.

DB instance recovered

+

DB instance recovered

TaurusInstanceRunningStatusRecovered

+

DBInstanceRecovered

Major

+

Major

The instance is recovered.

+

RDS rebuilds the standby DB instance with its high availability. After the instance is rebuilt, this event will be reported.

Observe the service running status.

+

The DB instance status is normal. Check whether services are running properly.

None

+

The instance is recovered.

Faulty node

+

Failure of changing single DB instance to primary/standby

TaurusNodeRunningStatusAbnormal

+

singleToHaFailed

Major

+

Major

The node process is faulty or the communications between the node and the DFV storage are abnormal.

+

A fault occurs when RDS is creating the standby DB instance or configuring replication between the primary and standby DB instances. The fault may occur because resources are insufficient in the data center where the standby DB instance is located.

Observe the instance and service running statuses.

+

Automatic retry is in progress.

A read replica may be promoted to the primary node.

+

Changing a single DB instance to primary/standby failed.

Node recovered

+

Database process restarted

TaurusNodeRunningStatusRecovered

+

DatabaseProcessRestarted

Major

+

Major

The node is recovered.

+

The database process is stopped due to insufficient memory or high load.

Observe the service running status.

+

Check whether services are running properly.

None

+

The primary instance is restarted. Services are interrupted for a short period of time.

Read replica deletion failure

+

Instance storage full

TaurusDeleteReadOnlyNodeFailed

+

instanceDiskFull

Major

+

Major

The communications between the management plane and the read replica are abnormal or the VM fails to be deleted from IaaS.

+

Generally, the cause is that the data space usage is too high.

Submit a service ticket.

+

Scale up the storage.

Read replicas fail to be deleted.

+

The instance storage is used up. No data can be written into databases.

Password reset failure

+

Instance storage full recovered

TaurusResetInstancePasswordFailed

+

instanceDiskFullRecovered

Major

+

Major

The communications between the management plane and the instance are abnormal or the instance is abnormal.

+

The instance disk is recovered.

Check the instance status and try again. If the fault persists, submit a service ticket.

+

Check whether services are running properly.

Passwords fail to be reset for instances.

+

The instance has available storage.

DB instance reboot failure

+

Kafka connection failed

TaurusRestartInstanceFailed

+

kafkaConnectionFailed

Major

+

Major

The network between the management plane and the instance is abnormal or the instance is abnormal.

+

The network is unstable or the Kafka server does not work properly.

Check the instance status and try again. If the fault persists, submit a service ticket.

+

Check whether services are affected.

Instances fail to be rebooted.

-

Restoration to new DB instance failure

-

TaurusRestoreToNewInstanceFailed

-

Major

-

The instance quota is insufficient, underlying resources are exhausted, or the data restoration logic is incorrect.

-

If the new instance fails to be created, check the instance quota, release resources, and try to restore to a new instance again. In other cases, submit a service ticket.

-

Backup data fails to be restored to new instances.

-

EIP binding failure

-

TaurusBindEIPToInstanceFailed

-

Major

-

The binding task fails.

-

Submit a service ticket.

-

EIPs fail to be bound to instances.

-

EIP unbinding failure

-

TaurusUnbindEIPFromInstanceFailed

-

Major

-

The unbinding task fails.

-

Submit a service ticket.

-

EIPs fail to be unbound from instances.

-

Parameter modification failure

-

TaurusUpdateInstanceParameterFailed

-

Major

-

The network between the management plane and the instance is abnormal or the instance is abnormal.

-

Check the instance status and try again. If the fault persists, submit a service ticket.

-

Instance parameters fail to be modified.

-

Parameter template application failure

-

TaurusApplyParameterGroupToInstanceFailed

-

Major

-

The network between the management plane and instances is abnormal or the instances are abnormal.

-

Check the instance status and try again. If the fault persists, submit a service ticket.

-

Parameter templates fail to be applied to instances.

-

Full backup failure

-

TaurusBackupInstanceFailed

-

Major

-

The network between the instance and the management plane (or the OBS) is disconnected, or the backup environment created for the instance is abnormal.

-

Submit a service ticket.

-

Backup jobs fail.

-

Primary/standby failover

-

TaurusActiveStandbySwitched

-

Major

-

When the network, physical machine, or database of the primary node is faulty, the system promotes a read replica to primary based on the failover priority to ensure service continuity.

-
  1. Check whether the service is running properly.
  2. Check whether an alarm is generated, indicating that the read replica failed to be promoted to primary.
-

During the failover, database connection is interrupted for a short period of time. After the failover is complete, you can reconnect to the database.

-

Database read-only

-

NodeReadonlyMode

-

Major

-

The database supports only query operations.

-

Submit a service ticket.

-

After the database becomes read-only, write operations cannot be processed.

-

Database read/write

-

NodeReadWriteMode

-

Major

-

The database supports both write and read operations.

-

Submit a service ticket.

-

None.

+

None
-
Table 6 GaussDB

Event Source

+
- - - - - - + - - - - - - - + - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 6 Document Database Service (DDS)

Event Source

Event Name

+

Namespace

Event ID

+

Event Name

Event Severity

+

Event ID

Description

+

Event Severity

Solution

+

Description

Impact

+

Solution

+

Impact

GaussDB

+

DDS

Process status alarm

+

SYS.DDS

ProcessStatusAlarm

+

DB instance creation failure

Major

+

DDSCreateInstanceFailed

Key processes exit, including CMS/CMA, ETCD, GTM, CN, and DN processes.

+

Major

Wait until the process is automatically recovered or a primary/standby failover is automatically performed. Check whether services are recovered. If no, contact SRE engineers.

+

A DDS instance fails to be created due to insufficient disks, quotas, and underlying resources.

If processes on primary nodes are faulty, services are interrupted and then rolled back. If processes on standby nodes are faulty, services are not affected.

+

Check the number and quota of disks. Release resources and create DDS instances again.

+

DDS instances cannot be created.

Component status alarm

+

Replication failed

ComponentStatusAlarm

+

DDSAbnormalReplicationStatus

Major

+

Major

Key components do not respond, including CMA, ETCD, GTM, CN, and DN components.

+

The possible causes are as follows:

+

The replication delay between the primary instance and the standby instance or a read replica is too long, which usually occurs when a large amount of data is being written to databases or a large transaction is being processed. During peak hours, data may be blocked.

+

The network between the primary instance and the standby instance or a read replica is disconnected.

Wait until the process is automatically recovered or a primary/standby failover is automatically performed. Check whether services are recovered. If no, contact SRE engineers.

+

Submit a service ticket.

If processes on primary nodes do not respond, neither do the services. If processes on standby nodes are faulty, services are not affected.

+

Your applications are not affected because this event does not interrupt data read and write.

Cluster status alarm

+

Replication recovered

ClusterStatusAlarm

+

DDSReplicationStatusRecovered

Major

+

Major

The cluster status is abnormal. For example, the cluster is read-only; majority of ETCDs are faulty; or the cluster resources are unevenly distributed.

+

The replication delay between the primary and standby instances is within the normal range, or the network connection between them has restored.

Contact SRE engineers.

+

No action is required.

If the cluster status is read-only, only read services are processed.

+

None

+

DB instance failed

+

DDSFaultyDBInstance

+

Major

+

This event is a key alarm event and is reported when an instance is faulty due to a disaster or a server failure.

+

Submit a service ticket.

+

The database service may be unavailable.

+

DB instance recovered

+

DDSDBInstanceRecovered

+

Major

+

If a disaster occurs, NoSQL provides an HA tool to automatically or manually rectify the fault. After the fault is rectified, this event is reported.

+

No action is required.

+

None

+

Faulty node

+

DDSFaultyDBNode

+

Major

+

This event is a key alarm event and is reported when a database node is faulty due to a disaster or a server failure.

+

Check whether the database service is available and submit a service ticket.

+

The database service may be unavailable.

+

Node recovered

+

DDSDBNodeRecovered

+

Major

+

If a disaster occurs, NoSQL provides an HA tool to automatically or manually rectify the fault. After the fault is rectified, this event is reported.

+

No action is required.

+

None

+

Primary/standby switchover or failover

+

DDSPrimaryStandbySwitched

+

Major

+

A primary/standby switchover is performed or a failover is triggered.

+

No action is required.

+

None

+

Insufficient storage space

+

DDSRiskyDataDiskUsage

+

Major

+

The storage space is insufficient.

+

Scale up storage space. For details, see section "Scaling Up Storage Space" in the corresponding user guide.

+

The instance is set to read-only and data cannot be written to the instance.

+

Data disk expanded and being writable

+

DDSDataDiskUsageRecovered

+

Major

+

The capacity of a data disk has been expanded and the data disk becomes writable.

+

No further action is required.

+

No adverse impact.

+

Schedule for deleting a KMS key

+

DDSplanDeleteKmsKey

+

Major

+

A request to schedule deletion of a KMS key was submitted.

+

After the KMS key is scheduled to be deleted, either decrypt the data encrypted by KMS key in a timely manner or cancel the key deletion.

+

After the KMS key is deleted, users cannot encrypt disks.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 7 GaussDB(for MySQL)

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

GaussDB(for MySQL)

+

SYS.GAUSSDB

+

+

Incremental backup failure

+

TaurusIncrementalBackupInstanceFailed

+

Major

+

The network between the instance and the management plane (or the OBS) is disconnected, or the backup environment created for the instance is abnormal.

+

Submit a service ticket.

+

Backup jobs fail.

+

Read replica creation failure

+

addReadonlyNodesFailed

+

Major

+

The quota is insufficient or underlying resources are exhausted.

+

Check the read replica quota. Release resources and create read replicas again.

+

Read replicas fail to be created.

+

DB instance creation failure

+

createInstanceFailed

+

Major

+

The instance quota or underlying resources are insufficient.

+

Check the instance quota. Release resources and create instances again.

+

DB instances fail to be created.

+

Read replica promotion failure

+

activeStandBySwitchFailed

+

Major

+

The read replica fails to be promoted to the primary node due to network or server failures. The original primary node takes over services quickly.

+

Submit a service ticket.

+

The read replica fails to be promoted to the primary node.

+

Instance specifications change failure

+

flavorAlterationFailed

+

Major

+

The quota is insufficient or underlying resources are exhausted.

+

Submit a service ticket.

+

Instance specifications fail to be changed.

+

Faulty DB instance

+

TaurusInstanceRunningStatusAbnormal

+

Major

+

The instance process is faulty or the communications between the instance and the DFV storage are abnormal.

+

Submit a service ticket.

+

Services may be affected.

+

DB instance recovered

+

TaurusInstanceRunningStatusRecovered

+

Major

+

The instance is recovered.

+

Observe the service running status.

+

None

+

Faulty node

+

TaurusNodeRunningStatusAbnormal

+

Major

+

The node process is faulty or the communications between the node and the DFV storage are abnormal.

+

Observe the instance and service running statuses.

+

A read replica may be promoted to the primary node.

+

Node recovered

+

TaurusNodeRunningStatusRecovered

+

Major

+

The node is recovered.

+

Observe the service running status.

+

None

+

Read replica deletion failure

+

TaurusDeleteReadOnlyNodeFailed

+

Major

+

The communications between the management plane and the read replica are abnormal or the VM fails to be deleted from IaaS.

+

Submit a service ticket.

+

Read replicas fail to be deleted.

+

Password reset failure

+

TaurusResetInstancePasswordFailed

+

Major

+

The communications between the management plane and the instance are abnormal or the instance is abnormal.

+

Check the instance status and try again. If the fault persists, submit a service ticket.

+

Passwords fail to be reset for instances.

+

DB instance reboot failure

+

TaurusRestartInstanceFailed

+

Major

+

The network between the management plane and the instance is abnormal or the instance is abnormal.

+

Check the instance status and try again. If the fault persists, submit a service ticket.

+

Instances fail to be rebooted.

+

Restoration to new DB instance failure

+

TaurusRestoreToNewInstanceFailed

+

Major

+

The instance quota is insufficient, underlying resources are exhausted, or the data restoration logic is incorrect.

+

If the new instance fails to be created, check the instance quota, release resources, and try to restore to a new instance again. In other cases, submit a service ticket.

+

Backup data fails to be restored to new instances.

+

EIP binding failure

+

TaurusBindEIPToInstanceFailed

+

Major

+

The binding task fails.

+

Submit a service ticket.

+

EIPs fail to be bound to instances.

+

EIP unbinding failure

+

TaurusUnbindEIPFromInstanceFailed

+

Major

+

The unbinding task fails.

+

Submit a service ticket.

+

EIPs fail to be unbound from instances.

+

Parameter modification failure

+

TaurusUpdateInstanceParameterFailed

+

Major

+

The network between the management plane and the instance is abnormal or the instance is abnormal.

+

Check the instance status and try again. If the fault persists, submit a service ticket.

+

Instance parameters fail to be modified.

+

Parameter template application failure

+

TaurusApplyParameterGroupToInstanceFailed

+

Major

+

The network between the management plane and instances is abnormal or the instances are abnormal.

+

Check the instance status and try again. If the fault persists, submit a service ticket.

+

Parameter templates fail to be applied to instances.

+

Full backup failure

+

TaurusBackupInstanceFailed

+

Major

+

The network between the instance and the management plane (or the OBS) is disconnected, or the backup environment created for the instance is abnormal.

+

Submit a service ticket.

+

Backup jobs fail.

+

Primary/standby failover

+

TaurusActiveStandbySwitched

+

Major

+

When the network, physical machine, or database of the primary node is faulty, the system promotes a read replica to primary based on the failover priority to ensure service continuity.

+
  1. Check whether the service is running properly.
  2. Check whether an alarm is generated, indicating that the read replica failed to be promoted to primary.
+

During the failover, database connection is interrupted for a short period of time. After the failover is complete, you can reconnect to the database.

+

Database read-only

+

NodeReadonlyMode

+

Major

+

The database supports only query operations.

+

Submit a service ticket.

+

After the database becomes read-only, write operations cannot be processed.

+

Database read/write

+

NodeReadWriteMode

+

Major

+

The database supports both write and read operations.

+

Submit a service ticket.

+

None.

+

Instance DR switchover

+

DisasterSwitchOver

+

Major

+

If an instance is faulty and unavailable, a switchover is performed to ensure that the instance continues to provide services.

+

Contact technical support.

+

The database connection is intermittently interrupted. The HA service switches workloads from the primary node to a read replica and continues to provide services.

+

Database process restarted

+

TaurusDatabaseProcessRestarted

+

Major

+

The database process is stopped due to insufficient memory or high load.

+

Log in to the Cloud Eye console. Check whether the memory usage increases sharply or the CPU usage is too high for a long time. You can increase the specifications or optimize the service logic.

+

When the database process is suspended, workloads on the node are interrupted. In this case, the HA service automatically restarts the database process and attempts to recover the workloads.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + +
Table 8 GaussDB

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

GaussDB

+

+

SYS.GAUSSDBV5

+

Process status alarm

+

ProcessStatusAlarm

+

Major

+

Key processes exit, including CMS/CMA, ETCD, GTM, CN, and DN processes.

+

Wait until the process is automatically recovered or a primary/standby failover is automatically performed. Check whether services are recovered. If no, contact SRE engineers.

+

If processes on primary nodes are faulty, services are interrupted and then rolled back. If processes on standby nodes are faulty, services are not affected.

+

Component status alarm

+

ComponentStatusAlarm

+

Major

+

Key components do not respond, including CMA, ETCD, GTM, CN, and DN components.

+

Wait until the process is automatically recovered or a primary/standby failover is automatically performed. Check whether services are recovered. If no, contact SRE engineers.

+

If processes on primary nodes do not respond, neither do the services. If processes on standby nodes are faulty, services are not affected.

+

Cluster status alarm

+

ClusterStatusAlarm

+

Major

+

The cluster status is abnormal. For example, the cluster is read-only; majority of ETCDs are faulty; or the cluster resources are unevenly distributed.

+

Contact SRE engineers.

+

If the cluster status is read-only, only read services are processed.

If the majority of ETCDs are fault, the cluster is unavailable.

If resources are unevenly distributed, the instance performance and reliability deteriorate.

Hardware resource alarm

+

Hardware resource alarm

HardwareResourceAlarm

+

HardwareResourceAlarm

Major

+

Major

A major hardware fault occurs in the instance, such as disk damage or GTM network fault.

+

A major hardware fault occurs in the instance, such as disk damage or GTM network fault.

Contact SRE engineers.

+

Contact SRE engineers.

Some or all services are affected.

+

Some or all services are affected.

Status transition alarm

+

Status transition alarm

StateTransitionAlarm

+

StateTransitionAlarm

Major

+

Major

The following events occur in the instance: DN build failure, forcible DN promotion, primary/standby DN switchover/failover, or primary/standby GTM switchover/failover.

+

The following events occur in the instance: DN build failure, forcible DN promotion, primary/standby DN switchover/failover, or primary/standby GTM switchover/failover.

Wait until the fault is automatically rectified and check whether services are recovered. If no, contact SRE engineers.

+

Wait until the fault is automatically rectified and check whether services are recovered. If no, contact SRE engineers.

Some services are interrupted.

+

Some services are interrupted.

Other abnormal alarm

+

Other abnormal alarm

OtherAbnormalAlarm

+

OtherAbnormalAlarm

Major

+

Major

Disk usage threshold alarm

+

Disk usage threshold alarm

Focus on service changes and scale up storage space as needed.

+

Focus on service changes and scale up storage space as needed.

If the used storage space exceeds the threshold, storage space cannot be scaled up.

+

If the used storage space exceeds the threshold, storage space cannot be scaled up.

Faulty DB instance

+

Faulty DB instance

TaurusInstanceRunningStatusAbnormal

+

TaurusInstanceRunningStatusAbnormal

Major

+

Major

This event is a key alarm event and is reported when an instance is faulty due to a disaster or a server failure.

+

This event is a key alarm event and is reported when an instance is faulty due to a disaster or a server failure.

Submit a service ticket.

+

Submit a service ticket.

The database service may be unavailable.

+

The database service may be unavailable.

DB instance recovered

+

DB instance recovered

TaurusInstanceRunningStatusRecovered

+

TaurusInstanceRunningStatusRecovered

Major

+

Major

GaussDB(openGauss) provides an HA tool for automated or manual rectification of faults. After the fault is rectified, this event is reported.

+

GaussDB(openGauss) provides an HA tool for automated or manual rectification of faults. After the fault is rectified, this event is reported.

No further action is required.

+

No further action is required.

None

+

None

Faulty DB node

+

Faulty DB node

TaurusNodeRunningStatusAbnormal

+

TaurusNodeRunningStatusAbnormal

Major

+

Major

This event is a key alarm event and is reported when a database node is faulty due to a disaster or a server failure.

+

This event is a key alarm event and is reported when a database node is faulty due to a disaster or a server failure.

Check whether the database service is available and submit a service ticket.

+

Check whether the database service is available and submit a service ticket.

The database service may be unavailable.

+

The database service may be unavailable.

DB node recovered

+

DB node recovered

TaurusNodeRunningStatusRecovered

+

TaurusNodeRunningStatusRecovered

Major

+

Major

GaussDB(openGauss) provides an HA tool for automated or manual rectification of faults. After the fault is rectified, this event is reported.

+

GaussDB(openGauss) provides an HA tool for automated or manual rectification of faults. After the fault is rectified, this event is reported.

No further action is required.

+

No further action is required.

None

+

None

DB instance creation failure

+

DB instance creation failure

GaussDBV5CreateInstanceFailed

+

GaussDBV5CreateInstanceFailed

Major

+

Major

Instances fail to be created because the quota is insufficient or underlying resources are exhausted.

+

Instances fail to be created because the quota is insufficient or underlying resources are exhausted.

Release the instances that are no longer used and try to provision them again, or submit a service ticket to adjust the quota.

+

Release the instances that are no longer used and try to provision them again, or submit a service ticket to adjust the quota.

DB instances cannot be created.

+

DB instances cannot be created.

Node adding failure

+

Node adding failure

GaussDBV5ExpandClusterFailed

+

GaussDBV5ExpandClusterFailed

Major

+

Major

The underlying resources are insufficient.

+

The underlying resources are insufficient.

Submit a service ticket. The O&M personnel will coordinate resources in the background, and then you delete the node that failed to be added and add a new node.

+

Submit a service ticket. The O&M personnel will coordinate resources in the background, and then you delete the node that failed to be added and add a new node.

None

+

None

Storage scale-up failure

+

Storage scale-up failure

GaussDBV5EnlargeVolumeFailed

+

GaussDBV5EnlargeVolumeFailed

Major

+

Major

The underlying resources are insufficient.

+

The underlying resources are insufficient.

Submit a service ticket. The O&M personnel will coordinate resources in the background and then you scale up the storage space again.

+

Submit a service ticket. The O&M personnel will coordinate resources in the background and then you scale up the storage space again.

Services may be interrupted.

+

Services may be interrupted.

Reboot failure

+

Reboot failure

GaussDBV5RestartInstanceFailed

+

GaussDBV5RestartInstanceFailed

Major

+

Major

The network is abnormal.

+

The network is abnormal.

Retry the reboot operation or submit a service ticket to the O&M personnel.

+

Retry the reboot operation or submit a service ticket to the O&M personnel.

The database service may be unavailable.

+

The database service may be unavailable.

Full backup failure

+

Full backup failure

GaussDBV5FullBackupFailed

+

GaussDBV5FullBackupFailed

Major

+

Major

The backup files fail to be exported or uploaded.

+

The backup files fail to be exported or uploaded.

Submit a service ticket to the O&M personnel.

+

Submit a service ticket to the O&M personnel.

Data cannot be backed up.

+

Data cannot be backed up.

Differential backup failure

+

Differential backup failure

GaussDBV5DifferentialBackupFailed

+

GaussDBV5DifferentialBackupFailed

Major

+

Major

The backup files fail to be exported or uploaded.

+

The backup files fail to be exported or uploaded.

Submit a service ticket to the O&M personnel.

+

Submit a service ticket to the O&M personnel.

Data cannot be backed up.

+

Data cannot be backed up.

Backup deletion failure

+

Backup deletion failure

GaussDBV5DeleteBackupFailed

+

GaussDBV5DeleteBackupFailed

Major

+

Major

This function does not need to be implemented.

+

This function does not need to be implemented.

N/A

+

N/A

N/A

+

N/A

EIP binding failure

+

EIP binding failure

GaussDBV5BindEIPFailed

+

GaussDBV5BindEIPFailed

Major

+

Major

The EIP is bound to another resource.

+

The EIP is bound to another resource.

Submit a service ticket to the O&M personnel.

+

Submit a service ticket to the O&M personnel.

The instance cannot be accessed from the Internet.

+

The instance cannot be accessed from the Internet.

EIP unbinding failure

+

EIP unbinding failure

GaussDBV5UnbindEIPFailed

+

GaussDBV5UnbindEIPFailed

Major

+

Major

The network is faulty or EIP is abnormal.

+

The network is faulty or EIP is abnormal.

Unbind the IP address again or submit a service ticket to the O&M personnel.

+

Unbind the IP address again or submit a service ticket to the O&M personnel.

IP addresses may be residual.

+

IP addresses may be residual.

Parameter template application failure

+

Parameter template application failure

GaussDBV5ApplyParamFailed

+

GaussDBV5ApplyParamFailed

Major

+

Major

Modifying a parameter template times out.

+

Modifying a parameter template times out.

Modify the parameter template again.

+

Modify the parameter template again.

None

+

None

Parameter modification failure

+

Parameter modification failure

GaussDBV5UpdateInstanceParamGroupFailed

+

GaussDBV5UpdateInstanceParamGroupFailed

Major

+

Major

Modifying a parameter template times out.

+

Modifying a parameter template times out.

Modify the parameter template again.

+

Modify the parameter template again.

None

+

None

Backup and restoration failure

+

Backup and restoration failure

GaussDBV5RestoreFromBcakupFailed

+

GaussDBV5RestoreFromBcakupFailed

Major

+

Major

The underlying resources are insufficient or backup files fail to be downloaded.

+

The underlying resources are insufficient or backup files fail to be downloaded.

Submit a service ticket.

+

Submit a service ticket.

The database service may be unavailable during the restoration failure.

+

The database service may be unavailable during the restoration failure.

+

Failed to upgrade the hot patch

+

GaussDBV5UpgradeHotfixFailed

+

Major

+

Generally, this fault is caused by an error reported during kernel upgrade.

+

View the error information about the workflow and redo or skip the job.

+

None

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 9 Distributed Database Middleware (DDM)

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

DDM

+

SYS.DDM

+

Failed to create a DDM instance

+

createDdmInstanceFailed

+

Major

+

The underlying resources are insufficient.

+

Release resources and create the instance again.

+

DDM instances cannot be created.

+

Failed to change class of a DDM instance

+

resizeFlavorFailed

+

Major

+

The underlying resources are insufficient.

+

Submit a service ticket to the O&M personnel to coordinate resources and try again.

+

Services on some nodes are interrupted.

+

Failed to scale out a DDM instance

+

enlargeNodeFailed

+

Major

+

The underlying resources are insufficient.

+

Submit a service ticket to the O&M personnel to coordinate resources, delete the node that fails to be added, and add a node again.

+

The instance fails to be scaled out.

+

Failed to scale in a DDM instance

+

reduceNodeFailed

+

Major

+

The underlying resources fail to be released.

+

Submit a service ticket to the O&M personnel to release resources.

+

The instance fails to be scaled in.

+

Failed to restart a DDM instance

+

restartInstanceFailed

+

Major

+

The DB instances associated are abnormal.

+

Check whether DB instances associated are normal. If the instances are normal, submit a service ticket to the O&M personnel.

+

Services on some nodes are interrupted.

+

Failed to create a schema

+

createLogicDbFailed

+

Major

+

The possible causes are as follows:

+
  • The password for the DB instance account is incorrect.
  • The security group of the DDM instance and the associated DB instance are incorrectly configured. As a result, the DDM instance cannot communicate with the associated DB instance.
+

Check whether

+
  • The username and password of the DB instance are correct.
  • The security groups associated with the DDM instance and underlying database instance are correctly configured.
+

Services cannot run properly.

+

Failed to bind an EIP

+

bindEipFailed

+

Major

+

The EIP is abnormal.

+

Try again later. In case of emergency, contact O&M personnel to rectify the fault.

+

The DDM instance cannot be accessed from the Internet.

+

Failed to scale out a schema

+

migrateLogicDbFailed

+

Major

+

The underlying resources fail to be processed.

+

Submit a service ticket to the O&M personnel.

+

The schema cannot be scaled out.

+

Failed to re-scale out a schema

+

retryMigrateLogicDbFailed

+

Major

+

The underlying resources fail to be processed.

+

Submit a service ticket to the O&M personnel.

+

The schema cannot be scaled out.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + +
Table 10 Layer 2 Connection Gateway (L2CG)

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

L2CG

+

SYS.ESW

+

IP addresses conflicted

+

IPConflict

+

Major

+

A cloud server and an on-premises server that need to communicate use the same IP address.

+

Check the ARP and switch information to locate the servers that have the same IP address and change the IP address.

+

The communications between the on-premises and cloud servers may be abnormal.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 11 Elastic IP and bandwidth

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Elastic IP and bandwidth

+

SYS.VPC

+

VPC deleted

+

deleteVpc

+

Major

+

VPC modified

+

modifyVpc

+

Minor

+

Subnet deleted

+

deleteSubnet

+

Minor

+

Subnet modified

+

modifySubnet

+

Minor

+

Bandwidth modified

+

modifyBandwidth

+

Minor

+

VPN deleted

+

deleteVpn

+

Major

+

VPN modified

+

modifyVpn

+

Minor

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 12 Elastic Volume Service (EVS)

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

EVS

+

SYS.EVS

+

Update disk

+

updateVolume

+

Minor

+

Update the name and description of an EVS disk.

+

No further action is required.

+

None

+

Expand disk

+

extendVolume

+

Minor

+

Expand an EVS disk.

+

No further action is required.

+

None

+

Delete disk

+

deleteVolume

+

Major

+

Delete an EVS disk.

+

No further action is required.

+

Deleted disks cannot be recovered.

+

QoS upper limit reached

+

reachQoS

+

Major

+

The I/O latency increases as the QoS upper limits of the disk are frequently reached and flow control triggered.

+

Change the disk type to one with a higher specification.

+

The current disk may fail to meet service requirements.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + +
Table 13 Key Management Service (KMS)

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

KMS

+

SYS.KMS

+

Key disabled

+

disableKey

+

Major

+

Key deletion scheduled

+

scheduleKeyDeletion

+

Minor

+

Grant retired

+

retireGrant

+

Major

+

Grant revoked

+

revokeGrant

+

Major

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + +
Table 14 Object Storage Service (OBS)

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

OBS

+

SYS.OBS

+

Bucket deleted

+

deleteBucket

+

Major

+

Bucket policy deleted

+

deleteBucketPolicy

+

Major

+

Bucket ACL configured

+

setBucketAcl

+

Minor

+

Bucket policy configured

+

setBucketPolicy

+

Minor

+
+
+ +
+ + + + + + + + + + + + + + + +
Table 15 Cloud Eye

Event Source

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Cloud Eye

+

Agent heartbeat interruption

+

agentHeartbeatInterrupted

+

Major

+

The Agent sends a heartbeat message to Cloud Eye every minute. If Cloud Eye cannot receive a heartbeat for 3 minutes, Agent Status is displayed as Faulty.

+
  • Confirm that the Agent domain name cannot be resolved.
  • Check whether your account is in arrears.
  • The Agent process is faulty. Restart the Agent. If the Agent process is still faulty after the restart, the Agent files may be damaged. In this case, reinstall the Agent.
  • Confirm that the server time is inconsistent with the local standard time.
  • Update the Agent to the latest version.
+
+
+ +
+ + + + + + + + + + + + + + + + + + + +
Table 16 DataSpace

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

Data Space

+

SYS.HWDS

+

New revision

+

newRevision

+

Minor

+

An updated version was released.

+

After receiving the notification, export the data of the updated version as required.

+

None.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 17 Distributed Cache Service (DCS)

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

DCS

+

SYS.DCS

+

Full sync retry during online migration

+

migrationFullResync

+

Minor

+

If online migration fails, full synchronization will be triggered because incremental synchronization cannot be performed.

+

Check whether full sync retries are triggered repeatedly. Check whether the source instance is connected and whether it is overloaded. If full sync retries are triggered repeatedly, contact O&M personnel.

+

The migration task is disconnected from the source instance, triggering another full sync. As a result, the CPU usage of the source instance may increase sharply.

+
  

masterStandbyFailover

+

Minor

+

The master node was abnormal, promoting a replica to master.

+		    

Memcached master/standby switchover

+

memcachedMasterStandbyFailover

+

Minor

+

The master node was abnormal, promoting the standby node to master.

+

Check whether services can recover by themselves. If applications cannot recover, restart them.

+

Persistent connections to the instance are interrupted.

+

Redis server abnormal

+

redisNodeStatusAbnormal

+

Major

+

The Redis server status was abnormal.

+

Check whether services are affected. If yes, contact O&M personnel.

+

If the master node is abnormal, an automatic failover is performed. If a standby node is abnormal and the client directly connects to the standby node for read/write splitting, no data can be read.

+

Redis server recovered

+

redisNodeStatusNormal

+

Major

+

The Redis server status recovered.

+

Check whether services can recover. If the applications are not reconnected, restart them.

+

Recover from an exception.

+

Sync failure in data migration

+

migrateSyncDataFail

+

Major

+

Online migration failed.

+

Reconfigure the migration task and migrate data again. If the fault persists, contact O&M personnel.

+

Data migration fails.

+

Memcached instance abnormal

+

memcachedInstanceStatusAbnormal

+

Major

+

The Memcached node status was abnormal.

+

Check whether services are affected. If yes, contact O&M personnel.

+

The Memcached instance is abnormal and may not be accessed.

+

Memcached instance recovered

+

memcachedInstanceStatusNormal

+

Major

+

The Memcached node status recovered.

+

Check whether services can recover. If the applications are not reconnected, restart them.

+

Recover from an exception.

+

Instance backup failure

+

instanceBackupFailure

+

Major

+

The DCS instance fails to be backed up due to an OBS access failure.

+

Retry backup manually.

+

Automated backup fails.

+

Instance node abnormal restart

+

instanceNodeAbnormalRestart

+

Major

+

DCS nodes restarted unexpectedly when they became faulty.

+

Check whether services can recover. If the applications are not reconnected, restart them.

+

Persistent connections to the instance are interrupted.

+

Long-running Lua scripts stopped

+

scriptsStopped

+

Informational

+

Lua scripts that had timed out automatically stopped running.

+

Optimize Lua scrips to prevent execution timeout.

+

If Lua scripts take a long time to execute, they will be forcibly stopped to avoid blocking the entire instance.

+

Node restarted

+

nodeRestarted

+

Informational

+

After write operations had been performed, the node automatically restarted to stop Lua scripts that had timed out.

+

Check whether services can recover by themselves. If applications cannot recover, restart them.

+

Persistent connections to the instance are interrupted.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 18 Intelligent Cloud Access (ICA)

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

ICA

+

SYS.ICA

+

BGP peer disconnection

+

BgpPeerDisconnection

+

Major

+

The BGP peer is disconnected.

+

Log in to the gateway and locate the cause.

+

Service traffic may be interrupted.

+

BGP peer connection success

+

BgpPeerConnectionSuccess

+

Major

+

The BGP peer is successfully connected.

+

None

+

None

+

Abnormal GRE tunnel status

+

AbnormalGreTunnelStatus

+

Major

+

The GRE tunnel status is abnormal.

+

Log in to the gateway and locate the cause.

+

Service traffic may be interrupted.

+

Normal GRE tunnel status

+

NormalGreTunnelStatus

+

Major

+

The GRE tunnel status is normal.

+

None

+

None

+

WAN interface goes up

+

EquipmentWanGoingOnline

+

Major

+

The WAN interface goes online.

+

None

+

None

+

WAN interface goes down

+

EquipmentWanGoingOffline

+

Major

+

The WAN interface goes offline.

+

Check whether the event is caused by a manual operation or device fault.

+

The device cannot be used.

+

Intelligent enterprise gateway going online

+

IntelligentEnterpriseGatewayGoingOnline

+

Major

+

The intelligent enterprise gateway goes online.

+

None

+

None

+

Intelligent enterprise gateway going offline

+

IntelligentEnterpriseGatewayGoingOffline

+

Major

+

The intelligent enterprise gateway goes offline.

+

Check whether the event is caused by a manual operation or device fault.

+

The device cannot be used.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 19 Multi-Site High Availability Service (MAS)

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

MAS

+

SYS.MAS

+

Abnormal database instance

+

dbError

+

Major

+

Abnormal database instance is detected by MAS.

+

Log in to the MAS console to view the cause and rectify the fault.

+

Services are interrupted.

+

Database instance recovered

+

dbRecovery

+

Major

+

The database instance is recovered.

+

None

+

Services are interrupted.

+

Abnormal Redis instance

+

redisError

+

Major

+

Abnormal Redis instance is detected by MAS.

+

Log in to the MAS console to view the cause and rectify the fault.

+

Services are interrupted.

+

Redis instance recovered

+

redisRecovery

+

Major

+

The Redis instance is recovered.

+

None

+

Services are interrupted.

+

Abnormal MongoDB database

+

mongodbError

+

Major

+

Abnormal MongoDB database is detected by MAS.

+

Log in to the MAS console to view the cause and rectify the fault.

+

Services are interrupted.

+

MongoDB database recovered

+

mongodbRecovery

+

Major

+

The MongoDB database is recovered.

+

None

+

Services are interrupted.

+

Abnormal Elasticsearch instance

+

esError

+

Major

+

Abnormal Elasticsearch instance is detected by MAS.

+

Log in to the MAS console to view the cause and rectify the fault.

+

Services are interrupted.

+

Elasticsearch instance recovered

+

esRecovery

+

Major

+

The Elasticsearch instance is recovered.

+

None

+

Services are interrupted.

+

Abnormal API

+

apiError

+

Major

+

The abnormal API is detected by MAS.

+

Log in to the MAS console to view the cause and rectify the fault.

+

Services are interrupted.

+

API recovered

+

apiRecovery

+

Major

+

The API is recovered.

+

None

+

Services are interrupted.

+

Area status changed

+

netChange

+

Major

+

Area status changes are detected by MAS.

+

Log in to the MAS console to view the cause and rectify the fault.

+

Network of the multi-active areas may change.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + +
Table 20 Config

Event Source

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

RMS

+

Configuration noncompliance notification

+

configurationNoncomplianceNotification

+

Major

+

The assignment evaluation result is Non-compliant.

+

Modify the noncompliant configuration items of the resource.

+

None

+

Configuration compliance notification

+

configurationComplianceNotification

+

Informational

+

The assignment evaluation result changed to be Compliant.

+

None

+

None

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 21 SecMaster

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

SecMaster

+

SYS.SecMaster

+

Exclusive engine creation failed

+

createEngineFailed

+

Major

+

The underlying resources are insufficient.

+

Submit a ticket to request sufficient resources from the O&M personnel and try again.

+

The exclusive engine cannot be created.

+

Exclusive engine exception

+

engineException

+

Critical

+

The traffic is too heavy or there are malicious processes or plug-ins.

+
  1. Check the executions of plug-ins and processes, see if they occupy too many resources.
  2. Check the instance monitoring information to see whether there is a sharp increase in the number of instances.
+

The instance cannot be executed.

+

Playbook instance execution failed

+

playbookInstanceExecFailed

+

Minor

+

Playbooks or processes are incorrectly configured.

+

Check the instance monitoring information to find the cause of the failure, and modify the playbook and process configuration.

+

None

+

Playbook instance increased sharply

+

playbookInstanceIncreaseSharply

+

Minor

+

Playbooks or processes are incorrectly configured.

+

Check the instance monitoring information to find the cause of the increase, and modify the playbook and process configuration.

+

None

+

Log messages increased sharply

+

logIncrease

+

Major

+

The upstream services suddenly generate a large number of log messages.

+

Check whether the upstream services are normal.

+

None

+

Log messages decreased sharply

+

logsDecrease

+

Major

+

Logs generated by the upstream services suddenly decrease.

+

Check whether the upstream services are normal.

+

None

+
+
+ +
+ + + + + + + + + + + + + + + + + + + +
Table 22 Key Pair Service

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

KPS

+

SYS.KPS

+

Key pair deleted

+

KPSDeleteKeypair

+

Informational

+

A key pair was deleted. This operation cannot be undone.

+

If this event occurred frequently within a short period of time, check whether malicious deletion took place.

+

Deleted key pairs cannot be restored.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 23 Host Security Service

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

HSS

+

SYS.HSS

+

HSS agent disconnected

+

hssAgentAbnormalOffline

+

Major

+

The communication between the agent and the server is abnormal, or the agent process on the server is abnormal.

+

Fix your network connection. If the agent is still offline for a long time after the network recovers, the agent process may be abnormal. In this case, log in to the server and restart the agent process.

+

Services are interrupted.

+

Abnormal HSS agent status

+

hssAgentAbnormalProtection

+

Major

+

The agent is abnormal probably because it does not have sufficient resources.

+

Log in to the server and check your resources. If the usage of memory or other system resources is too high, increase their capacity first. If the resources are sufficient but the fault persists after the agent process is restarted, submit a service ticket to the O&M personnel.

+

Services are interrupted.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 24 Image Management Service

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

IMS

+

SYS.IMS

+

Create Image

+

createImage

+

Major

+

An image was created.

+

None

+

You can use this image to create cloud servers.

+

Update Image

+

updateImage

+

Major

+

Metadata of an image was modified.

+

None

+

Cloud servers may fail to be created from this image.

+

Delete Image

+

deleteImage

+

Major

+

An image was deleted.

+

None

+

This image will be unavailable on the management console.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 25 Cloud Storage Gateway (CSG)

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

CSG

+

SYS.CSG

+

Abnormal CSG process status

+

gatewayProcessStatusAbnormal

+

Major

+

This event is triggered when an exception occurs in the CSG process status.

+

Abnormal CSG connection status

+

gatewayToServiceConnectAbnormal

+

Major

+

This event is triggered when no CSG status report is returned for five consecutive periods.

+

Abnormal connection status between CSG and OBS

+

gatewayToObsConnectAbnormal

+

Major

+

This event is triggered when CSG cannot connect to OBS.

+

Read-only file system

+

gatewayFileSystemReadOnly

+

Major

+

This event is triggered when the partition file system on CSG becomes read-only.

+

Read-only file share

+

gatewayFileShareReadOnly

+

Major

+

This event is triggered when the file share becomes read-only due to insufficient cache disk storage space.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 26 Global Accelerator

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

GA

+

SYS.GA

+

Anycast IP address blocked

+

blockAIP

+

Critical

+

The used bandwidth of an EIP exceeded 5 Gbit/s, the EIP were blocked and packets were discarded. Such an event may be caused by DDoS attacks.

+

Locate the root cause and rectify the fault.

+

Services are affected. The traffic will not be properly forwarded.

+

Anycast IP address unblocked

+

unblockAIP

+

Critical

+

The anycast IP address was unblocked.

+

Ensure that traffic can be properly forwarded.

+

None

+

Unhealthy endpoint

+

healthCheckError

+

Major

+

Health check detects the endpoint unhealthy.

+

Submit a service ticket.

+

+

If an endpoint is considered unhealthy, traffic will not be forwarded to it until the endpoint recovers.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 27 Cloud Certificate Manager (CCM)

Event Source

+

Namespace

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

CCM

+

SYS.CCM

+

Certificate revocation

+

CCMRevokeCertificate

+

Major

+

The certificate enters into the revocation process. Once revoked, the certificate cannot be used anymore.

+

Check whether the certificate revocation is really needed. Certificate revocation can be canceled.

+

If a certificate is revoked, the website is inaccessible using HTTPS.

+

Certificate auto-deployment failure

+

CCMAutoDeploymentFailure

+

Major

+

The certificate fails to be automatically deployed.

+

Check service resources whose certificates need to be replaced.

+

If no new certificate is deployed after a certificate expires, the website is inaccessible using HTTPS.

+

Certificate expiration

+

CCMCertificateExpiration

+

Major

+

An SSL certificate has expired.

+

Purchase a new certificate in a timely manner.

+

If no new certificate is deployed after a certificate expires, the website is inaccessible using HTTPS.

+

Certificate about to expire

+

CCMcertificateAboutToExpiration

+

Major

+

This alarm is generated when an SSL certificate is about to expire in one week, one month, and two months.

+

Renew or purchase a new certificate in a timely manner.

+

If no new certificate is deployed after a certificate expires, the website is inaccessible using HTTPS.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 28 Bare Metal Server (BMS)

Event Source

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

BMS

+

ECC uncorrectable errors generated on GPU SRAM

+

SRAMUncorrectableEccError

+

Major

+

There are ECC uncorrectable errors generated on GPU SRAM.

+

If services are affected, submit a service ticket.

+

The GPU hardware may be faulty. As a result, the GPU memory is faulty, and services exit abnormally.

+

osShutdown

+

osShutdown

+

Major

+

The BMS was stopped

+
  • on the management console.
  • by calling APIs.
+
  • Deploy service applications in HA mode.
  • After the BMS is started, check whether services recover.
+

Services are interrupted.

+

Abnormal shutdown

+

serverShutdown

+

Major

+

The BMS was stopped unexpectedly, which may be caused by

+
  • unexpected power-off.
  • hardware faults.
+
  • Deploy service applications in HA mode.
  • After the BMS is started, check whether services recover.
+

Services are interrupted.

+

Abnormal reboot

+

serverReboot

+

Major

+

The BMS restarted unexpectedly, which may be caused by

+
  • OS faults.
  • hardware faults.
+
  • Deploy service applications in HA mode.
  • After the BMS is restarted, check whether services recover.
+

Services are interrupted.

+

Network interruption

+

linkDown

+

Major

+

The BMS network was disconnected. Possible causes are as follows:

+
  • The BMS was unexpectedly stopped or restarted.
  • The switch was faulty.
  • The gateway was faulty.
+
  • Deploy service applications in HA mode.
  • After the BMS is started, check whether services recover.
+

Services are interrupted.

+

PCIE error

+

pcieError

+

Major

+

The PCIe devices or main board of the BMS was faulty.

+
  • Deploy service applications in HA mode.
  • After the BMS is started, check whether services recover.
+

The network or disk read/write services are affected.

+

Disk error

+

diskError

+

Major

+

The disk backplane or disks of the BMS were faulty.

+
  • Deploy service applications in HA mode.
  • After the fault is rectified, check whether services recover.
+

Data read/write services are affected, or the BMS cannot be started.

+

Storage error

+

storageError

+

Major

+

The BMS failed to connect to EVS disks. Possible causes are as follows:

+
  • The SDI card was faulty.
  • Remote storage devices were faulty.
+
  • Deploy service applications in HA mode.
  • After the fault is rectified, check whether services recover.
+

Data read/write services are affected, or the BMS cannot be started.

+

OS reboot

+

osReboot

+

Major

+

The BMS was restarted

+
  • on the management console.
  • by calling APIs.
+
  • Deploy service applications in HA mode.
  • After the BMS is restarted, check whether services recover.
+

Services are interrupted.

+

Inforom alarm generated on GPU

+

gpuInfoROMAlarm

+

Major

+

The driver failed to read inforom information due to GPU faults.

+

Non-critical services can continue to use the GPU card. For critical services, submit a service ticket to resolve this issue.

+

Services will not be affected if inforom information cannot be read. If error correction code (ECC) errors are reported on GPU, faulty pages may not be automatically retired and services are affected.

+

Double-bit ECC alarm generated on GPU

+

doubleBitEccError

+

Major

+

A double-bit ECC error occurred on GPU.

+
  1. If services are interrupted, restart the services to restore.
  2. If services cannot be restarted, restart the VM where services are running.
  3. If services still cannot be restored, submit a service ticket.
+

Services may be interrupted. After faulty pages are retired, the GPU card can continue to be used.

+

Too many retired pages

+

gpuTooManyRetiredPagesAlarm

+

Major

+

An ECC page retirement error occurred on GPU.

+

If services are affected, submit a service ticket.

+

Services may be affected.

+

ECC alarm generated on GPU A100

+

gpuA100EccAlarm

+

Major

+

An ECC error occurred on GPU.

+
  1. If services are interrupted, restart the services to restore.
  2. If services cannot be restarted, restart the VM where services are running.
  3. If services still cannot be restored, submit a service ticket.
+

Services may be interrupted. After faulty pages are retired, the GPU card can continue to be used.

+

GPU ECC memory page retirement failure

+

eccPageRetirementRecordingFailure

+

Major

+

Automatic page retirement failed due to ECC errors.

+
  1. If services are interrupted, restart the services to restore.
  2. If services cannot be restarted, restart the VM where services are running.
  3. If services still cannot be restored, submit a service ticket.
+

Services may be interrupted, and memory page retirement fails. As a result, services cannot no longer use the GPU card.

+

GPU ECC page retirement alarm generated

+

eccPageRetirementRecordingEvent

+

Minor

+

Memory pages are automatically retired due to ECC errors.

+
  1. If services are interrupted, restart the services to restore.
  2. If services cannot be restarted, restart the VM where services are running.
  3. If services still cannot be restored, submit a service ticket.
+

Generally, this alarm is generated together with the ECC error alarm. If this alarm is generated independently, services are not affected.

+

Too many single-bit ECC errors on GPU

+

highSingleBitEccErrorRate

+

Major

+

There are too many single-bit ECC errors.

+
  1. If services are interrupted, restart the services to restore.
  2. If services cannot be restarted, restart the VM where services are running.
  3. If services still cannot be restored, submit a service ticket.
+

Single-bit errors can be automatically rectified and do not affect GPU-related applications.

+

GPU card not found

+

gpuDriverLinkFailureAlarm

+

Major

+

A GPU link is normal, but the NVIDIA driver cannot find the GPU card.

+
  1. Restart the VM to restore services.
  2. If services still cannot be restored, submit a service ticket.
+

The GPU card cannot be found.

+

GPU link faulty

+

gpuPcieLinkFailureAlarm

+

Major

+

GPU hardware information cannot be queried through lspci due to a GPU link fault.

+

If services are affected, submit a service ticket.

+

The driver cannot use GPU.

+

GPU card lost

+

vmLostGpuAlarm

+

Major

+

The number of GPU cards on the VM is less than the number specified in the specifications.

+

If services are affected, submit a service ticket.

+

GPU cards get lost.

+

GPU memory page faulty

+

gpuMemoryPageFault

+

Major

+

The GPU memory page is faulty, which may be caused by applications, drivers, or hardware.

+

If services are affected, submit a service ticket.

+

The GPU hardware may be faulty. As a result, the GPU memory is faulty, and services exit abnormally.

+

GPU image engine faulty

+

graphicsEngineException

+

Major

+

The GPU image engine is faulty, which may be caused by applications, drivers, or hardware.

+

If services are affected, submit a service ticket.

+

The GPU hardware may be faulty. As a result, the image engine is faulty, and services exit abnormally.

+

GPU temperature too high

+

highTemperatureEvent

+

Major

+

GPU temperature too high

+

If services are affected, submit a service ticket.

+

If the GPU temperature exceeds the threshold, the GPU performance may deteriorate.

+

GPU NVLink faulty

+

nvlinkError

+

Major

+

A hardware fault occurs on the NVLink.

+

If services are affected, submit a service ticket.

+

The NVLink link is faulty and unavailable.

+

nvidia-smi suspended

+

nvidiaSmiHangEvent

+

Major

+

nvidia-smi timed out.

+

If services are affected, submit a service ticket.

+

The driver may report an error during service running.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 29 Elastic IP and bandwidth

Event Source

+

Event Name

+

Event ID

+

Event Severity

+

Elastic IP and bandwidth

+

Delete VPC

+

deleteVpc

+

Major

+

Modify VPC

+

modifyVpc

+

Minor

+

Delete subnet

+

deleteSubnet

+

Minor

+

Modify subnet

+

modifySubnet

+

Minor

+

Modify bandwidth

+

modifyBandwidth

+

Minor

+

Delete VPN

+

deleteVpn

+

Major

+

Modify VPN

+

modifyVpn

+

Minor

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 30 Cloud Phone Host (CPH)

Event Source

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

CPH

+

Server shutdown

+

cphServerOsShutdown

+

Major

+

The cloud phone server was stopped

+
  • on the management console.
  • by calling APIs.
+

Deploy service applications in HA mode.

+

After the fault is rectified, check whether services recover.

+

Services are interrupted.

+

Server abnormal shutdown

+

cphServerShutdown

+

Major

+

The cloud phone server was stopped unexpectedly. Possible causes are as follows:

+
  • The cloud phone server was powered off unexpectedly.
  • The cloud phone server was stopped due to hardware faults.
+

Deploy service applications in HA mode.

+

After the fault is rectified, check whether services recover.

+

Services are interrupted.

+

Server reboot

+

cphServerOsReboot

+

Major

+

The cloud phone server was rebooted

+
  • on the management console.
  • by calling APIs.
+

Deploy service applications in HA mode.

+

After the fault is rectified, check whether services recover.

+

Services are interrupted.

+

Server abnormal reboot

+

cphServerReboot

+

Major

+

The cloud phone server was rebooted unexpectedly due to

+
  • OS faults.
  • hardware faults.
+

Deploy service applications in HA mode.

+

After the fault is rectified, check whether services recover.

+

+

Services are interrupted.

+

Network interruption

+

cphServerlinkDown

+

Major

+

The network where the cloud phone server was deployed was disconnected. Possible causes are as follows:

+
  • The cloud phone server was stopped unexpectedly and rebooted.
  • The switch was faulty.
  • The gateway node was faulty.
+

Deploy service applications in HA mode.

+

After the fault is rectified, check whether services recover.

+

+

Services are interrupted.

+

PCIE error

+

cphServerPcieError

+

Major

+

The PCIe device or main board on the cloud phone server was faulty.

+

Deploy service applications in HA mode.

+

After the fault is rectified, check whether services recover.

+

+

The network or disk read/write is affected.

+

Disk error

+

cphServerDiskError

+

Major

+

The disk on the cloud phone server was faulty due to

+
  • disk backplane faults.
  • disk faults.
+

Deploy service applications in HA mode.

+

After the fault is rectified, check whether services recover.

+

+

Data read/write services are affected, or the BMS cannot be started.

+

Storage error

+

cphServerStorageError

+

Major

+

The cloud phone server could not connect to EVS disks. Possible causes are as follows:

+
  • SDI card faults
  • Remote storage devices were faulty.
+

Deploy service applications in HA mode.

+

After the fault is rectified, check whether services recover.

+

+

Data read/write services are affected, or the BMS cannot be started.

+

GPU offline

+

cphServerGpuOffline

+

Major

+

GPU of the cloud phone server was loose and disconnected.

+

Stop the cloud phone server and reboot it.

+

Faults occur on cloud phones whose GPUs are disconnected. Cloud phones cannot run properly even if they are restarted or reconfigured.

+

GPU timeout

+

cphServerGpuTimeOut

+

Major

+

GPU of the cloud phone server timed out.

+

Reboot the cloud phone server.

+

+

Cloud phones whose GPUs timed out cannot run properly and are still faulty even if they are restarted or reconfigured.

+

Disk full

+

cphServerDiskFull

+

Major

+

Disk space of the cloud phone server was used up.

+

Clear the application data in the cloud phone to release space.

+

+

Cloud phone is sub-healthy, prone to failure, and unable to start.

+

Disk readonly

+

cphServerDiskReadOnly

+

Major

+

The disk of the cloud phone server became read-only.

+

Reboot the cloud phone server.

+

+

Cloud phone is sub-healthy, prone to failure, and unable to start.

+

Phone metadata damage

+

cphPhoneMetaDataDamage

+

Major

+

Cloud phone metadata was damaged.

+

Contact O&M personnel.

+

The cloud phone cannot run properly even if it is restarted or reconfigured.

+

GPU failure

+

gpuAbnormal

+

Critical

+

The GPU was faulty.

+

Submit a service ticket.

+

Services are interrupted.

+

GPU back to normal

+

gpuNormal

+

Informational

+

The GPU was running properly.

+

No further action is required.

+

N/A

+

Kernel crash

+

kernelCrash

+

Critical

+

The kernel log indicated crash.

+

Submit a service ticket.

+

Services are interrupted during the crash.

+

Kernel OOM

+

kernelOom

+

Major

+

The kernel log indicated out of memory.

+

Submit a service ticket.

+

Services are interrupted.

+

Hardware malfunction

+

hardwareError

+

Critical

+

The kernel log indicated Hardware Error.

+

Submit a service ticket.

+

Services are interrupted.

+

PCIE error

+

pcieAer

+

Critical

+

The kernel log indicated PCIe Bus Error.

+

Submit a service ticket.

+

Services are interrupted.

+

SCSI error

+

scsiError

+

Critical

+

The kernel log indicated SCSI Error.

+

Submit a service ticket.

+

Services are interrupted.

+

Image storage became read-only

+

partReadOnly

+

Critical

+

The image storage became read-only.

+

Submit a service ticket.

+

Services are interrupted.

+

Image storage superblock damaged

+

badSuperBlock

+

Critical

+

The superblock of the file system of the image storage was damaged.

+

Submit a service ticket.

+

Services are interrupted.

+

Image storage /.sharedpath/master became read-only

+

isuladMasterReadOnly

+

Critical

+

Mount point /.sharedpath/master of the image storage became read-only.

+

Submit a service ticket.

+

Services are interrupted.

+

Cloud phone data disk became read-only

+

cphDiskReadOnly

+

Critical

+

The cloud phone data disk became read-only.

+

Submit a service ticket.

+

Services are interrupted.

+

Cloud phone data disk superblock damaged

+

cphDiskBadSuperBlock

+

Critical

+

The superblock of the file system of the cloud phone data disk was damaged.

+

Submit a service ticket.

+

Services are interrupted.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + +
Table 31 Object Storage Service (OBS)

Event Source

+

Event Name

+

Event ID

+

Event Severity

+

OBS

+

Delete bucket

+

deleteBucket

+

Major

+

Delete bucket policy

+

deleteBucketPolicy

+

Major

+

Set bucket ACL

+

setBucketAcl

+

Minor

+

Set bucket policy

+

setBucketPolicy

+

Minor

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 32 Enterprise connection

Event Source

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

EC

+

The WAN interface goes up

+

EquipmentWanGoesOnline

+

Major

+

The WAN interface goes online.

+

None

+

None

+

The WAN interface goes down

+

EquipmentWanGoesOffline

+

Major

+

The WAN interface goes offline.

+

Check whether the event is caused by a manual operation or device fault.

+

The device cannot be used.

+

BGP peer disconnection

+

BgpPeerDisconnection

+

Major

+

BGP peer disconnection

+

Check whether the event is caused by a manual operation or device fault.

+

The device cannot be used.

+

BGP peer connection success

+

BgpPeerConnectionSuccess

+

Major

+

The BGP peer is successfully connected.

+

None

+

None

+

Abnormal GRE tunnel status

+

AbnormalGreTunnelStatus

+

Major

+

Abnormal GRE tunnel status

+

Check whether the event is caused by a manual operation or device fault.

+

The device cannot be used.

+

Normal GRE tunnel status

+

NormalGreTunnelStatus

+

Major

+

The GRE tunnel status is normal.

+

None

+

None

+

The intelligent enterprise gateway goes online

+

IntelligentEnterpriseGatewayGoesOnline

+

Major

+

The intelligent enterprise gateway goes online.

+

None

+

None

+

The intelligent enterprise gateway goes offline

+

IntelligentEnterpriseGatewayGoesOffline

+

Major

+

The intelligent enterprise gateway goes offline.

+

Check whether the event is caused by a manual operation or device fault.

+

The device cannot be used.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 33 Elastic IP (EIP)

Event Source

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

EIP

+

EIP bandwidth overflow

+

EIPBandwidthOverflow

+

Major

+

The used bandwidth exceeded the purchased one, which may slow down the network or cause packet loss. The value of this event is the maximum value in a monitoring period, and the value of the EIP inbound and outbound bandwidth is the value at a specific time point in the period.

+

The metrics are described as follows:

+

egressDropBandwidth: dropped outbound packets (bytes)

+

egressAcceptBandwidth: accepted outbound packets (bytes)

+

egressMaxBandwidthPerSec: peak outbound bandwidth (byte/s)

+

ingressAcceptBandwidth: accepted inbound packets (bytes)

+

ingressMaxBandwidthPerSec: peak inbound bandwidth (byte/s)

+

ingressDropBandwidth: dropped inbound packets (bytes)

+

Check whether the EIP bandwidth keeps increasing and whether services are normal. Increase bandwidth if necessary.

+

The network becomes slow or packets are lost.

+

Delete EIP

+

deleteEip

+

Minor

+

The EIP was released.

+

Check whether the EIP was release by mistake.

+

The server that has the EIP bound cannot access the Internet.

+

EIP blocked

+

blockEIP

+

Critical

+

The used bandwidth of an EIP exceeded 5 Gbit/s, the EIP were blocked and packets were discarded. Such an event may be caused by DDoS attacks.

+

Replace the EIP to prevent services from being affected.

+

Locate and deal with the fault.

+

Services are impacted.

+

EIP unblocked

+

unblockEIP

+

Critical

+

The EIP was unblocked.

+

Use the previous EIP again.

+

None

+

Start DDoS traffic scrubbing

+

ddosCleanEIP

+

Major

+

Traffic scrubbing on the EIP was started to prevent DDoS attacks.

+

Check whether the EIP was attacked.

+

Services may be interrupted.

+

Stop DDoS traffic scrubbing

+

ddosEndCleanEip

+

Major

+

Traffic scrubbing on the EIP to prevent DDoS attacks was ended.

+

Check whether the EIP was attacked.

+

Services may be interrupted.

+

Enterprise-class QoS bandwidth limit exceeded

+

EIPBandwidthRuleOverflow

+

Major

+

The used QoS bandwidth exceeded the allocated one, which may slow down the network or cause packet loss. The value of this event is the maximum value in a monitoring period, and the value of the EIP inbound and outbound bandwidth is the value at a specific time point in the period.

+

egressDropBandwidth: dropped outbound packets (bytes)

+

egressAcceptBandwidth: accepted outbound packets (bytes)

+

egressMaxBandwidthPerSec: peak outbound bandwidth (byte/s)

+

ingressAcceptBandwidth: accepted inbound packets (bytes)

+

ingressMaxBandwidthPerSec: peak inbound bandwidth (byte/s)

+

ingressDropBandwidth: dropped inbound packets (bytes)

+

Check whether the EIP bandwidth keeps increasing and whether services are normal. Increase bandwidth if necessary.

+

The network becomes slow or packets are lost.

+
+
+ +
+ + + + + + + + + + + + + + + diff --git a/docs/ces/api-ref/ces_03_0001.html b/docs/ces/api-ref/ces_03_0001.html index f80d3318..62177ae3 100644 --- a/docs/ces/api-ref/ces_03_0001.html +++ b/docs/ces/api-ref/ces_03_0001.html @@ -1,7 +1,7 @@

API Usage Guidelines

-

Public cloud APIs comply with the RESTful API design principles. REST-based Web services are organized into resources. Each resource is identified by one or more Uniform Resource Identifiers (URIs). An application accesses a resource based on the resource's Unified Resource Locator (URL). A URL is usually in the following format: https://Endpoint/uri. In the URL,uri indicates the resource path, that is, the API access path.

+

Public cloud APIs comply with the RESTful API design principles. REST-based Web services are organized into resources. Each resource is identified by one or more Uniform Resource Identifiers (URIs). An application accesses a resource based on the resource's Unified Resource Locator (URL). A URL is usually in the following format: https://Endpoint/uri. In the URL, uri indicates the resource path, that is, the API access path.

Public cloud APIs use HTTPS as the transmission protocol. Requests/Responses are transmitted by using JSON messages, with media type represented by Application/json.

For details about how to use APIs, see API Usage Guidelines.

An endpoint is the request address for calling an API. Endpoints vary depending on services and regions. For example, the endpoint of the eu-de region is ces.eu-de.otc.t-systems.com. For the endpoints of all services, see Regions and Endpoints.

diff --git a/docs/ces/api-ref/ces_03_0023.html b/docs/ces/api-ref/ces_03_0023.html index a08d2fb3..5cae2030 100644 --- a/docs/ces/api-ref/ces_03_0023.html +++ b/docs/ces/api-ref/ces_03_0023.html @@ -2,6 +2,8 @@

Querying Metrics

Function

This API is used to query metrics supported by Cloud Eye. You can specify the namespace, metric, dimension, sorting order, start records, and the maximum number of records when using this API to query metrics.

+

After a cloud service resource is deleted, its data is cached for 3 hours, so metrics of the resource can still be queried within the 3 hours.

+

URI

GET /V1.0/{project_id}/metrics

  • Parameter description @@ -41,7 +43,7 @@
- diff --git a/docs/ces/api-ref/ces_03_0027.html b/docs/ces/api-ref/ces_03_0027.html index b72cc101..a147a431 100644 --- a/docs/ces/api-ref/ces_03_0027.html +++ b/docs/ces/api-ref/ces_03_0027.html @@ -102,7 +102,7 @@

Request

None

Response

  • Response parameters -
Table 34 Enterprise Switch

Event Source

+

Event Name

+

Event ID

+

Event Severity

+

Description

+

Solution

+

Impact

+

Enterprise Switch

+

IP Address Conflict

+

IPConflict

+

Major

+

A cloud server and an on-premises server that need to communicate use the same IP address.

+

Check the ARP and switch information to locate the servers that have the same IP address and change the IP address.

+

The communications between the on-premises and cloud servers may be abnormal.

String

Query the namespace of a service. For details, see Services Interconnected with Cloud Eye.

+

Specifies the namespace of a service. For details, see Services Interconnected with Cloud Eye.

The namespace must be in the service.item format and contain 3 to 32 characters. service and item each must start with a letter and contain only letters, digits, and underscores (_).

Table 4 Response parameters

Parameter

+
@@ -406,7 +406,7 @@ - - -
Table 4 Parameter description

Parameter

Type

Integer

Specifies the interval for triggering an alarm if the alarm persists.

+

Specifies the interval for triggering an alarm if the alarm persists.

Possible intervals are as follows:

0: Cloud Eye triggers the alarm only once.

300: Cloud Eye triggers the alarm every 5 minutes.

diff --git a/docs/ces/api-ref/ces_03_0028.html b/docs/ces/api-ref/ces_03_0028.html index 0e6cb9c8..38d08139 100644 --- a/docs/ces/api-ref/ces_03_0028.html +++ b/docs/ces/api-ref/ces_03_0028.html @@ -334,7 +334,7 @@

Integer

Specifies the interval for triggering an alarm if the alarm persists.

+

Specifies the interval for triggering an alarm if the alarm persists.

Possible intervals are as follows:

0: Cloud Eye triggers the alarm only once.

300: Cloud Eye triggers the alarm every 5 minutes.

diff --git a/docs/ces/api-ref/ces_03_0031.html b/docs/ces/api-ref/ces_03_0031.html index 2660fd8e..d321824b 100644 --- a/docs/ces/api-ref/ces_03_0031.html +++ b/docs/ces/api-ref/ces_03_0031.html @@ -388,14 +388,14 @@

Integer

Specifies the interval for triggering an alarm if the alarm persists.

+

Specifies the interval for triggering an alarm if the alarm persists.

Possible intervals are as follows:

0: Cloud Eye triggers the alarm only once.

300: Cloud Eye triggers the alarm every 5 minutes.

-

600: Cloud Eye triggers the alarm every 10 minutes.

+

600: Cloud Eye triggers the alarm every 10 minutes.

900: Cloud Eye triggers the alarm every 15 minutes.

1800: Cloud Eye triggers the alarm every 30 minutes.

-

3600: Cloud Eye triggers the alarm every hour.

+

3600: Cloud Eye triggers the alarm every hour.

10800: Cloud Eye triggers the alarm every 3 hours.

21600: Cloud Eye triggers the alarm every 6 hours.

43200: Cloud Eye triggers the alarm every 12 hours.

@@ -484,8 +484,8 @@ } -

Response

  • Response parameters -
    Table 8 Response parameters

    Parameter

    +

    Response

    • Response parameter +
      diff --git a/docs/ces/api-ref/ces_03_0033.html b/docs/ces/api-ref/ces_03_0033.html index 83c76b2e..d79aa592 100644 --- a/docs/ces/api-ref/ces_03_0033.html +++ b/docs/ces/api-ref/ces_03_0033.html @@ -85,8 +85,8 @@
      Table 8 Parameter description

      Parameter

      Type

      Integer

      Specifies how often Cloud Eye aggregates data, which can be

      -
      • 1: Cloud Eye displays raw data.
      -
      • 300: Cloud Eye aggregates data every 5 minutes.
      • 1200: Cloud Eye aggregates data every 20 minutes.
      • 3600: Cloud Eye aggregates data every 1 hour.
      • 14400: Cloud Eye aggregates data every 4 hours.
      • 86400: Cloud Eye aggregates data every 24 hours.
      +
      • 1: Cloud Eye performs no aggregation and displays raw data.
      +
      • 300: Cloud Eye aggregates data every 5 minutes.
      • 1200: Cloud Eye aggregates data every 20 minutes.
      • 3600: Cloud Eye aggregates data every hour.
      • 14400: Cloud Eye aggregates data every 4 hours.
      • 86400: Cloud Eye aggregates data every 24 hours.

      filter

      @@ -127,7 +127,7 @@

      Request

      None

      Response

      • Response parameters -
        Table 3 Response parameters

        Parameter

        +
        @@ -155,11 +155,11 @@
        Table 3 Parameter description

        Parameter

        Type

        -
        Table 4 datapoints data structure description

        Parameter

        +
        - - @@ -270,7 +270,7 @@ -
        Table 4 datapoints data structure description

        Parameter

        Type

        +

        Type

        Description

        +

        Description

        403 Forbidden

        You are forbidden to access the page requested.

        +

        Access to the requested page is forbidden.

        408 Request Timeout

        diff --git a/docs/ces/api-ref/ces_03_0034.html b/docs/ces/api-ref/ces_03_0034.html index 31bdd961..d13e711c 100644 --- a/docs/ces/api-ref/ces_03_0034.html +++ b/docs/ces/api-ref/ces_03_0034.html @@ -27,11 +27,11 @@

        Request

        1. The size of a POST request cannot exceed 512 KB. Otherwise, the request will be denied.
        2. The default maximum query intervals of different periods are different.

          If period is 1, the maximum interval between from and to is 4 hours. If the interval between from and to is longer than 4 hours, adjust the value of from to to - 4*3600*1000.

          -

          If period is 300, the maximum interval between from and to is one day. If the interval between from and to is longer than 1 day, adjust the value of from to to - 24*3600*1000.

          -

          If period is 1200, the maximum interval between from and to is three days. If the interval between from and to is longer than three days, adjust the value of from to to - 3*24*3600*1000.

          -

          If period is 3600, the maximum interval between from and to is 10 days. If the interval between from and to is longer than 10 days, adjust the value of from to to - 10*24*3600*1000.

          -

          If period is 14400, the maximum interval between from and to is 30 days. If the interval between from and to is longer than 30 days, adjust the value of from to to - 30*24*3600*1000.

          -

          If period is 86400, the maximum interval between from and to is 180 days. If the interval between from and to is longer than 180 days, adjust the value of from to to - 180*24*3600*1000.

          +

          If period is 300, the maximum interval between from and to is one day. If the interval between from and to is longer than one day, adjust the value of from to to - 24*3600*1000.

          +

          If period is 1200, the maximum interval between from and to is three days. If the interval between from and to is longer than three days, adjust the value of from to to - 3*24*3600*1000.

          +

          If period is 3600, the maximum interval between from and to is 10 days. If the interval between from and to is longer than 10 days, adjust the value of from to to - 10*24*3600*1000.

          +

          If period is 14400, the maximum interval between from and to is 30 days. If the interval between from and to is longer than 30 days, adjust the value of from to to - 30*24*3600*1000.

          +

          If period is 86400, the maximum interval between from and to is 180 days. If the interval between from and to is longer than 180 days, adjust the value of from to to - 180*24*3600*1000.

        • Request parameters @@ -100,13 +100,13 @@
        -
        Table 3 metrics data structure description

        Parameter

        +
        - - - @@ -116,11 +116,21 @@ - - + + + + + @@ -135,26 +145,17 @@

        For details, see Table 4.

        - - - - -
        Table 3 metrics data structure description

        Parameter

        Mandatory

        +

        Mandatory

        Type

        +

        Type

        Description

        +

        Description

        String

        Specifies the metric namespace, which must be in the service.item format and contain 3 to 32 characters.

        -

        service and item each must start with a letter and contain only letters, digits, and underscores (_).

        +

        Specifies the namespace of a service. For details, see Services Interconnected with Cloud Eye.

        +

        The namespace must be in the service.item format and contain 3 to 32 characters. service and item each must start with a letter and contain only letters, digits, and underscores (_).

        dimensions

        +

        metric_name

        +

        Yes

        +

        String

        +

        Specifies the metric ID. For example, if the monitoring metric of an ECS is CPU usage, metric_name is cpu_util. For details, see Services Interconnected with Cloud Eye.

        +

        The value must start with a letter. Enter 1 to 64 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed.

        +

        dimensions

        Yes

        metric_name

        -

        Yes

        -

        String

        -

        Specifies the metric name. Start with a letter. Enter 1 to 64 characters. Only letters, digits, and underscores (_) are allowed.

        -
        -
        Table 4 dimensions data structure description

        Parameter

        +
        - - - @@ -174,17 +175,110 @@ -
        Table 4 dimensions data structure description

        Parameter

        Mandatory

        +

        Mandatory

        Type

        +

        Type

        Description

        +

        Description

        String

        Specifies the dimension value, for example, an ECS ID.

        +

        Specifies the dimension value, for example, an ECS ID. dimensions can be obtained from the response body by calling the API for querying metrics.

        Start with a letter or a digit. Enter 1 to 256 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed.
        -
        • dimensions can be obtained from the response body by calling the API for Querying Metrics.
        • OBS metric data can be queried only when the related OBS APIs are called.
        +
        • dimensions can be obtained from the response body by calling the API for querying metrics.
        • OBS metric data can be queried only when the related OBS APIs are called.
        -
        • Example request
          Request example 1: View the average cpu_util of the ECS whose instance_id is faea5b75-e390-4e2b-8733-9226a9026070 and the average network_vm_connections of the ECS whose instance_id is 06b4020f-461a-4a52-84da-53fa71c2f42b. The monitoring data was collected from 20:00:00 to 22:00:00 on April 30, 2019.
          {
+
          • Example request
            Request example 1: Query the average disk usage of the OS on the ECS whose instance_id is 07d878a9-2243-4e84-aeef-c47747d18024 and mount_point is 012bec14bc176310c19f40e384fd629b from 20:00:00 to 22:00:00 on April 30, 2019.
            
+
            {
+	"from": 1556625600000,
+	"to": 1556632800000,
+	"period": "1",
+	"filter": "average",
+	"metrics": [{
+		"dimensions": [{
+			"name": "instance_id",
+			"value": "07d878a9-2243-4e84-aeef-c47747d18024"
+		}, {
+			"name": "mount_point",
+			"value": "012bec14bc176310c19f40e384fd629b"
+		}],
+		"metric_name": "disk_usedPercent",
+		"namespace": "AGT.ECS"
+	}]
+}
            
+
            Request example 2: Query the average memory usage of the OS of the ECS whose instance_id is 238764d4-c4e1-4274-88a1-5956b057766b from 20:00:00 to 22:00:00 on April 30, 2019.
            
+
            {
+	"from": 1556625600000,
+	"to": 1556632800000,
+	"period": "1",
+	"filter": "average",
+	"metrics": [{
+		"dimensions": [{
+			"name": "instance_id",
+			"value": "238764d4-c4e1-4274-88a1-5956b057766b"
+		}],
+		"metric_name": "mem_usedPercent",
+		"namespace": "AGT.ECS"
+	}]
+}
            
+
            Request example 3: Query the average cpu_util of the five ECSs whose instance_id are faea5b75-e390-4e2b-8733-9226a9026070, faea5b75-e390-4e2b-8733-9226a9026071, faea5b75-e390-4e2b-8733-9226a9026072, faea5b75-e390-4e2b-8733-9226a9026073, and faea5b75-e390-4e2b-8733-9226a9026074 from 00:00:00 to 23:59:59 on August 21, 2024. Query five metrics. The monitoring period is 60,000 ms. The maximum value of (to-from) is 36,000,000. The value of the request parameter (to-from) is 86,399,000, which exceeds the maximum value 36,000,000. The formula is as follows: The number of metrics × (to-from)/Monitoring period ≤ 3000. The value of from in the request parameter is automatically changed to to-36,000,000, that is, 1,724,219,999,000.
            
+
            {
+    "metrics": [
+       {
+            "namespace": "SYS.ECS",
+            "dimensions": [
+                {
+                    "name": "instance_id",
+                    "value": "faea5b75-e390-4e2b-8733-9226a9026070"
+                }
+            ],
+            "metric_name": "cpu_util"
+        },
+       {
+            "namespace": "SYS.ECS",
+            "dimensions": [
+                {
+                    "name": "instance_id",
+                    "value": "faea5b75-e390-4e2b-8733-9226a9026071"
+                }
+            ],
+            "metric_name": "cpu_util"
+        },
+		       {
+            "namespace": "SYS.ECS",
+            "dimensions": [
+                {
+                    "name": "instance_id",
+                    "value": "faea5b75-e390-4e2b-8733-9226a9026072"
+                }
+            ],
+            "metric_name": "cpu_util"
+        },
+		       {
+            "namespace": "SYS.ECS",
+            "dimensions": [
+                {
+                    "name": "instance_id",
+                    "value": "faea5b75-e390-4e2b-8733-9226a9026073"
+                }
+            ],
+            "metric_name": "cpu_util"
+        },
+		       {
+            "namespace": "SYS.ECS",
+            "dimensions": [
+                {
+                    "name": "instance_id",
+                    "value": "faea5b75-e390-4e2b-8733-9226a9026074"
+                }
+            ],
+            "metric_name": "cpu_util"
+        },
+    ], 
+    "from": 1724169600000,
+    "to": 1724255999000,
+    "period": "1",
+    "filter": "average"
+}
+
            
+
            Request example 4: View the average cpu_util of the ECS whose instance_id is faea5b75-e390-4e2b-8733-9226a9026070 and the average network_vm_connections of the ECS whose instance_id is 06b4020f-461a-4a52-84da-53fa71c2f42b. The monitoring data was collected from 20:00:00 to 22:00:00 on April 30, 2019.
            {
     "metrics": [
        {
             "namespace": "SYS.ECS",
@@ -214,7 +308,7 @@
 }
 
            
 
            
-
            Request example 2: View the sums of rds021_myisam_buf_usage of the RDS instance whose rds_cluster_id is 3c8cc15614ab46f5b8743317555e0de2in01 and the RDS instance whose rds_cluster_id is 3b2fa8b55a9b4adca3713962a9d31884in01. The monitoring data was collected from 20:00:00 to 22:00:00 on April 30, 2019.
            {
+
            Request example 5: View the sums of rds021_myisam_buf_usage of the RDS instance whose rds_cluster_id is 3c8cc15614ab46f5b8743317555e0de2in01 and the RDS instance whose rds_cluster_id is 3b2fa8b55a9b4adca3713962a9d31884in01. The monitoring data was collected from 20:00:00 to 22:00:00 on April 30, 2019.
            {
     "metrics": [
         {
             "namespace": "SYS.RDS",
@@ -243,7 +337,7 @@
     "filter": "sum"
 }
            
 
            
-
            Example request 3: View the minimum proc_specified_count of the server whose instance_id is cd841102-f6b1-407d-a31f-235db796dcbb and proc is b28354b543375bfa94dabaeda722927f. The monitoring data is collected from 20:00:00 to 22:00:00 on April 30, 2019 and the rollup period is 20 minutes.
            {
+
            Example request 6: View the minimum proc_specified_count of the server whose instance_id is cd841102-f6b1-407d-a31f-235db796dcbb and proc is b28354b543375bfa94dabaeda722927f. The monitoring data is collected from 20:00:00 to 22:00:00 on April 30, 2019 and the rollup period is 20 minutes.
            {
     "metrics": [
         {
             "namespace": "AGT.ECS",
@@ -269,9 +363,9 @@

          Response

          • Response parameters -
            Table 5 Response parameters

            Parameter

            +
            - @@ -289,11 +383,11 @@
            Table 5 Parameter description

            Parameter

            Type

            +

            Type

            Description

            -
            Table 6 metrics data structure description

            Parameter

            +
            - - @@ -343,11 +437,11 @@
            Table 6 metrics data structure description

            Parameter

            Type

            +

            Type

            Description

            +

            Description
            -
            Table 7 dimensions data structure description

            Parameter

            +
            - - @@ -371,11 +465,11 @@
            Table 7 dimensions data structure description

            Parameter

            Type

            +

            Type

            Description

            +

            Description
            -
            Table 8 datapoints data structure description

            Parameter

            +
            - - diff --git a/docs/ces/api-ref/ces_03_0035.html b/docs/ces/api-ref/ces_03_0035.html index 986e554c..f826f3b7 100644 --- a/docs/ces/api-ref/ces_03_0035.html +++ b/docs/ces/api-ref/ces_03_0035.html @@ -43,7 +43,7 @@ - @@ -99,7 +99,7 @@

            Request

            None

            Response

            • Response parameters -
            Table 8 datapoints data structure description

            Parameter

            Type

            +

            Type

            Description

            +

            Description

            String

            Query the namespace of a service. For details, see Services Interconnected with Cloud Eye.

            +

            Specifies the namespace of a service. For details, see Services Interconnected with Cloud Eye.

            The namespace must be in the service.item format and contain 3 to 32 characters. service and item each must start with a letter and contain only letters, digits, and underscores (_).
            Table 2 Response parameters

            Parameter

            +
            @@ -188,7 +188,7 @@ -
            Table 2 Parameter description

            Parameter

            Type

            403 Forbidden

            You are forbidden to access the page requested.

            +

            Access to the requested page is forbidden.

            408 Request Timeout

            diff --git a/docs/ces/api-ref/ces_03_0057.html b/docs/ces/api-ref/ces_03_0057.html index 88f709d7..ea76e537 100644 --- a/docs/ces/api-ref/ces_03_0057.html +++ b/docs/ces/api-ref/ces_03_0057.html @@ -5,7 +5,7 @@

            Obtain the Project ID by Calling an API

            You can obtain the project ID by calling the IAM API used to query project information based on the specified criteria.

            -

            The API used to obtain a project ID is GET https://{Endpoint}/v3/projects. {Endpoint} is the IAM endpoint and can be obtained from Regions and Endpoints.

            +

            The API used to obtain a project ID is GET https://{Endpoint}/v3/projects. {Endpoint} is the IAM endpoint and can be obtained from Regions and Endpoints.

            The following is an example response. The value of id is the project ID.

            {
     "projects": [
@@ -32,7 +32,7 @@
 }

            Obtain a Project ID from the Console

            A project ID needs to be specified in the URIs of some APIs. Therefore, you need to obtain the project ID before calling APIs. The following procedure describes how to obtain a project ID:
            1. Log in to the management console.
            2. Click the username and select My Credentials from the drop-down list.

              On the My Credentials page, view project IDs in the project list.

              -
              Figure 1 Viewing project IDs
              +
              Figure 1 Viewing project IDs

              In multi-project scenarios, expand the region, and obtain your sub-project ID from the Project ID column.

            @@ -44,3 +44,10 @@
            + + \ No newline at end of file diff --git a/docs/ces/api-ref/ces_03_0059.html b/docs/ces/api-ref/ces_03_0059.html index 7ff81be5..1b7d66af 100644 --- a/docs/ces/api-ref/ces_03_0059.html +++ b/docs/ces/api-ref/ces_03_0059.html @@ -2,267 +2,191 @@

            Services Interconnected with Cloud Eye

            -

            Category

            +
            - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/ces/api-ref/ces_03_0060.html b/docs/ces/api-ref/ces_03_0060.html index 472b1cec..b7d1f717 100644 --- a/docs/ces/api-ref/ces_03_0060.html +++ b/docs/ces/api-ref/ces_03_0060.html @@ -8,7 +8,13 @@ - + + + -

            Category

            Service

            +

            Service

            Namespace

            +

            Namespace

            Dimension

            -

            Reference

            +

            Reference

            Compute

            +

            Compute

            Elastic Cloud Server

            +

            Elastic Cloud Server

            SYS.ECS

            +

            SYS.ECS

            Key: instance_id

            -

            Value: ECS ID

            -

            Basic ECS metrics

            +

            Basic ECS metrics

            Bare Metal Server

            +

            Bare Metal Server

            SERVICE.BMS

            +

            SERVICE.BMS

            Key: instance_id

            -

            Value: ECS ID

            -

            BMS metrics (with the Agent installed)

            +

            BMS metrics (with the Agent installed)

            Auto Scaling

            +

            Auto Scaling

            SYS.AS

            +

            SYS.AS

            Key: AutoScalingGroup

            -

            Value: auto scaling group ID

            -

            AS metrics

            +

            AS metrics

            Storage

            +

            Storage

            Elastic Volume Service (attached to an ECS or BMS)

            +

            Elastic Volume Service (attached to an ECS or BMS)

            SYS.EVS

            +

            SYS.EVS

            Key: disk_name

            -

            Value: server ID-drive letter (sda is the drive letter.)

            -

            EVS metrics

            +

            EVS metrics

            Object Storage Service (OBS)

            +

            Object Storage Service

            SYS.OBS

            +

            SYS.OBS

            Key: bucket_name

            -

            Value: bucket name

            -

            OBS metrics

            +

            OBS metrics

            Scalable File Service

            +

            Scalable File Service

            SYS.SFS

            +

            SYS.SFS

            Key: share_id

            -

            Value: SFS file system

            -

            SFS metrics

            +

            SFS metrics

            SFS Turbo

            +

            SFS Turbo

            SYS.EFS

            +

            SYS.EFS

            Key: efs_instance_id

            -

            Value: instance

            -

            SFS Turbo metrics

            +

            SFS Turbo metrics

            Cloud Backup and Recovery

            +

            Cloud Backup and Recovery

            SYS.CBR

            +

            SYS.CBR

            -

            Vault: vault name/ID

            -

            CBR metrics

            +

            CBR metrics

            Network

            +

            Network

            Elastic IP and bandwidth

            +

            Elastic IP and bandwidth

            SYS.VPC

            +

            SYS.VPC

            • Key: publicip_id

              Value: EIP ID

              -
            • Key: bandwidth_id

              Value: bandwidth ID

              -
            -

            VPC metrics

            +

            VPC metrics

            Elastic Load Balance

            +

            Elastic Load Balance

            SYS.ELB

            +

            SYS.ELB

            • Key: lbaas_instance_id

              Value: ID of a dedicated or shared load balancer

              -
            • Key: lbaas_listener_id

              Value: ID of a dedicated or shared load balancer listener

              -
            -

            ELB metrics

            +

            ELB metrics

            Direct Connect

            +

            Direct Connect

            SYS.DCAAS

            +

            SYS.DCAAS

            • Key: direct_connect_id

              Value: connection

              -
            • Key: virtual_interface_id

              Value: virtual interface

              -
            -

            Direct Connect metrics

            +

            Direct Connect metrics

            NAT Gateway

            +

            NAT Gateway

            SYS.NAT

            +

            SYS.NAT

            • Key: nat_gateway_id

              Value: NAT gateway ID

              -
            -

            NAT Gateway metrics

            +

            NAT Gateway metrics

            Security

            +

            Security

            Web Application Firewall

            +

            Web Application Firewall

            SYS.WAF

            +

            SYS.WAF

            • Key: waf_instance_id

              Value: cloud WAF instance

              -
            -

            WAF metrics

            +

            WAF metrics

            Application

            +

            Application

            Distributed Message Service

            +

            Distributed Message Service

            SYS.DMS

            +

            SYS.DMS

            For details, see the information in the right column.

            -

            DMS metrics

            +

            DMS metrics

            Distributed Cache Service

            +

            Distributed Cache Service

            SYS.DCS

            +

            SYS.DCS

            • Key: dcs_instance_id

              Value: DCS Redis instance

              -
            -
            • Key: dcs_cluster_redis_node

              Value: Redis Server

              -
            • Key: dcs_cluster_proxy_node

              Value: Proxy in a Proxy Cluster DCS Redis 3.0 instance

              -
            -

            DCS metrics

            +

            DCS metrics

            Database

            +

            Database

            Relational Database Service

            +

            Relational Database Service

            SYS.RDS

            +

            SYS.RDS

            For details, see the information in the right column.

            -

            RDS for MySQL metrics

            +

            RDS for MySQL metrics

            RDS for PostgreSQL metrics

            RDS for SQL Server metrics

            Document Database Service

            +

            Document Database Service

            SYS.DDS

            +

            SYS.DDS

            • Key: mongodb_node_id

              Value: DDS node ID

              -
            -
            • Key: mongodb_instance_id

              Value: DDS DB instance ID

              -
            -

            DDS metrics

            +

            DDS metrics

            GaussDB NoSQL

            +

            GeminiDB

            SYS.NoSQL

            +

            SYS.NoSQL

            For details, see the information in the right column.

            -

            GaussDB(for Cassandra) metrics

            +

            GeminiDB metrics

            GaussDB(for MySQL)

            +

            GaussDB(for MySQL)

            SYS.GAUSSDB

            +

            SYS.GAUSSDB

            For details, see the information in the right column.

            -

            GaussDB(for MySQL) metrics

            +

            GaussDB(for MySQL) metrics

            GaussDB

            +

            GaussDB(for openGauss)

            SYS.GAUSSDBV5

            +

            SYS.GAUSSDBV5

            For details, see the information in the right column.

            -

            GaussDB metrics

            +

            GaussDB(for openGauss) metrics

            Data analysis

            +

            Data analysis

            Data Warehouse Service

            +

            Data Warehouse Service

            SYS.DWS

            +

            SYS.DWS

            • Key: datastore_id

              Value: data warehouse cluster ID

              -
            -
            • Key: dws_instance_id

              Value: data warehouse node ID

              -
            -

            DWS metrics

            +

            DWS metrics

            Cloud Search Service

            +

            Cloud Search Service

            SYS.ES

            +

            SYS.ES

            • Key: cluster_id

              Values: Cluster ID

              -
            -

            CSS metrics

            +

            CSS metrics

            Data Ingestion Service (DIS)

            +

            Data Ingestion Service (DIS)

            SYS.DAYU

            +

            SYS.DAYU

            Key: stream_id

            -

            Value: real-time data ingestion

            -

            DIS Metrics

            +

            DIS Metrics

            2022-10-10

            +

            2024-01-04

            +

            This release incorporates the following changes:

            + +

            2022-10-10

            This release incorporates the following change:

            Added section "Events Supported by Event Monitoring".

            @@ -95,7 +101,7 @@

            2017-11-30

            This release incorporates the following change:

            -

            Added Auto Scaling (AS) metrics.

            +

            Added Auto Scaling metrics.

            2017-10-30

            @@ -173,7 +179,7 @@

            2016-04-14

            This release incorporates the following changes:

            -
            • Modified parameter descriptions in URL in Service Usage.
            • Modified steps for invoking interfaces in Token Authentication.
            +
            • Modified parameter descriptions in URL in Service Usage.
            • Modified steps for calling APIs in Token Authentication.

            2016-03-09

            diff --git a/docs/ces/api-ref/en-us_topic_0032831274.html b/docs/ces/api-ref/en-us_topic_0032831274.html index b83e10a9..0af026f9 100644 --- a/docs/ces/api-ref/en-us_topic_0032831274.html +++ b/docs/ces/api-ref/en-us_topic_0032831274.html @@ -2,6 +2,7 @@

            Adding Monitoring Data

            Function

            This API is used to add one or more pieces of custom metric monitoring data to solve the problem that the system metrics cannot meet specific service requirements.

            +

            For details about the monitoring data retention period, see How Long Is Metric Data Retained?

            URI

            POST /V1.0/{project_id}/metric-data

            • Parameter description @@ -289,7 +290,7 @@

            403 Forbidden

            You are forbidden to access the page requested.

            +

            Access to the requested page is forbidden.

            408 Request Timeout

            diff --git a/docs/ces/api-ref/public_sys-resources/imageclose.gif b/docs/ces/api-ref/public_sys-resources/imageclose.gif new file mode 100644 index 0000000000000000000000000000000000000000..3a3344af4afdeedcbd8d49c6739d1e100142841b GIT binary patch literal 1238 zcmZ?wbhEHb6krfwSj57xcJ11&Tet4ryZ7kPqyPW^XMh34|J)J20SYdOC5b@V#=fE; zF*!T6L?J0PJu}Z%>HY5gN(z}Nwo2iqz6QPp&Z!xh9#uuD!Bu`C$yM3OmMKd1b_zBX zRu#Dgxv3?I3Kh9IdBs*0wn~X9`AMl(KsHENUr7P1q$Jx`$q^)>0J76LzbI9~RL@v9 z*}%|H!OTq0(8Sct%uq+c$iUD@-vEfrbPY|cOwFu}%oU(O320kUN}5%WiyPD~AkS7Q zqokz3N?*Ucyj-u`STDaQUEk2s(h_8bk&!M?g>G?WUP)qwZeFo6%mkOz;^d;tf|AVq zJOz-6iAnjTCALaHmqNUdTj1*pH#o0Y59}emIIA zz^b}9q_QAYKPa_0zqBYh6{uVprWqJ^_$>k{1iHq`zbF$JDTz5Q`N^fZsd*)yF1AWQ z8NHOu6f0*7Co?Al3m0=|Hz!wTLqkUsXG>=zLt`g5XA?&!BSV-O*z_71I9eK+yO_E; zSy&hvx;k5$nmSv$xwx4dyBfNhxVXUddgc|EB<3Zj!tBii+6&cdf>*DVb5UwyNq$jC zetr%t1q5W|m*f{`1N{AbeZ0LqJ>1<~U7Vd99qjFFZLF;!Y#3Q(W~w5=#5%__*n4QdyV zXRDM^Qc_^0uU}qXu2*iXmtT~wZ)j<02{OaTNEfI=x41H|B(Xv_uUHvof=g;~a#3bM zNoIbY0?5R~r2NtnTP2`NAzsKWfE$}vtOxdvUUGh}ennz|zM-B0$V)JVzP|XC=H|jx z7ncO3BHWAB;NpiyW)Z+ZoqU2Pda%GTJ1y;^Qsfi`|MIrh5Ij~R+$jC3rFV4s> zP;d@5Q_u*{%uC5HFV+OB_w}{%%quQQ%u7!7bg@+enxL1NnPO#X>1=9lW@_r@WZ`IN z=<4ibV(4aRVPt0NVq{?MV&MeS>yn>bnwy$e0@Is<&})WMFDNPG765H_NiE7OOHFYr z%Fk5*d)X=zw_A*Hng`XJg4-=7IQ8lS9itD5Sfq%C2?0|NhzU=&Kn^_Nr{)1udl4{M zGyebg_s{QNKYx7x_Vvr>Pai+LfA{vy>sK#dJb(7|$>T>4AKbrp_s;EGH*Z|OcJ<2T zOBXMkKX>-b=~E|996xsS$l*f=5A5H!chBx!J9li~wsp(qO&d3?U$=J6>QyUOEMK;C z$>K!|7tEhGch2ltGiOYnHg(G6NfRgZ_x1L4cXf8Ox3#u3H#IiY*VWckS5;P&mz9V~xOjJZzNKk;EkC%s= zi<5($jg^I&iIIUp@h1zAWM$9+l@y?Ign`*MLgebdMh%7=#f^GV`6oq~%OupNBpS~X u5MOie_{@!7oGG@??#=tAc88xep;u>9v^MK*8TL~W837UsORumnSOWmkrlE=e literal 0 HcmV?d00001 diff --git a/docs/ces/api-ref/public_sys-resources/imagemax.gif b/docs/ces/api-ref/public_sys-resources/imagemax.gif new file mode 100644 index 0000000000000000000000000000000000000000..99c07dc2570d75fa74b38e02474edaa068eac3cd GIT binary patch literal 1267 zcmZ?wbhEHb6krfw*v!GOcJ12l-@k9&x^?f~y+@B8egFRbvuDrl-Mjby|9=K-K=D6! zgl~X?OJYePkhZa}C`e4sPAySLN=?tqvsHS(d%u!GW{Ry+xT&v!Z-H}aMy5wqQEG6N zUr2IQcCuxPlD(aRO@&oOZb5EpNuokUZcbjYRfVlmVoH8esuhq864qBz04piUwpDTj zNhpBqbj~kIRWQ{v)=f4rG*mD%(=#+NH8V5RQ7|$vG}1Q!A~Rh>6Dw0QDv55FG|-pw6wGYnPFt43sj+7T$xvrSfQI& ztPC^3CAB!YD6^m>Ge1uOWMX1cerbuV640d(FXR^Z`oay)E7k*hNG~}*SHB{$K;KZ$ zKtDGZMv>iKmOL5>Q4jB{Rj!(%9U^(#_1k!qLsi)!ER{(Zt!(*~rk?$<5is(aFdV zW(GFBW=_V&CN6HqZcY|XhK8=r7Urf-7UpI~1}+w6&MsyKFuk66#U+V($*C}VGlBL( z^%~*TYvo*&npl!w6q28x14{t`8Tlpo#Toep3eLf13L4>=c`5nj#hRe#f%w)XwJ5VJ zHN~wcKUV=9zE+u7>?iDRh~5-(!b~6N7=2LUKuRnyAz%swG2uxc$bn~`)I4C0DFS8< z#{d8R{`vju=a28-zJB@q>Enm@@7}(7{p#h5=g*!#dHm?%gZuaH-no72=8fyuu3ou( z>Eea+=gyuved^?i(;JWy=vu(<;#{X zS-fcBg8B32&Y3-H=8WmnrcRkWY2t+bzTTehuFj73w$_&BrpAW)y4srRs>+J;veJ^` zqQZjwyxg4Ztjvt`wA7U3q{M{yxY(HJsK|)$u+Wg;puhlsKVKhjFHaA5H&+*DCr1Z+ zJ6juTD@$N%Ff}nYGBnWF)78<|($r8_Q&mw`QdE$ala-N{l9Uh^6BQ8_5)|O)XVTX7EuW7CC;Uoy5{=yToaG3U&3L8;cDnPJJLQNKKPZ{%RG1_1H#8IXksPAt^OIGtXA({qFrr3YjUkO5vuy2EGN( zsTr9bRYj@6RemAKRoTgwDN6Qs3N{s16}bhusU?XD6}dTi#a0!zN{K1?NvT#qHb_`s zNdc^+B->WW5hS4iveP-gC{@8!&saCvz|c^^%uLVF#MI2pP)EVYz|ctF0Eof6`()~Xj@TAnpKdC8`Lf!&sHg;q@=(~U%$M(T(8_%FTW^V-_X+15@d#vkuFe$ zZgFK^Nn(X=Ua>OF1ees}+TSP$$Sz2y8{ z{ffi_eM3D1ke6TzeSPsO&CP|YE-nd5MYtEM!Nnn!1*!T$sm1xFMaii^<;ozd3ap%q zQWHz^i$e1Ab6}wukda@KU!0L&px_*Arl1j?nU|7ZUaSdL@9S&jnO9trn3tUD>0+w{ zG(j&jGsVi;)!4|{)Y-tz$->Fd(AC+}+1b$1!r0u+z{1eL#Lx_;*Cju>G&eP`1g19y zq1O}YRmZE0?5Y^blRt*Nf6tSB!lEh#Q4EXdEx&B@Nn%t%j5O-W8lOo)$*jfswmj0g`4 z4G9hk4Dk2!_3`%d^l*1`b#Zobbg;LxwXwFcv@ka_H8D0aG|<=6)zQ|{)KFJbRZ&(_ zRFIdGm64W`ln@sa6%iH^6yWFM<>BVy6BSI4CSAxB&DwTho$F4IIcJuq UNiKC-d_mhd`j^M;_8g}v-SbPqCQVNtM2CT+7#Xk6Q*af`Orwy*^+O_OOG+GOHnYSW&? zo9v(1vxo?u#DixKUc{3(f5C#kz?pvOp{!uY$NNs+=Xt+hH|h^}clLJ#LD;RH*iH7m z#h>d}+56GiUXClY(xENfr&E_8q2%Kp0@ctRpeAzt+4C=`C;as5}7yR_l>6Qtb8%e6o-_?hAdB~Q)!x&Fd4{D*LBXJsu^aHNoEms z(@c~ctQl;ScqE8vfFr;e-5#D$Q)H1YQwZZ)Z9^O-t3t7o$*CL5P*UVDCjWP44pcEVH!{30@%I zAvgq!`WnF&|NqW=iS_@dW-<##=EL#Vu&j^R1afgR`b^m@4~p2v5VjicKjJrRtq!Yp zsh$4l(Kzm&?{$0Uw{PZ0-`_s{;C$WZ!q47~2QRM(jc>xQv*_X(-^6OAZoeycU;PHJ CuQ@6J literal 0 HcmV?d00001 diff --git a/value b/value new file mode 100644 index 00000000..e69de29b diff --git a/with b/with new file mode 100644 index 00000000..e69de29b