A newer version of this documentation is available.

View Latest

Email Alerts

      +
      Email alerts can be dispatched automatically.

      Configuring Email Alerts

      Email alerts can be dispatched automatically by Couchbase Server, in order to highlight specific issues and problems. When an issue occurs, an alert is generated, and is sent as an email by Couchbase Server to a configured SMTP server. From there, the email is forwarded to a configured list of email recipients. Each alert, when received, appears as a pop-up, within the Couchbase Web Console of its recipient.

      All cluster-nodes must have network access to the configured SMTP server, for the system to be fully effective.

      Only Full Administrators and Cluster Administrators can configure email alerts. Configuration can be performed with Couchbase Web Console, the Couchbase CLI, or the REST API.

      Configure Email Alerts with the UI

      Access the Email Alerts settings screen. First, click on the Settings tab, in the navigation bar at the left-hand side of Couchbase Web Console:

      settingsTab

      This brings up the main Settings screen. Now, access the Email Alerts panel, by means of the Email Alerts tab, located on the horizontal navigation bar, at the top:

      emailAlertsTab

      The Email Alerts panel now appears. Initially, its content is greyed out, and the user-interface components are inaccessible. To make the components accessible, use the Enable email alerts toggle, near the top of the panel:

      enableEmailAlertsToggleOff

      Switch the toggle to the right:

      enableEmailAlertsToggleOn

      The Email Alerts panel is now fully displayed, and the user-interface components are accessible:

      settings alerts

      To establish an appropriate email-alerts configuration, first, enter appropriate data into the displayed fields, using the data provided in the Email Settings table, immediately below. Then, proceed to Saving and Testing the Alert Configuration, further below.

      Email Settings

      Option Description

      Email Server Host

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

      Port

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

      Username

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

      Password

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

      Require encryption (TLS)

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

      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.

      Recipients

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

      Send Test Email

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

      Saving and Testing the Alert Configuration

      When you have entered appropriate data into the fields, proceed as follows:

      1. Save the configuration, by clicking on the Save button, at the bottom of the screen:

        saveEmailAlertsConfiguration

        Note that when you click on Save, 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.

        Alternatively, click on Cancel/Reset, to remove the configuration.

      2. Optionally, click on the Send Test Email button, to send a test email.

      Available Alerts

      The Available Alerts panel provides a list of all available alerts, and allows you to select, by means of interactive checkboxes, the subset of alert messages that you wish to be sent. The listed alerts are are follows.

      Alert Description Code

      Node was auto-failed-over

      The sending node has been failed over automatically.

      auto_failover_node

      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.

      auto_failover_maximum_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.

      auto_failover_other_nodes_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.

      auto_failover_cluster_too_small

      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.

      auto_failover_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.

      ip

      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.

      disk

      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.

      overhead

      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.

      ep_oom_errors

      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.

      ep_item_commit_failed

      Writing event to audit log has failed

      The audit log event writing has failed.

      audit_dropped_events

      Approaching full Indexer RAM warning

      The indexer RAM limit threshold is approaching warning.

      indexer_ram_max_usage

      Remote mutation timestamp exceeded drift threshold

      The remote mutation timestamp exceeded drift threshold warning.

      ep_clock_cas_drift_threshold_exceeded

      Communication issues among some nodes in the cluster

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

      communication_issue

      On-demand pricing reporting issues

      There are issues with the reporting of on-demand pricing.

      odp_report_failed

      Configure Email Alerts with the CLI

      To configure email alerts with the Couchbase CLI, use the setting-alert command, as follows:

      couchbase-cli setting-alert -c 10.143.192.101 --username Administrator \
      --password password --enable-email-alert 1 --email-user admin \
      --email-password password --email-host mail.couchbase.com --email-port 25 \
      --email-recipients user1@couchbase.com,user2@couchbase.com \
      --email-sender noreply@couchbase.com --enable-email-encrypt 0 \
      --alert-auto-failover-node --alert-auto-failover-max-reached \
      --alert-auto-failover-node-down --alert-auto-failover-cluster-small

      In this example, cluster 10.143.192.101 is accessed, with administor username and password specified. The enable-email-alert flag is specified as 1, enabling email alerts. Additional flags specify the username and password required by the mail server, as well as email host, port, recipients, and sender. The enable-mail-encrypt flag specifies encryption as off.

      Four additional flags are used to indicate which alerts should be sent. Every possible alert has a flag: if a flag is not specified, the corresponding alert will not be sent. If the above command is executed, subsequently, the Available Alerts panel on the Email Alerts screen appears as follows:

      availableAlertsPanelAfterReconfiguration

      See Email Settings and Available Alerts, above, for descriptions of settings and alerts. See setting-alert for further information on using the CLI, including a full list of command-line parameters.

      Configure Email Alerts with REST

      To configure email alerts with the Couchbase REST API, use the /settings/alerts method, as follows:

      curl -v -X POST http://10.143.192.101:8091/settings/alerts \
      -u Administrator:password  \
      -d 'emailPass=password' \
      -d 'alerts=auto_failover_node,auto_failover_maximum_reached,auto_failover_other_nodes_down,auto_failover_cluster_too_small' \
      -d 'sender=noreply@couchbase.com' \
      -d 'recipients=user1@couchbase.com,user2@couchbase.com' \
      -d 'emailHost=mail.couchbase.com' \
      -d 'emailPort=25' \
      -d 'emailEncrypt=false' \
      -d 'enabled=true'

      This example demonstrates flags that specify mail-server password, sender, recipients, host, and port. Emails settings are enabled with the enabled flag; and encryption is specified as off, by means of the emailEncrypt flag. A list of the alerts that can be sent is provided as the value to the alerts flag. See the Code column of the Available Alerts table, above, for additional event-codes. See Email Settings, above, for a description of available settings.