Updated on 2026-04-16 GMT+08:00

Supported Events

Description

Event monitoring provides data collection, query, and alarm reporting for events. You can create alarm rules for both system events and custom events. When specific events occur, Cloud Eye generates alarms for you.

Cloud Eye can monitor dimensions (or objects) nested to a maximum depth of four levels (levels 0 to 3). Level 3 is the deepest level. For example, if the monitored dimension of an event is influxdb_cluster_id,influxdb_node_id, influxdb_cluster_id indicates level 0 and influxdb_node_id indicates level 1.

Namespace

SYS.NoSQL

Events That Can Be Monitored

Table 1 Supported GeminiDB events

Event Name

Event ID

Event Severity

Description

Solution

Impact

Dimension

Instance creation failure

NoSQLCreateInstanceFailed

Major

The instance quota or underlying resources are insufficient.

Release unnecessary instances and try again. You can also choose Service Tickets > Create Service Ticket in the upper right corner of the console and submit a service ticket to adjust the quota.

DB instances cannot be created.

influxdb_cluster_id

Specifications change failure

NoSQLResizeInstanceFailed

Major

The underlying resources are insufficient.

Choose Service Tickets > Create Service Ticket in the upper right corner of the console. Submit a service ticket to the O&M personnel to coordinate resources in the background and change the specifications again.

Services are interrupted.

influxdb_cluster_id

Node adding failure

NoSQLAddNodesFailed

Major

The underlying resources are insufficient.

Choose Service Tickets > Create Service Ticket in the upper right corner of the console. Submit a service ticket to O&M personnel to coordinate resources in the background, delete nodes that failed to be added, and add the nodes again.

None

influxdb_cluster_id

Node deletion failure

NoSQLDeleteNodesFailed

Major

Releasing underlying resources failed.

Delete the node again.

None

influxdb_cluster_id

Storage scale-up failure

NoSQLScaleUpStorageFailed

Major

The underlying resources are insufficient.

Choose Service Tickets > Create Service Ticket in the upper right corner of the console. Submit a service ticket to O&M personnel to coordinate resources in the background and scale up storage again.

Services may be interrupted.

influxdb_cluster_id

Password reset failure

NoSQLResetPasswordFailed

Major

Resetting the password times out.

Reset the password again.

None

influxdb_cluster_id

Parameter template change failure

NoSQLUpdateInstanceParamGroupFailed

Major

Changing a parameter template times out.

Change the parameter template again.

None

influxdb_cluster_id

Backup policy configuration failure

NoSQLSetBackupPolicyFailed

Major

The database connection is abnormal.

Configure the backup policy again.

None

influxdb_cluster_id

Manual backup creation failure

NoSQLCreateManualBackupFailed

Major

The backup files fail to be exported or uploaded.

Choose Service Tickets > Create Service Ticket in the upper right corner of the console and submit a service ticket to O&M personnel.

Data cannot be backed up.

influxdb_cluster_id

Automated backup creation failure

NoSQLCreateAutomatedBackupFailed

Major

The backup files fail to be exported or uploaded.

Choose Service Tickets > Create Service Ticket in the upper right corner of the console and submit a service ticket to O&M personnel.

Data cannot be backed up.

influxdb_cluster_id

Abnormal instance

NoSQLFaultyDBInstance

Major

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

Choose Service Tickets > Create Service Ticket in the upper right corner of the console and submit a service ticket to O&M personnel.

The database service may be unavailable.

influxdb_cluster_id

Instance recovered

NoSQLDBInstanceRecovered

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 further action is required.

None

influxdb_cluster_id

Abnormal node

NoSQLFaultyDBNode

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 functional. Choose Service Tickets > Create Service Ticket in the upper right corner of the console and submit a service ticket to O&M personnel.

The database service may be unavailable.

influxdb_cluster_id,influxdb_node_id

Node status recovery

NoSQLDBNodeRecovered

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 further action is required.

None

influxdb_cluster_id,influxdb_node_id

Primary/standby switchover or failover

NoSQLPrimaryStandbySwitched

Major

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

No further action is required.

None

influxdb_cluster_id

Occurrence of hotspot partitioning keys

HotKeyOccurs

Major

Hotspot data is stored in one partition because the primary key is improper. Improper application design causes frequent read and write operations on a key.

1. Choose a proper partition key.

2. Add service cache so that service applications read hotspot data from the cache first.

The service request success rate is affected, and the cluster performance and stability deteriorates.

influxdb_cluster_id,influxdb_node_id

BigKey occurrence

BigKeyOccurs

Major

The primary key design is improper. There are too many records or too much data in a single partition, causing load imbalance on nodes.

1. Choose a proper partition key.

2. Add a new partition key for hashing data.

As more and more data is stored in the partition, cluster stability deteriorates.

influxdb_cluster_id,influxdb_node_id

Insufficient storage space

NoSQLRiskyDataDiskUsage

Major

The storage space is insufficient.

Scale up storage by following Scaling Storage Space.

The instance becomes read-only, and data cannot be written to the database.

influxdb_cluster_id

Data disk expanded and being writable

NoSQLDataDiskUsageRecovered

Major

The data disk has been expanded and becomes writable.

No further action is required.

None

influxdb_cluster_id

Index creation failure

NoSQLCreateIndexFailed

Major

The workload exceeds what the instance specifications can take. In this case, creating indexes consumes more instance resources, which can increase response latency or cause stalls, eventually leading to a timeout and index creation failure.

