When monitoring big data platforms in real time, O&M teams need to be promptly notified of cluster health status or any abnormal changes in service metrics. Although Elasticsearch provides powerful search capabilities, the native engine lacks deep integration with cloud-native notification services. CSS addresses this by offering a built-in Open Distro alerting plugin that integrates seamlessly with the Simple Message Notification (SMN) service. This integration enables a highly automated monitoring workflow: monitors are configured to query specified indexes periodically; triggers evaluate the query results against predefined thresholds to identify anomalies and generate alerts; CSS then calls the SMN API to push alerts to subscribers.
CSS Elasticsearch clusters provide the built-in open-source Open Distro alerting plugin, which triggers alerts and sends notifications via SMN when predefined conditions are met.
Figure 1 Alert notification link

For details about the Open Distro alerting plugin, see the official document Open Distro Alerting.
Only Elasticsearch 7.6.2 and 7.10.2 clusters provide a built-in Open Distro alerting plugin. Only clusters of these versions support alert notification via SMN.
The CSS administrator account must have the following minimum IAM permissions:
Log in using an account with CSS permissions.
Parameter | Description |
|---|---|
Name | User-defined destination name. You are advised to use English letters and digits. |
Type | Type of the notification. Select SMN. |
Topic | An associated SMN topic. Select the SMN topic created in Preparations. |
Figure 2 Add destination

Figure 3 Destination list

Parameter | Description | |
|---|---|---|
Configure monitor | Monitor name | User-defined monitor name |
Monitor state | Whether to disable the monitor.
| |
Define monitor | Method of definition | Select a method to define the monitor. You are advised to use Define using extraction query.
|
Index | Index to be monitored | |
Time field | Timestamp used for time-based aggregations, such as count. This parameter is required only when you select Define using visual graph to define the monitor. | |
Monitor schedule | Frequency | Select the monitor frequency and set the monitor interval. The options include:
|
Parameter | Description | |
|---|---|---|
Define trigger | Trigger name | User-defined trigger name |
Severity level | Sensitivity of a trigger, that is, the number of alerts that need to be triggered before a notification is sent. 1 indicates the highest sensitivity. | |
Trigger condition | Trigger condition. An alert is triggered when the trigger condition is hit. | |
Configure actions | Action name | Name of a trigger action |
Destination | Select the SMN destination created in 5. | |
Message subject | Message title. This parameter is required only for Elasticsearch 7.10.2 clusters. | |
Message | Message body. By default, the subject and body are defined when the destination is an email address. | |
Action throttling | Specify the message frequency to limit the number of notifications you receive within a given span of time. Without it, high-frequency or low-severity triggers may cause information overload or result in unexpected cloud costs. For example, if this parameter is set to 10 minutes, SMN sends only one alert notification in the next 10 minutes even if the trigger condition is hit multiple times. After 10 minutes, SMN sends another notification if the trigger condition is met again. | |
Figure 4 Setting the destination of a trigger action

Figure 5 Sending a test message

Figure 6 Email notification
