Events Reference

Capella Operational

reference

The possible events that can occur in Couchbase Capella.

Couchbase Capella produces events that reflect specific conditions in your Capella organization, projects, and clusters. For events with the Critical and Warning severity, Capella sends an alert when the event occurs. Capella writes all events to the Activity Log, where you can view them.

Capella can produce the following events.

Display Name	Resource	Tags	Description
Couchbase Nodes Dying	cluster	critical	The number of active nodes has reduced in a 10 minute period.
App Service Critically High Memory Usage	app services		During a 1-minute interval, the 5-minute average memory usage of one or more app services exceeded 90%. High memory usage events can impact the throughput of your service. This issue could be due to recent changes in the downstream application or dataset, such as changes to the data type sent, the amount of data sent, or natural data/transaction growth. Consider scaling your service nodes to address the issue.
Very High Disk Usage	cluster	critical	A Capella node is experience over 85% disk usage. Consider adding more disk storage to your cluster.
App Service High Access Errors Warning	app services		In the last 5 minutes, more than 50 requests made to the App Endpoint failed to successfully authenticate. A high volume of unsuccessful authentications may indicate malicious clients attempting to access the system.
Critically High CPU Usage	cluster	alert, performance.	During a 1-minute interval, the 5-minute average CPU usage of one or more cluster nodes exceeded 90%. High CPU usage events can impact the throughput of your cluster. This issue could be due to recent changes in the downstream application or dataset, such as changes to the data type sent, the amount of data sent, or natural data/transaction growth. Consider scaling your service nodes to address the issue. If new queries were recently introduced, validate and add any required indexes.
App Service Log Streaming Failures	app services		A number of Fluentbit output calls were retried but failed. This could have been caused by a misconfiguration of the Log Streaming for the App Service, or if the output url was unreachable.
App Service Log Streaming Critical	app services	alert	A number of Fluentbit output calls were retried but failed. This could have been caused by a misconfiguration of the Log Streaming for the App Service, or if the output url was unreachable.
Low Node Disk Storage	cluster	alert, performance.	A cluster node has low disk storage. The addition of more documents could fill the cluster and result in a service interruption. This issue could be due to spikes in data usage or natural data growth. Consider expanding the storage to resolve the issue.
XDCR High Memory Usage	cluster	alert	The sysproc_mem_size stat for xdcr shows that for the past 5m the process is using 4GB memory or greater.
Low Bucket Quota Memory	cluster	alert, performance.	A bucket has low memory. This can be caused by a change to incoming data, undersized service nodes, undersized service quotas, or a long time to live (TTL) setting on documents causing stale data to be held in memory. The service manages low memory by automatically evicting documents from memory to free up space. Evicted documents are still available from disk, but the GET performance is slower than reading from memory. If this is a persistent issue or you get Out of Memory (OOM) alerts, consider node scaling or adjusting memory quota limits for the bucket.
Data Service Down	cluster	alert	A node is reporting that the data service is down and requires immediate attention. Prometheus is reporting an up metric for the data service is 0. This means we are not getting data service metrics when we are expecting to. This issue should be investigated.
Search Service Down	cluster	alert	A node is reporting that the search service is down and requires immediate attention. Prometheus is reporting an up metric for the search service is 0. This means we are not getting search service metrics when we are expecting to. This issue should be investigated.
Runaway Disk Queue	cluster	alert, performance.	A bucket is experiencing a runaway disk queue. This is when data is added to the write queue faster than the node can write to the bucket. This issue can be caused by a sudden spike of incoming transactions or an undersized cluster that can’t keep up with its workload. Consider validating incoming data before scaling node capacity.
Index Service Down	cluster	alert	A node is reporting that the index service is down and requires immediate attention. Prometheus is reporting an up metric for the index service is 0. This means we are not getting index service metrics when we are expecting to. This issue should be investigated.
High CPU Usage Warning	cluster	alert, performance.	During a 5-minute interval, the 5-minute average CPU usage of one or more cluster nodes exceeded 85%. High CPU usage events can impact the throughput of your cluster. This issue could be due to recent changes in the downstream application or dataset, such as changes to the data type sent, the amount of data sent, or natural data/transaction growth. Consider scaling your service nodes to address the issue. If new queries were recently introduced, validate and add the required indexes.
Data Service Down	cluster	alert	A node is reporting that the analytics service is down and requires immediate attention. Prometheus is reporting an up metric for the analytics service is 0. This means we are not getting analytics service metrics when we are expecting to. This issue should be investigated.
Bucket Hard Out Of Memory	cluster	alert, performance.	A bucket exceeded its available memory and requires immediate attention. This issue can be caused by changes to the incoming data, undersized service nodes, undersized service quotas, or a long time to live (TTL) setting on documents. Consider immediately adding additional memory or nodes to resolve the issue.
Eventing Service Down	cluster	alert	A node is reporting that the eventing service is down and requires immediate attention. Prometheus is reporting an up metric for the eventing service is 0. This means we are not getting eventing service metrics when we are expecting to. This issue should be investigated.
Cluster Deployment Completed	cluster	availability, billing.	A new cluster was successfully deployed and can now serve traffic. Clusters are managed deployments of Couchbase Server. Each cluster consists of Couchbase Server instances that each run on independent nodes. Remember to scale your cluster to meet your performance requirements. Running clusters consumes Couchbase Capella Credits.
Cluster Created	cluster	availability, billing.	Scale your Cluster to meet your performance requirements. Running Clusters consume Capella credits.
Cluster Deleted	cluster	availability, billing.	Couchbase Capella does not retain backups from deleted Clusters.
Cluster Turn On Completed	cluster	availability, billing.	The cluster has successfully turned on and is now ready to resume normal operations. Before attempting to turn off the cluster again, please ensure that all maintenance operations have completed or have been re-scheduled.
Cluster Deletion Completed	cluster	availability, billing.	A cluster was successfully deleted. Deleting a cluster securely deletes all of its data. Couchbase Capella does not retain backups from deleted clusters.
Cluster Turn Off Completed	cluster	availability, billing.	The cluster has successfully turned off. You can no longer connect to the cluster or perform any read and write operations. Scheduled backups will not run while the cluster is turned off. The cluster can remain turned off for a maximum of 30 days. After 30 days, it will automatically turn on.
Cluster Node Disk Storage Increased	cluster	performance	A Couchbase Server node’s disk storage was increased.
App Service High Access Errors Warning	app services		In the last 5 minutes, more than 50 requests made to the App Endpoint failed to successfully authenticate. A high volume of unsuccessful authentications may indicate malicious clients attempting to access the system.
App Service High Data Sync Errors Warning	app services		In a 5 minute interval, more than 10 documents were rejected by the App Endpoint’s Sync Function. These documents will not be accessible via the App Endpoint. If this is unexpected, there may be an error in the Sync Function.
App Service High Import Errors Warning	app services		In a 5 minute interval, more than 10 documents failed to import due to error. These documents will not be accessible via the App Endpoint. The documents may have been rejected by the App Endpoint’s Sync Function, or encountered an error processing the document. If this is unexpected, there may be an error in the Sync Function’s logic. If this is expected, this alert can avoided by defining an import filter to limit Sync Function execution to only those documents that should be imported.
App Service High CPU Usage Warning	app services		During a 5-minute interval, the 5-minute average CPU usage of one or more App Service nodes exceeded 90%. High CPU usage events can impact throughput and latency of App Endpoints. This issue could be due to changes in the downstream application or dataset, such as changes to the number of requests or connections, the amount of data sent, or natural data/request growth. It may also be related to changes to the endpoints access control function or back end dataset. If these changes are expected, you may consider scaling your App Service deployment to address the issue.
App Service High Memory Usage Warning	app services		During a 5-minute interval, the 5-minute average memory usage of one or more app services exceeded 85%. High memory usage events can impact the throughput of your service. This issue could be due to recent changes in the downstream application or dataset, such as changes to the data type sent, the amount of data sent, or natural data/transaction growth. Consider scaling your service nodes to address the issue.
App Service Critically High CPU Usage	app services		During a 1-minute interval, the 5-minute average CPU usage of one or more App Service nodes exceeded 95% High CPU usage events can impact throughput and latency of App Endpoints. This issue could be due to changes in the downstream application or dataset, such as changes to the number of requests or connections, the amount of data sent, or natural data/request growth. It may also be related to changes to the endpoints access control function or back end dataset. If these changes are expected, you may consider scaling your App Service deployment to address the issue.
Approaching Low Index Resident Percentage	cluster	Warning	The percentage of indexes resident in RAM on the specified node has fallen below the threshold of 10%. Consider adding more memory, either by increasing the memory quota for the Index service, or by adding more nodes.
Bucket Flushed	cluster	maintenance	A bucket in this cluster was flushed, this deletes all of the documents within the bucket.
Backup Create Download Completed	cluster	maintenance	The creation of a downloadable backup file from a backup cycle has completed for a bucket in this cluster. You can copy the download URL from the Backup Downloadable Backups in the console.
Restore Started	cluster	maintenance	The process to restore data from a backup has started for a bucket in this cluster. This will restore all contents from the backup into the bucket, based on your selected restoration options.
On-Demand Backup Triggered	cluster	maintenance	The on-demand backup is now in the queue and starts when any previously scheduled backups or cluster maintenance finishes.
Backup Download URL Link Generated	cluster	maintenance	A pre-signed URL for a downloadable backup of a bucket in this cluster has been created. The URL is valid for one hour.
Backup Deleted	cluster	maintenance	A backup for a bucket in this cluster has been deleted.
Backup Create Download Started	cluster	maintenance	The process to create a downloadable backup file from a backup cycle has started for a bucket in this cluster.
Restore Triggered	cluster	maintenance	A request to restore data from a backup was triggered for a bucket in this cluster. The restore process will start as soon as possible.
Backup Create Download Triggered	cluster	maintenance	A request to download a backup was triggered for a bucket in this cluster. The download create process will start as soon as possible.
Restore Failed	cluster	maintenance	The process to restore data from a backup has failed for a bucket in this cluster. Some contents from the backup may have been successfully restored. Please consider retrying and if the restore continues to fail then contact Support, if Support is included in your chosen cluster plan. You can create a support ticket by clicking on the Create Support Ticket button.
Backup Failed	cluster	maintenance	A backup for a bucket in this cluster has failed. Please consider retrying and if the backup continues to fail then contact Support, if Support is included in your chosen cluster plan. You can create a support ticket by clicking on the Create Support Ticket button.
Maintenance Scheduled	cluster	maintenance	A maintenance has been scheduled for this cluster. Please visit the cluster’s Maintenance page to see more details and make changes to the schedule time.
Backup Create Download Failed	cluster	maintenance	The process to create a downloadable backup file from a backup cycle has failed for a bucket in this cluster. Please retry and if the creation of the download file continues to fail then contact Support, if Support is included in your chosen cluster plan. You can create a support ticket by clicking on the Create Support Ticket button.
Backup Completed	cluster	maintenance	A backup for a bucket in this cluster has completed. The backup is now available to restore on the ‘Backups’ page for the cluster.
Backup Deletion Failed	cluster	maintenance	A backup for a bucket in this cluster has failed to delete. Please consider retrying and if deleting the backup continues to fail then contact Support, if Support is included in your chosen cluster plan. You can create a support ticket by clicking on the Create Support Ticket button.
Restore Completed	cluster	maintenance	The process to restore data from a backup has completed for a bucket in this cluster. All contents from the backup should now be restored into the bucket. You can review the state of the last restore performed by visiting the ‘Last Restore’ tab for the bucket being restored.
Backup Started	cluster	maintenance	A backup for a bucket in this cluster has started. This will backup all data and indexes within the bucket and once completed will be available on the ‘Backups’ page for the cluster.
User Removed	tenant	security	A user was removed from the tenant and no longer has a project role. This permission change takes effect immediately. Every project member is assigned one or more project roles, which determine if a user can do things within the scope of a project, like create cluster credentials or create and manage clusters. To view and manage project users, open the project from the Projects tab and click the Users tab.
Vercel Integration Added	tenant	security	The Vercel Integration was added to the Organization. This allows selected clusters in this Organization to be accessible from the connected Vercel project. This will allow traffic from all IP addresses (CIDR 0.0.0.0/0) to the cluster. A user (vercel-user-xxxx) with Read/Write access to the selected bucket was created for the Vercel project.
API Key Deleted	tenant	security	An API key was deleted in your organization. Any calls to the API using this key will now fail. API keys are specific to individual Capella accounts and control the authorization for API operations. The Capella Public API uses a Bearer Token mechanism for authentication, so each call to the API requires a key to authenticate.
User Email Address Verified	tenant	security	A user has verified an email address associated with their account.
Cluster Credentials Updated	cluster	security	A cluster credential for a cluster was updated. An application can use this credential to access cluster data. We recommend the regular rotation of cluster credentials.
Team Created	tenant	security	A Team has been created.
User Added	tenant	security	A user has been added to the tenant and given a project role. The permissions of this new user take effect immediately. Every project member is assigned one or more project roles, which determine if a user can do things within the scope of a project, like create cluster credentials or create and manage clusters. To view and manage project users, open the project from the Projects tab and click the Users tab.
Team Roles Updated	tenant	security	Team Roles has been Updated.
Team Deleted	tenant	security	A Team has been deleted.
User Role Assigned	tenant	security	A user in the tenant has been assigned a new project role. This permission change takes effect immediately. Project roles determine if a user can do things within the scope of a project, like create cluster credentials or create and manage clusters. To view and manage project users, open the project from the Projects tab and click the Users tab.
User Removed from Project	project	availability, security.	A user was removed from a project. This user will no longer have any access to the clusters within this project. You can view and manage project users by opening the project in the Projects tab and clicking the Users tab.
User Logged In	tenant	security	A user has logged in to the tenant.
User Role Changed	tenant	security	A user’s organization role was changed. Organization roles control access to Couchbase Capella’s features and services. Every organization member is assigned one or more organization roles.
Cluster Credentials Created	cluster	security	A cluster credential was created for a cluster. An application can use this credential to access cluster data. We recommend the regular rotation of cluster credentials.
User Accepted Invitation	tenant	security	A user accepted an invitation to your organization. For new users, this means that they have successfully verified their account. If an existing Capella user, they have accepted the invitation in the Invites section of their Capella Account User Settings.
User Logged Out - Inactivity	tenant	security	A user has been automatically logged out of the tenant due to inactivity.
Audit Log Export Request Created	cluster	security	Cluster audit log export request has been created. An audit log export request prepares the requested audit logs into an archive which will be available for download once the logs are retrieved.
User Account Registered with the Social Sign-In Provider	tenant	security	A user has successfully registered with their social sign-in provider.
User Account Connected with the Social-Sign Provider	tenant	security	A user has successfully connected their social sign-in provider with their account.
User Deleted	tenant	security	A user was removed from your organization. Removing a user from an organization removes all of their assigned organization roles and access to any projects contained in that organization.
API Key Created	tenant	security	A new API key was created in your organization. API keys are specific to individual Capella accounts and control the authorization for API operations. The Capella Public API uses a Bearer Token mechanism for authentication, so each call to the API requires a key to authenticate.
User Added to Project	project	availability, security.	An organization user was added to a project. The level of access every project user has to the clusters in a project is controlled by their assigned project role(s). You can view and manage project users by opening the project in the Projects tab and clicking the Users tab.
Realm Created	tenant	security	A Realm has been created.
Cluster Credentials Deleted	cluster	security	A cluster credential was deleted from a cluster. If an application is still actively using this credential, it may stop functioning. Cluster credentials provide application-level access to cluster data.
Realm Deleted	tenant	security	A Realm has been deleted.
User Declined Invitation	tenant	security	A user declined an invitation to your organization using the Invites section of their Capella Account User Settings.
Failed to Update Group Mapping for all SSO Users	tenant	security	When the Group Mapping is Disabled or Enabled for a Realm, the Group Mapping field for all SSO users of the Realm should also be updated. If one or more of the SSO user is not updated, this event will occur.
IP Added to Allow List	cluster	security	There’s a new entry in a cluster’s Allowed IP list. This IP address or CIDR block now has temporary or permanent ingress access to the cluster. We recommend that you use temporary entries whenever possible and routinely audit the Allowed IP list.
User Invited	tenant	security	An email inviting a user to join the organization was sent. This email contains a link to activate a user account and create login credentials. Until this invitation is accepted, this new user will appear with a Pending status in the Users tab.
Failed to Delete All SSO User Permissions	tenant	security	When a Realm is deleted, the Capella RBAC permissions for associated SSO users should also be deleted. If one or more of the SSO user permissions were not able to be deleted, this event will occur.
Realm Updated	tenant	security	A Realm has been updated.
Cluster Audit Settings Configured	cluster	security	Cluster audit settings have been modified. Cluster audit settings determine if audit logs are enabled, which events are logged, and which users are disabled.
IP Removed from Allow List	cluster	security	An entry was removed from a cluster’s Allowed IP list. The removed IP address or CIDR block will no longer have access to the cluster. It can take a few minutes for the cluster to reject traffic once you remove an address. Any attempted connection to or from an IP address that isn’t in a cluster’s Allowed IP list is denied.
IP Updated from Allow List	cluster	security	An entry in a cluster’s Allowed IP list was updated. Capella only allows clusters to connect to trusted IP addresses added to the Allowed IP list. Any attempted connection to or from an IP address that isn’t in a cluster’s Allowed IP list is denied.
User Role Removed	tenant	security	A user in the tenant had a project role removed. This permission change takes effect immediately. Project roles determine if a user can do things within the scope of a project, like create cluster credentials or create and manage clusters. To view and manage project users, open the project from the Projects tab and click the Users tab.
User Logged Out	tenant	security	A user has logged out of the tenant.
User Password Reset	tenant	security	A user has successfully reset their password.
CMEK Created	tenant	security	A customer managed encryption key was created. This key can be used by Capella clusters to encrypt data at rest.
CMEK Rotated	tenant	security	A customer managed encryption key was rotated. The rotation of the key results in all clusters using the key to be redeployed to use the new key.
CMEK Deleted	tenant	security	A customer managed encryption key was deleted.
Cluster On/Off Scheduled Added	cluster	availability	An On/Off schedule has been added for the cluster. Your cluster will automatically turn off and back on according to this schedule. You can still manually turn the cluster on and off, and it will remain in the state you choose until the next scheduled operation.
Cluster Upgrade Failed	cluster	availability	The process to upgrade a cluster has failed. Please contact Support for assistance with this issue. You can create a support ticket by clicking on the Create Support Ticket button.
Cluster Peering Failed	cluster	availability	The process to peer a cluster has failed. Please contact Support for assistance with this issue. You can create a support ticket by clicking on the Create Support Ticket button.
Cluster Turn Off Failed	cluster	availability	The cluster has failed to turn off. Please contact Couchbase Capella Support for assistance.
Cluster Peering Completed	cluster	availability	The process to peer a cluster has completed successfully, network access is now available between the cluster and peered VPC.
Cluster Configuration Updated	cluster	availability	A cluster’s configuration was manually updated. To view this new configuration or make further updates, open the cluster’s Configuration tab.
Cluster Upgrade Completed	cluster	availability	The process to upgrade a cluster has completed successfully.
Private Endpoints Disabled	cluster	availability	Private endpoints was enabled for the cluster. When private endpoint is disabled, the private IP address to the cluster is no longer accessible.
Cluster Scheduled Turn On Initiated	cluster	availability	The On/Off schedule has started a turn on operation on the cluster. After the cluster turns on, you cannot turn it back off if there is maintenance scheduled within the next hour. You can reschedule cluster maintenance from the Maintenance page in your cluster settings.
Cluster Peering Initiated	cluster	availability	The process to peer a cluster with an application VPC or another cluster has been initiated.
Cluster Failed to Turn On From Schedule	cluster	availability	The cluster has failed to turn on from its set schedule. Please contact Couchbase Capella Support for assistance.
Cluster Rebalance Completed	cluster	availability	A rebalance for a cluster has completed successfully.
Bucket Created	cluster	availability	A new bucket was created in a cluster. Buckets are a container for grouping your data and are individually configurable. You can create up to 30 buckets in each cluster based on the cluster configuration.
Cluster On/Off Schedule Changed	cluster	availability	The On/Off schedule for the cluster has been successfully updated. Your cluster will automatically turn off and back on according to the new schedule. You can still turn the cluster on and off manually, and it will stay in the state you choose until the next scheduled operation.
Cluster Deployment Requested	cluster	availability	A new cluster was requested. Clusters are managed deployments of Couchbase Server. Each cluster consists of Couchbase Server instances that each run on independent nodes. Remember to scale your cluster to meet your performance requirements. Running clusters consumes Couchbase Capella Credits.
Private Endpoints Enabled	cluster	availability	Private endpoints was enabled for the cluster. Private endpoint is a network interface that uses a private IP address from the cluster virtual network.
Cluster Deployment Failed	cluster	availability	A cluster failed to deploy. Clusters that fail deployment cannot guarantee service functionality. This issue could be due to an underlying service or limit issue. If you need immediate assistance, contact Couchbase Capella Support or try again later. You can create a support ticket by clicking on the Create Support Ticket button.
Cluster Upgrade Initiated	cluster	availability	An upgrade for a cluster was initiated.
Cluster Deleted	cluster	availability, billing.	Couchbase Capella does not retain backups from deleted Clusters.
Cluster Scaling Initiated	cluster	availability	A cluster’s topology was changed and the scaling process has started.
Cluster Deletion Failed	cluster	availability	A cluster delete operation has failed. Please contact Couchbase Capella Support for assistance. You can create a support ticket by clicking on the Create Support Ticket button.
Free Tier Cluster Turn Off Requested	cluster	information	A request was made to turn off your free cluster. After the cluster turns off, you can no longer connect it or perform any read and write operations. The cluster can remain turned off for a maximum of 30 days. After 30 days, it will automatically be deleted.
Free Tier Cluster Turn Off Completed	cluster	information	Your free cluster has successfully turned off. You can no longer connect to the database or perform any read and write operations. The cluster can remain turned off for a maximum of 30 days. After 30 days, it will automatically be deleted.
Free Tier Cluster Turn On Requested	cluster	information	A request was made to turn on your free cluster. After the cluster turns on, you can connect to it and perform normal read and write operations.
Free Tier Cluster Turn On Completed	cluster	information	Your free cluster has successfully turned on and is now ready to resume normal operations.
Free Tier Cluster Turn Off Failed	cluster	warning	The free cluster has failed to turn off. Please contact Couchbase Capella Support for assistance.
Free Tier Cluster Turn On Failed	cluster	warning	The free cluster has failed to turn on. Please contact Couchbase Capella Support for assistance.
Self-Managed Target Reference Created	cluster	availability	A self-managed target reference was created in a cluster. You can create replication to the self-managed target.
Cluster Deletion Requested	cluster	availability	There has been a request to delete a cluster. Deleting a cluster securely deletes all of its data. Couchbase Capella does not retain backups from deleted clusters.
Project Deleted	project	availability	A project in your organization was deleted. This is a permanent action and cannot be reversed.
Project Created	project	availability	A new project was created in your organization. Projects group and manage access to clusters. Only organization members that are part of this project can access its contained clusters. You can view and manage project users by opening the project in the Projects tab and clicking the Users tab.
Bucket Config Updated	cluster	availability	The configuration of a bucket was changed. Buckets are a container for grouping your data and are individually configurable. Such configuration options include memory quotas, document time to live (TTL), and more.
Cluster Turn Off Requested	cluster	availability	A request was made to turn off the cluster. After the cluster is turned off, you can no longer connect it or perform any read and write operations. Scheduled backups will not run while the cluster is turned off. The cluster can remain turned off for a maximum of 30 days. After 30 days, it will automatically turn on.
Cluster Rebalance Initiated	cluster	availability	A rebalance for a cluster was initiated. This is caused by a change in the number of replicas for a given bucket or the recovery of a failed node.
Cluster Scaling Failed	cluster	availability	The process to scale a cluster has failed. Please contact Support for assistance with this issue. You can create a support ticket by clicking on the Create Support Ticket button.
Cluster Storage Increased	cluster	availability	A cluster’s storage was automatically increased. To view the new configuration or make further updates, open the cluster’s Settings tab.
Cluster Failed to Turn Off From Schedule	cluster	availability	The cluster has failed to turn off from its set schedule. Please contact Couchbase Capella Support for assistance.
Bucket Deleted	cluster	availability	A bucket and its contents were deleted from a cluster. Buckets are a container for grouping your data and are individually configurable.
Organization Created	tenant	availability	Welcome to Couchbase Capella!
Self-Managed Target Reference Deleted	cluster	availability	A self-managed target reference was deleted in a cluster.
Cluster Scheduled Turn Off Initiated	cluster	availability	The process to turn off the cluster has started on schedule. If the cluster has any pending or active backup-related jobs, the turn off process will wait until these jobs finish. After the cluster turns off, you will no longer be able to connect to it or perform any read and write operations. Scheduled backups will not run while the cluster is turned off but will continue to expire. The cluster can remain turned off for a maximum of 30 days. After 30 days, it will automatically turn on.
Cluster Storage Not Increased	cluster	availability	A cluster’s storage was not automatically increased due to AWS limits on how often a volume can be modified. To increase the storage manually through replacing the volumes, open the cluster’s Settings tab.
Cluster Turn On Requested	cluster	availability	A request was made to turn on the cluster. After the cluster turns on, you cannot turn it back off if there is maintenance scheduled within the next hour. You can reschedule cluster maintenance from the Maintenance page in your cluster settings.
Cluster Scaling Completed	cluster	availability	The process to scale a cluster has completed successfully, it is now using the new desired topology.
Cluster Rebalance Failed	cluster	availability	The process to rebalance a cluster has failed. Please contact Support for assistance with this issue. You can create a support ticket by clicking on the Create Support Ticket button.
Cluster Turn On Failed	cluster	availability	The cluster has failed to turn on. Please contact Couchbase Capella Support for assistance.

