You can set up log alerts to automatically get notified about issues that demand attention.

Community plans have a limit on the number of alerts that may be enabled. See the official pricing page for details.

Configuring an alert

Name the alert

Give your alert a meaningful name. When your alert triggers, its name is used as the email subject or notification heading.

Search components

Next, set the search components. This determines which logs to look for and in which accounts.

If you intend to create a correlated alert with 2 queries, see the this guide.

Alert group by settings

To perform date range filtering on the @timestamp field, include the field as part of a query, rather than by adding it as a filter: @timestamp filters are overwritten.

Query and filters

You can use any combination of filters and a search query. Note the following:

  • Use a Lucene search query.
    • You have the option to use wildcards.
    • Kibana Query Language (KQL) is not supported.
  • All filters are accepted, including: is, is not, is one of, is not one of, exists, does not exist.

Once you’re done refining your search query and filters, you can click Preview in Kibana to open Kibana Discover in another tab. It can help to review the returned logs and make sure you get the expected results.

Group-by (order matters!)

You have the option to apply group by operators to up to 3 fields. If you use this option, the alert will return the aggregated results.

The order of group-by fields matters. Results are grouped in the order in which the group-by fields are added. (The fields are shown from first to last from Left-To-Right.)

For example, the following will group results by continent, then country, then city:

Ordered group by field functions

If we reverse the order (city, then country, then continent), it will likely generate unintended results.

Next, select the Accounts to search. An account is the equivalent of an Elasticsearch index.

  • If you select All accounts, the alert will query the logs in all the accounts it has access to. It will automatically include any accounts added in the future.

  • You can select specific accounts. Select Just these accounts and add the relevant accounts from the dropdown list.

Set threshold and severity levels

Set your threshold and severity levels.

In the Trigger if... section, click + Add a threshold to set up to 5 threshold conditions, each with its own severity tag.

Alert trigger thresholds

Set alert schedule

You can use the scheduling mechanism to manage the trigger condition frequency.

Scheduling defines the frequency and the time frame for the alerts. To define a schedule, select On Schedule and use a cron expression to specify when to trigger the alert.

The cron expression can only be set in increments rounded to the nearest minute.

Schedule alert screen

For example, you can apply the following schedule to your alerts:

Cron expression Alert trigger schedule
0 0/10 * ? * * * Every 10 minutes
0 0 0/1 ? * * * Rounded to the nearest hour
0 * 8-17 ? * MON,TUE,WED,THU,FRI * Every minute between 8 am to 5 pm, Monday through Friday
0 5 0 ? * * * Every day at exactly 12:05 am

By default, trigger conditions run approximately every minute. If there’s a lag, the alert is not checked until all data reaches Elastic. In addition, once an alert has met its condition and is triggered, it won’t be checked again for the remainder of the alert trigger condition time range.

(Optional) Set notification details
Description and tags

Alert description and tags

The Description is visible on the Alert definitions page. It’s also included with emails and Slack messages when the alert is triggered. We recommend making your description helpful to recipients, like telling them how to fix the issues that led to the alert.

The Tags are useful for filtering. They can be used to create filtered visualizations and dashboards or to filter the Alert definitions page.

Who to send it to

Recipients and wait between notifications

If you want to send notifications or emails when the alert is triggered, choose notification endpoints. This isn’t required, though—triggered alerts are still logged and searchable in Kibana.

Choose the endpoints or email addresses to notify under Who to send it to.

Add an email address as a recipient

To use an email as your endpoint, you need to type the email in the Recipients table and click enter.

Enter custom email

If you need help adding a new endpoint, see Notification endpoints.

To limit how often recipients are notified, choose a time period to wait between sending out notifications. will continue to log triggered alerts without sending notifications, and you will be able to review triggered alerts directly from the platform at any time.

Output format & content

When triggered, the alert will send out a notification with sample data.

Sample data can be sent in either JSON or Table formats. Toggle the button to select your preferred format.

If the alert includes any aggregation or group by field, the notification output will send the aggregated results by default.

Output format

To be selective about the output, click Add a field and select a field from the dropdown list. If you want, you can also add a sorting rule and a regex filter. Learn more about regex filters for alert notifications

  • If you select JSON format, you can send the full log (with all fields) or select as many as 7 fields.
  • If you select Table, you can send as many as 7 fields.

Output table

Save it!

Click Save to save your alert. If the thresholds are passed and the alert is triggered, will log the alert and send the configured notifications.