A newer version of this documentation is available.

View Latest

Email Alerts

      Email alerts can be dispatched automatically when a significant error occurs.

      Configuring Email Alerts

      Only Full Administrators and Cluster Administrators can configure alerts.

      The email-alert system works by sending an email directly to a configured SMTP server. Each alert email is sent to the configured list of email recipients, to highlight specific issues and problems. Alerts are provided as a popup within Couchbase Web Console.

      It is important to ensure that all Couchbase Server nodes have network access to the configured SMTP server.

      You can define the settings using Couchbase Web Console, or using the REST API.

      The Email Alerts screen appears as follows:

      settings alerts

      To set up email alerts using Couchbase Web Console, first, select the Enable email alerts check box, to enable the email-alerts configuration. Then, enter appropriate data into the fields listed below.

      Email Server Settings

      Option Description


      The hostname of the SMTP server that will be used to send the email.


      The TCP/IP port to be used to communicate with the SMTP server. The default is the standard SMTP port 25.


      For email servers that require a username and password to send email, the username is used for authentication.


      For email servers that require a username and password to send email, the password is used for authentication. Note that when you save the settings you enter, the password that you typed into the Password field becomes invisible, and the field therefore appears blank. This is a security measure imposed by Couchbase Server: the password remains valid, and will be used in authenticating with the email server.

      Require encryption (TLS)

      Enable Transport Layer Security (TLS) when sending the email through the designated server.

      Email Settings

      Option Description

      Sender Email

      The email address identified as a source from which the email is sent. This email address should be one that is valid as a sender address for the SMTP server that you specify.


      A list of the recipients of each alert message. To specify more than one recipient, separate each address by a space, comma (,), or semicolon (;).

      Test Mail

      Click Send Test Email to send a test email to confirm the settings and configuration of the email server and recipients.

      Available Alerts

      You can enable individual alert messages that can be sent by selecting the appropriate check boxes. The supported alerts are:

      Alert Description Code

      Node was auto-failed-over

      The sending node has been failed over automatically.


      Maximum number of auto-failed-over nodes was reached

      The auto-failover system stops auto-failover when the maximum number of spare nodes available has been reached.


      Node wasn’t auto-failed-over as other nodes are down at the same time

      Auto-failover does not take place if there is already a node down.


      Node was not auto-failed-over as there are not enough nodes in the cluster running the same service

      You cannot support auto-failover with less than three nodes.


      Node was not auto-failed-over as auto-failover for one or more services running on the node is disabled

      Auto-failover does not take place on a node as one or more services running on the node is disabled.


      Node’s IP address has changed unexpectedly

      The IP address of the node has changed, which may indicate a network interface, operating system, or other network or system failure.


      Disk space used for persistent storage has reach at least 90% of capacity

      The disk device configured for storage of persistent data is nearing full capacity.


      Metadata overhead is more than 50%

      The amount of data required to store the metadata information for your dataset is now greater than 50% of the available RAM.


      Bucket memory on a node is entirely used for metadata

      All the available RAM on a node is being used to store the metadata for the objects stored. This means that there is no memory available for caching values. With no memory left for storing metadata, further requests to store data will also fail.

      Only applicable to buckets configured for value-only ejection. See Ejection, for information.


      Writing data to disk for a specific bucket has failed

      The disk or device used for persisting data has failed to store persistent data for a bucket.


      Writing event to audit log has failed

      The audit log event writing has failed.


      Approaching full Indexer RAM warning

      The indexer RAM limit threshold is approaching warning.


      Remote mutation timestamp exceeded drift threshold

      The remote mutation timestamp exceeded drift threshold warning.


      Communication issues among some nodes in the cluster

      There are some communication issues in some nodes within the cluster.