Display Name

Resource

Tags

Description

Couchbase Nodes Dying

cluster

critical

The number of active nodes has reduced in a 10 minute period.

App Service Critically High Memory Usage

app services

During a 1-minute interval, the 5-minute average memory usage of one or more app services exceeded 90%. High memory usage events can impact the throughput of your service. This issue could be due to recent changes in the downstream application or dataset, such as changes to the data type sent, the amount of data sent, or natural data/transaction growth. Consider scaling your service nodes to address the issue.

Very High Disk Usage

cluster

critical

A Capella node is experience over 85% disk usage. Consider adding more disk storage to your cluster.

App Service High Access Errors Warning

app services

In the last 5 minutes, more than 50 requests made to the App Endpoint failed to successfully authenticate. A high volume of unsuccessful authentications may indicate malicious clients attempting to access the system.

Critically High CPU Usage

cluster

alert, performance.

During a 1-minute interval, the 5-minute average CPU usage of one or more cluster nodes exceeded 90%. High CPU usage events can impact the throughput of your cluster. This issue could be due to recent changes in the downstream application or dataset, such as changes to the data type sent, the amount of data sent, or natural data/transaction growth. Consider scaling your service nodes to address the issue. If new queries were recently introduced, validate and add any required indexes.

App Service Log Streaming Failures