1. Select matched instance specifications based on the service loads.

2. Create indexes during off-peak hours.

3. Create indexes in the background.

4. Select indexes as required.

The index fails to be created or is incomplete. Delete the index and create a new one.

influxdb_cluster_id

Write speed decrease

NoSQLStallingOccurs

Major

The write speed is close to the maximum write speed allowed by the cluster scale and instance specifications. As a result, the database flow control mechanism is triggered, and requests may fail.

1. Adjust the cluster scale or node specifications based on the maximum write rate of services.

2. Measure the maximum write request rate of services and distribute the peak write rate of services.

The success rate of service requests is affected.

influxdb_cluster_id

Data write stopped

NoSQLStoppingOccurs

Major

The data write speed is too fast, reaching the maximum write capability allowed by the cluster and instance specifications. As a result, the database flow control is triggered, and requests may fail.

1. Adjust the cluster scale or node specifications based on the maximum write rate of services.

2. Measure the maximum write request rate of services and distribute the peak write rate of services.

The success rate of service requests is affected.

influxdb_cluster_id

Database restart failure

NoSQLRestartDBFailed

Major

The instance status is abnormal.

Choose Service Tickets > Create Service Ticket in the upper right corner of the console and submit a service ticket to O&M personnel.

The instance may be abnormal.

influxdb_cluster_id

Restoration failure on a new instance

NoSQLRestoreToNewInstanceFailed

Major

The underlying resources are insufficient.

Choose Service Tickets > Create Service Ticket in the upper right corner of the console. Submit a service ticket to O&M personnel to coordinate resources in the background and add nodes again.

Data cannot be restored to a new instance.

influxdb_cluster_id

Restoration failure on an existing instance

NoSQLRestoreToExistInstanceFailed

Major

The backup file fails to be downloaded or restored.

Choose Service Tickets > Create Service Ticket in the upper right corner of the console and submit a service ticket to O&M personnel.

The current instance may be unavailable.

influxdb_cluster_id

Backup file deletion failure

NoSQLDeleteBackupFailed

Major

The backup files fail to be deleted from OBS.

Delete the backup files again.

None

influxdb_cluster_id

Failure to display slow query logs in plaintext

NoSQLSwitchSlowlogPlainTextFailed

Major

The API does not support this function.

Refer to GeminiDB User Guide to ensure that the API supports slow query logs in plaintext. Choose Service Tickets > Create Service Ticket in the upper right corner of the console and submit a service ticket to O&M personnel.

None

influxdb_cluster_id

EIP binding failure

NoSQLBindEipFailed

Major

The node status is abnormal, an EIP has been bound to the node, or the EIP to be bound is invalid.

Check whether the node is normal and whether the EIP is valid.

The instance cannot be accessed from a public network.

influxdb_cluster_id

EIP unbinding failure

NoSQLUnbindEipFailed

Major

The node is abnormal or the EIP has been unbound from the node.

Check whether the node and EIP status are normal.

None

influxdb_cluster_id

Parameter modification failure

NoSQLModifyParameterFailed

Major

The parameter value is invalid.

Check whether the parameter value is valid. Choose Service Tickets > Create Service Ticket in the upper right corner of the console and submit a service ticket to O&M personnel.

None

influxdb_cluster_id

Parameter template application failure

NoSQLApplyParameterGroupFailed

Major

The instance status is abnormal. So, the parameter template cannot be applied.

Choose Service Tickets > Create Service Ticket in the upper right corner of the console and submit a service ticket to O&M personnel.

None

influxdb_cluster_id

Failure to enable or disable SSL

NoSQLSwitchSSLFailed

Major

Enabling or disabling SSL times out.

Try again or choose Service Tickets > Create Service Ticket in the upper right corner of the console and submit a service ticket. Retain the SSL connection mode configured before the event occurred.

The SSL connection mode cannot be changed.

influxdb_cluster_id

Too much data in a single row

LargeRowOccurs

Major

If there is too much data in a single row, queries may time out, causing faults like OOM error.

1. Limit the write length of each column and row so that the key and value length of each row does not exceed the preset threshold.

2. Check whether there are abnormal writes or coding, causing large rows.

If there are too many records in a single row, cluster stability will deteriorate as the data volume increases.

influxdb_cluster_id

Schedule for deleting a KMS key

planDeleteKmsKey

Major

The user plans to delete a KMS key.

Check whether the GeminiDB instance associated with the key has been deleted or is no longer used. Deleting the key will affect the instance services.

The key will be automatically deleted after it expires. Deleting the key will affect the instance workloads.

influxdb_cluster_id

Too many tombstones

TooManyQueryTombstones

Major

Querying too many tombstones may time out.

Use a proper query and deletion method to avoid batch range queries.

The query may time out.

influxdb_cluster_id

Ultra-large collection column

TooLargeCollectionColumn

Major

If there are too many elements in the collection column, the query will fail.

Set a threshold for the number of elements in the collection column.

Check whether there is an error while data is written and encoded.

The query on the collection column will fail.

influxdb_cluster_id

Dimensions

Key

Value

influxdb_cluster_id

Cluster ID of a GeminiDB Influx instance

You can obtain the value by calling the Querying the Original Dimension Values in Server Monitoring API of Cloud Eye.

influxdb_node_id

Node ID of a GeminiDB Influx instance

You can obtain the value by calling the Querying the Original Dimension Values in Server Monitoring API of Cloud Eye.