app services

A number of Fluentbit output calls were retried but failed. This could have been caused by a misconfiguration of the Log Streaming for the App Service, or if the output url was unreachable.

App Service Log Streaming Critical

app services

alert

A number of Fluentbit output calls were retried but failed. This could have been caused by a misconfiguration of the Log Streaming for the App Service, or if the output url was unreachable.

Low Node Disk Storage

cluster

alert, performance.

A cluster node has low disk storage. The addition of more documents could fill the cluster and result in a service interruption. This issue could be due to spikes in data usage or natural data growth. Consider expanding the storage to resolve the issue.

XDCR High Memory Usage

cluster

alert

The sysproc_mem_size stat for xdcr shows that for the past 5m the process is using 4GB memory or greater.

Low Bucket Quota Memory

cluster

alert, performance.

A bucket has low memory. This can be caused by a change to incoming data, undersized service nodes, undersized service quotas, or a long time to live (TTL) setting on documents causing stale data to be held in memory. The service manages low memory by automatically evicting documents from memory to free up space. Evicted documents are still available from disk, but the GET performance is slower than reading from memory. If this is a persistent issue or you get Out of Memory (OOM) alerts, consider node scaling or adjusting memory quota limits for the bucket.

Data Service Down

cluster

alert

A node is reporting that the data service is down and requires immediate attention. Prometheus is reporting an up metric for the data service is 0. This means we are not getting data service metrics when we are expecting to. This issue should be investigated.

Search Service Down

cluster

alert

A node is reporting that the search service is down and requires immediate attention. Prometheus is reporting an up metric for the search service is 0. This means we are not getting search service metrics when we are expecting to. This issue should be investigated.

Runaway Disk Queue

cluster

alert, performance.

A bucket is experiencing a runaway disk queue. This is when data is added to the write queue faster than the node can write to the bucket. This issue can be caused by a sudden spike of incoming transactions or an undersized cluster that can’t keep up with its workload. Consider validating incoming data before scaling node capacity.

Index Service Down

cluster

alert

A node is reporting that the index service is down and requires immediate attention. Prometheus is reporting an up metric for the index service is 0. This means we are not getting index service metrics when we are expecting to. This issue should be investigated.

High CPU Usage Warning

cluster

alert, performance.

During a 5-minute interval, the 5-minute average CPU usage of one or more cluster nodes exceeded 85%. High CPU usage events can impact the throughput of your cluster. This issue could be due to recent changes in the downstream application or dataset, such as changes to the data type sent, the amount of data sent, or natural data/transaction growth. Consider scaling your service nodes to address the issue. If new queries were recently introduced, validate and add the required indexes.

Data Service Down

cluster

alert

A node is reporting that the analytics service is down and requires immediate attention. Prometheus is reporting an up metric for the analytics service is 0. This means we are not getting analytics service metrics when we are expecting to. This issue should be investigated.

Bucket Hard Out Of Memory

cluster

alert, performance.

A bucket exceeded its available memory and requires immediate attention. This issue can be caused by changes to the incoming data, undersized service nodes, undersized service quotas, or a long time to live (TTL) setting on documents. Consider immediately adding additional memory or nodes to resolve the issue.

Eventing Service Down

cluster

alert

A node is reporting that the eventing service is down and requires immediate attention. Prometheus is reporting an up metric for the eventing service is 0. This means we are not getting eventing service metrics when we are expecting to. This issue should be investigated.

Cluster Deployment Completed

cluster

availability, billing.

A new cluster was successfully deployed and can now serve traffic. Clusters are managed deployments of Couchbase Server. Each cluster consists of Couchbase Server instances that each run on independent nodes. Remember to scale your cluster to meet your performance requirements. Running clusters consumes Couchbase Capella Credits.

Cluster Created

cluster

availability, billing.

Scale your Cluster to meet your performance requirements. Running Clusters consume Capella credits.

Cluster Deleted

cluster

availability, billing.

Couchbase Capella does not retain backups from deleted Clusters.

Cluster Turn On Completed

cluster

availability, billing.

The cluster has successfully turned on and is now ready to resume normal operations. Before attempting to turn off the cluster again, please ensure that all maintenance operations have completed or have been re-scheduled.

Cluster Deletion Completed

cluster

availability, billing.

A cluster was successfully deleted. Deleting a cluster securely deletes all of its data. Couchbase Capella does not retain backups from deleted clusters.

Cluster Turn Off Completed

cluster

availability, billing.

The cluster has successfully turned off. You can no longer connect to the cluster or perform any read and write operations. Scheduled backups will not run while the cluster is turned off. The cluster can remain turned off for a maximum of 30 days. After 30 days, it will automatically turn on.

Cluster Node Disk Storage Increased

cluster

performance

A Couchbase Server node’s disk storage was increased.

App Service High Access Errors Warning

app services

App Service High Data Sync Errors Warning

app services

In a 5 minute interval, more than 10 documents were rejected by the App Endpoint’s Sync Function. These documents will not be accessible via the App Endpoint. If this is unexpected, there may be an error in the Sync Function.

App Service High Import Errors Warning

app services

In a 5 minute interval, more than 10 documents failed to import due to error. These documents will not be accessible via the App Endpoint. The documents may have been rejected by the App Endpoint’s Sync Function, or encountered an error processing the document. If this is unexpected, there may be an error in the Sync Function’s logic. If this is expected, this alert can avoided by defining an import filter to limit Sync Function execution to only those documents that should be imported.

App Service High CPU Usage Warning

app services

During a 5-minute interval, the 5-minute average CPU usage of one or more App Service nodes exceeded 90%. High CPU usage events can impact throughput and latency of App Endpoints. This issue could be due to changes in the downstream application or dataset, such as changes to the number of requests or connections, the amount of data sent, or natural data/request growth. It may also be related to changes to the endpoints access control function or back end dataset. If these changes are expected, you may consider scaling your App Service deployment to address the issue.

App Service High Memory Usage Warning

app services

During a 5-minute interval, the 5-minute average memory usage of one or more app services exceeded 85%. High memory usage events can impact the throughput of your service. This issue could be due to recent changes in the downstream application or dataset, such as changes to the data type sent, the amount of data sent, or natural data/transaction growth. Consider scaling your service nodes to address the issue.

App Service Critically High CPU Usage

app services

During a 1-minute interval, the 5-minute average CPU usage of one or more App Service nodes exceeded 95% High CPU usage events can impact throughput and latency of App Endpoints. This issue could be due to changes in the downstream application or dataset, such as changes to the number of requests or connections, the amount of data sent, or natural data/request growth. It may also be related to changes to the endpoints access control function or back end dataset. If these changes are expected, you may consider scaling your App Service deployment to address the issue.

Approaching Low Index Resident Percentage

cluster

Warning

The percentage of indexes resident in RAM on the specified node has fallen below the threshold of 10%. Consider adding more memory, either by increasing the memory quota for the Index service, or by adding more nodes.

Bucket Flushed

cluster

maintenance

A bucket in this cluster was flushed, this deletes all of the documents within the bucket.

Backup Create Download Completed

cluster

maintenance

The creation of a downloadable backup file from a backup cycle has completed for a bucket in this cluster. You can copy the download URL from the Backup Downloadable Backups in the console.

Restore Started

cluster

maintenance

The process to restore data from a backup has started for a bucket in this cluster. This will restore all contents from the backup into the bucket, based on your selected restoration options.

On-Demand Backup Triggered

cluster

maintenance

The on-demand backup is now in the queue and starts when any previously scheduled backups or cluster maintenance finishes.

Backup Download URL Link Generated

cluster

maintenance

A pre-signed URL for a downloadable backup of a bucket in this cluster has been created. The URL is valid for one hour.

Backup Deleted

cluster

maintenance

A backup for a bucket in this cluster has been deleted.

Backup Create Download Started

cluster

maintenance

The process to create a downloadable backup file from a backup cycle has started for a bucket in this cluster.

Restore Triggered

cluster

maintenance

A request to restore data from a backup was triggered for a bucket in this cluster. The restore process will start as soon as possible.

Backup Create Download Triggered

cluster

maintenance

A request to download a backup was triggered for a bucket in this cluster. The download create process will start as soon as possible.

Restore Failed

cluster

maintenance

The process to restore data from a backup has failed for a bucket in this cluster. Some contents from the backup may have been successfully restored. Please consider retrying and if the restore continues to fail then contact Support, if Support is included in your chosen cluster plan. You can create a support ticket by clicking on the Create Support Ticket button.

Backup Failed

cluster

maintenance

A backup for a bucket in this cluster has failed. Please consider retrying and if the backup continues to fail then contact Support, if Support is included in your chosen cluster plan. You can create a support ticket by clicking on the Create Support Ticket button.

Maintenance Scheduled

cluster

maintenance

A maintenance has been scheduled for this cluster. Please visit the cluster’s Maintenance page to see more details and make changes to the schedule time.

Backup Create Download Failed

cluster

maintenance

The process to create a downloadable backup file from a backup cycle has failed for a bucket in this cluster. Please retry and if the creation of the download file continues to fail then contact Support, if Support is included in your chosen cluster plan. You can create a support ticket by clicking on the Create Support Ticket button.

Backup Completed

cluster

maintenance

A backup for a bucket in this cluster has completed. The backup is now available to restore on the ‘Backups’ page for the cluster.

Backup Deletion Failed

cluster

maintenance

A backup for a bucket in this cluster has failed to delete. Please consider retrying and if deleting the backup continues to fail then contact Support, if Support is included in your chosen cluster plan. You can create a support ticket by clicking on the Create Support Ticket button.

Restore Completed

cluster

maintenance

The process to restore data from a backup has completed for a bucket in this cluster. All contents from the backup should now be restored into the bucket. You can review the state of the last restore performed by visiting the ‘Last Restore’ tab for the bucket being restored.

Backup Started

cluster

maintenance

A backup for a bucket in this cluster has started. This will backup all data and indexes within the bucket and once completed will be available on the ‘Backups’ page for the cluster.

User Removed

tenant

security

A user was removed from the tenant and no longer has a project role. This permission change takes effect immediately. Every project member is assigned one or more project roles, which determine if a user can do things within the scope of a project, like create cluster credentials or create and manage clusters. To view and manage project users, open the project from the Projects tab and click the Users tab.

Vercel Integration Added

tenant

security

The Vercel Integration was added to the Organization. This allows selected clusters in this Organization to be accessible from the connected Vercel project. This will allow traffic from all IP addresses (CIDR 0.0.0.0/0) to the cluster. A user (vercel-user-xxxx) with Read/Write access to the selected bucket was created for the Vercel project.

API Key Deleted

tenant

security

An API key was deleted in your organization. Any calls to the API using this key will now fail. API keys are specific to individual Capella accounts and control the authorization for API operations. The Capella Public API uses a Bearer Token mechanism for authentication, so each call to the API requires a key to authenticate.

User Email Address Verified

tenant

security

A user has verified an email address associated with their account.

Cluster Credentials Updated

cluster

security

A cluster credential for a cluster was updated. An application can use this credential to access cluster data. We recommend the regular rotation of cluster credentials.

Team Created

tenant

security

A Team has been created.

User Added

tenant

security

A user has been added to the tenant and given a project role. The permissions of this new user take effect immediately. Every project member is assigned one or more project roles, which determine if a user can do things within the scope of a project, like create cluster credentials or create and manage clusters. To view and manage project users, open the project from the Projects tab and click the Users tab.

Team Roles Updated

tenant

security

Team Roles has been Updated.

Team Deleted

tenant

security

A Team has been deleted.

User Role Assigned

tenant

security

A user in the tenant has been assigned a new project role. This permission change takes effect immediately. Project roles determine if a user can do things within the scope of a project, like create cluster credentials or create and manage clusters. To view and manage project users, open the project from the Projects tab and click the Users tab.

User Removed from Project

project

availability, security.

A user was removed from a project. This user will no longer have any access to the clusters within this project. You can view and manage project users by opening the project in the Projects tab and clicking the Users tab.

User Logged In

tenant

security

A user has logged in to the tenant.

User Role Changed

tenant

security

A user’s organization role was changed. Organization roles control access to Couchbase Capella’s features and services. Every organization member is assigned one or more organization roles.

Cluster Credentials Created

cluster

security

A cluster credential was created for a cluster. An application can use this credential to access cluster data. We recommend the regular rotation of cluster credentials.

User Accepted Invitation

tenant

security

A user accepted an invitation to your organization. For new users, this means that they have successfully verified their account. If an existing Capella user, they have accepted the invitation in the Invites section of their Capella Account User Settings.

User Logged Out - Inactivity

tenant

security

A user has been automatically logged out of the tenant due to inactivity.

Audit Log Export Request Created

cluster

security

Cluster audit log export request has been created. An audit log export request prepares the requested audit logs into an archive which will be available for download once the logs are retrieved.

User Account Registered with the Social Sign-In Provider

tenant

security

A user has successfully registered with their social sign-in provider.

User Account Connected with the Social-Sign Provider

tenant

security

A user has successfully connected their social sign-in provider with their account.

User Deleted

tenant

security

A user was removed from your organization. Removing a user from an organization removes all of their assigned organization roles and access to any projects contained in that organization.

API Key Created

tenant

security

A new API key was created in your organization. API keys are specific to individual Capella accounts and control the authorization for API operations. The Capella Public API uses a Bearer Token mechanism for authentication, so each call to the API requires a key to authenticate.

User Added to Project

project

availability, security.

An organization user was added to a project. The level of access every project user has to the clusters in a project is controlled by their assigned project role(s). You can view and manage project users by opening the project in the Projects tab and clicking the Users tab.

Realm Created

tenant

security

A Realm has been created.

Cluster Credentials Deleted

cluster

security

A cluster credential was deleted from a cluster. If an application is still actively using this credential, it may stop functioning. Cluster credentials provide application-level access to cluster data.

Realm Deleted

tenant

security

A Realm has been deleted.

User Declined Invitation

tenant

security

A user declined an invitation to your organization using the Invites section of their Capella Account User Settings.

Failed to Update Group Mapping for all SSO Users

tenant

security

When the Group Mapping is Disabled or Enabled for a Realm, the Group Mapping field for all SSO users of the Realm should also be updated. If one or more of the SSO user is not updated, this event will occur.

IP Added to Allow List

cluster

security

There’s a new entry in a cluster’s Allowed IP list. This IP address or CIDR block now has temporary or permanent ingress access to the cluster. We recommend that you use temporary entries whenever possible and routinely audit the Allowed IP list.

User Invited

tenant

security

An email inviting a user to join the organization was sent. This email contains a link to activate a user account and create login credentials. Until this invitation is accepted, this new user will appear with a Pending status in the Users tab.

Failed to Delete All SSO User Permissions

tenant

security

When a Realm is deleted, the Capella RBAC permissions for associated SSO users should also be deleted. If one or more of the SSO user permissions were not able to be deleted, this event will occur.

Realm Updated

tenant

security

A Realm has been updated.

Cluster Audit Settings Configured

cluster

security

Cluster audit settings have been modified. Cluster audit settings determine if audit logs are enabled, which events are logged, and which users are disabled.

IP Removed from Allow List

cluster

security

An entry was removed from a cluster’s Allowed IP list. The removed IP address or CIDR block will no longer have access to the cluster. It can take a few minutes for the cluster to reject traffic once you remove an address. Any attempted connection to or from an IP address that isn’t in a cluster’s Allowed IP list is denied.

IP Updated from Allow List

cluster

security

An entry in a cluster’s Allowed IP list was updated. Capella only allows clusters to connect to trusted IP addresses added to the Allowed IP list. Any attempted connection to or from an IP address that isn’t in a cluster’s Allowed IP list is denied.

User Role Removed

tenant

security

A user in the tenant had a project role removed. This permission change takes effect immediately. Project roles determine if a user can do things within the scope of a project, like create cluster credentials or create and manage clusters. To view and manage project users, open the project from the Projects tab and click the Users tab.

User Logged Out

tenant

security

A user has logged out of the tenant.

User Password Reset

tenant

security

A user has successfully reset their password.

CMEK Created

tenant

security

A customer managed encryption key was created. This key can be used by Capella clusters to encrypt data at rest.

CMEK Rotated

tenant

security

A customer managed encryption key was rotated. The rotation of the key results in all clusters using the key to be redeployed to use the new key.

CMEK Deleted

tenant

security

A customer managed encryption key was deleted.

Cluster On/Off Scheduled Added

cluster

availability

An On/Off schedule has been added for the cluster. Your cluster will automatically turn off and back on according to this schedule. You can still manually turn the cluster on and off, and it will remain in the state you choose until the next scheduled operation.

Cluster Upgrade Failed

cluster

availability

The process to upgrade a cluster has failed. Please contact Support for assistance with this issue. You can create a support ticket by clicking on the Create Support Ticket button.

Cluster Peering Failed

cluster

availability

The process to peer a cluster has failed. Please contact Support for assistance with this issue. You can create a support ticket by clicking on the Create Support Ticket button.

Cluster Turn Off Failed

cluster

availability

The cluster has failed to turn off. Please contact Couchbase Capella Support for assistance.

Cluster Peering Completed

cluster

availability

The process to peer a cluster has completed successfully, network access is now available between the cluster and peered VPC.

Cluster Configuration Updated

cluster

availability

A cluster’s configuration was manually updated. To view this new configuration or make further updates, open the cluster’s Configuration tab.

Cluster Upgrade Completed

cluster

availability

The process to upgrade a cluster has completed successfully.

Private Endpoints Disabled

cluster

availability

Private endpoints was enabled for the cluster. When private endpoint is disabled, the private IP address to the cluster is no longer accessible.

Cluster Scheduled Turn On Initiated

cluster

availability

The On/Off schedule has started a turn on operation on the cluster. After the cluster turns on, you cannot turn it back off if there is maintenance scheduled within the next hour. You can reschedule cluster maintenance from the Maintenance page in your cluster settings.

Cluster Peering Initiated

cluster

availability

The process to peer a cluster with an application VPC or another cluster has been initiated.

Cluster Failed to Turn On From Schedule

cluster

availability

The cluster has failed to turn on from its set schedule. Please contact Couchbase Capella Support for assistance.

Cluster Rebalance Completed

cluster

availability

A rebalance for a cluster has completed successfully.

Bucket Created

cluster

availability

A new bucket was created in a cluster. Buckets are a container for grouping your data and are individually configurable. You can create up to 30 buckets in each cluster based on the cluster configuration.

Cluster On/Off Schedule Changed

cluster

availability

The On/Off schedule for the cluster has been successfully updated. Your cluster will automatically turn off and back on according to the new schedule. You can still turn the cluster on and off manually, and it will stay in the state you choose until the next scheduled operation.

Cluster Deployment Requested

cluster

availability

A new cluster was requested. Clusters are managed deployments of Couchbase Server. Each cluster consists of Couchbase Server instances that each run on independent nodes. Remember to scale your cluster to meet your performance requirements. Running clusters consumes Couchbase Capella Credits.

Private Endpoints Enabled

cluster

availability

Private endpoints was enabled for the cluster. Private endpoint is a network interface that uses a private IP address from the cluster virtual network.

Cluster Deployment Failed

cluster

availability

A cluster failed to deploy. Clusters that fail deployment cannot guarantee service functionality. This issue could be due to an underlying service or limit issue. If you need immediate assistance, contact Couchbase Capella Support or try again later. You can create a support ticket by clicking on the Create Support Ticket button.

Cluster Upgrade Initiated

cluster

availability

An upgrade for a cluster was initiated.

Cluster Deleted

cluster

availability, billing.

Couchbase Capella does not retain backups from deleted Clusters.

Cluster Scaling Initiated

cluster

availability

A cluster’s topology was changed and the scaling process has started.

Cluster Deletion Failed

cluster

availability

A cluster delete operation has failed. Please contact Couchbase Capella Support for assistance. You can create a support ticket by clicking on the Create Support Ticket button.

Free Tier Cluster Turn Off Requested

cluster

information

A request was made to turn off your free cluster. After the cluster turns off, you can no longer connect it or perform any read and write operations. The cluster can remain turned off for a maximum of 30 days. After 30 days, it will automatically be deleted.

Free Tier Cluster Turn Off Completed

cluster

information

Your free cluster has successfully turned off. You can no longer connect to the database or perform any read and write operations. The cluster can remain turned off for a maximum of 30 days. After 30 days, it will automatically be deleted.

Free Tier Cluster Turn On Requested

cluster

information

A request was made to turn on your free cluster. After the cluster turns on, you can connect to it and perform normal read and write operations.

Free Tier Cluster Turn On Completed

cluster

information

Your free cluster has successfully turned on and is now ready to resume normal operations.

Free Tier Cluster Turn Off Failed

cluster

warning

The free cluster has failed to turn off. Please contact Couchbase Capella Support for assistance.

Free Tier Cluster Turn On Failed

cluster

warning

The free cluster has failed to turn on. Please contact Couchbase Capella Support for assistance.

Self-Managed Target Reference Created

cluster

availability

A self-managed target reference was created in a cluster. You can create replication to the self-managed target.

Cluster Deletion Requested

cluster

availability

There has been a request to delete a cluster. Deleting a cluster securely deletes all of its data. Couchbase Capella does not retain backups from deleted clusters.

Project Deleted

project

availability

A project in your organization was deleted. This is a permanent action and cannot be reversed.

Project Created

project

availability

A new project was created in your organization. Projects group and manage access to clusters. Only organization members that are part of this project can access its contained clusters. You can view and manage project users by opening the project in the Projects tab and clicking the Users tab.

Bucket Config Updated

cluster

availability

The configuration of a bucket was changed. Buckets are a container for grouping your data and are individually configurable. Such configuration options include memory quotas, document time to live (TTL), and more.

Cluster Turn Off Requested

cluster

availability

A request was made to turn off the cluster. After the cluster is turned off, you can no longer connect it or perform any read and write operations. Scheduled backups will not run while the cluster is turned off. The cluster can remain turned off for a maximum of 30 days. After 30 days, it will automatically turn on.

Cluster Rebalance Initiated

cluster

availability

A rebalance for a cluster was initiated. This is caused by a change in the number of replicas for a given bucket or the recovery of a failed node.

Cluster Scaling Failed

cluster

availability

The process to scale a cluster has failed. Please contact Support for assistance with this issue. You can create a support ticket by clicking on the Create Support Ticket button.

Cluster Storage Increased

cluster

availability

A cluster’s storage was automatically increased. To view the new configuration or make further updates, open the cluster’s Settings tab.

Cluster Failed to Turn Off From Schedule

cluster

availability

The cluster has failed to turn off from its set schedule. Please contact Couchbase Capella Support for assistance.

Bucket Deleted

cluster

availability

A bucket and its contents were deleted from a cluster. Buckets are a container for grouping your data and are individually configurable.

Organization Created

tenant

availability

Welcome to Couchbase Capella!

Self-Managed Target Reference Deleted

cluster

availability

A self-managed target reference was deleted in a cluster.

Cluster Scheduled Turn Off Initiated

cluster

availability

The process to turn off the cluster has started on schedule. If the cluster has any pending or active backup-related jobs, the turn off process will wait until these jobs finish. After the cluster turns off, you will no longer be able to connect to it or perform any read and write operations. Scheduled backups will not run while the cluster is turned off but will continue to expire. The cluster can remain turned off for a maximum of 30 days. After 30 days, it will automatically turn on.

Cluster Storage Not Increased

cluster

availability

A cluster’s storage was not automatically increased due to AWS limits on how often a volume can be modified. To increase the storage manually through replacing the volumes, open the cluster’s Settings tab.

Cluster Turn On Requested

cluster

availability

A request was made to turn on the cluster. After the cluster turns on, you cannot turn it back off if there is maintenance scheduled within the next hour. You can reschedule cluster maintenance from the Maintenance page in your cluster settings.

Cluster Scaling Completed

cluster

availability

The process to scale a cluster has completed successfully, it is now using the new desired topology.

Cluster Rebalance Failed

cluster

availability

The process to rebalance a cluster has failed. Please contact Support for assistance with this issue. You can create a support ticket by clicking on the Create Support Ticket button.

Cluster Turn On Failed

cluster

availability

The cluster has failed to turn on. Please contact Couchbase Capella Support for assistance.

Events Reference

See Also