When you set out to create an alert, you’ll need to start with a query. If you haven’t formed your query yet, we recommend starting in Kibana so you can see the results of the query in real time.
If you already have a query and filters, you can create a blank alert from the top menu (Alerts & Events > New alert) or from the Alert definitions page.
You can also create an alert from Application Insights or Cognitive Insights, or you can duplicate an existing alert.
Community plans can have up to 50 alerts enabled at a time.
To create an alert in Kibana
Refine your search query and filters, and review the returned logs to make sure you got the expected results.
Alerts support Lucene query language only. You won’t be able to create an alert from a search written in Kibana Query Language (KQL).
Once you’re happy with your alert, click Create alert (above the query bar). You’re taken to the New alert page.
Continue with To configure an alert. 👇
To create an alert from another alert
You can duplicate an alert from the Alert definitions page when you want to reuse its configuration without recreating it from scratch. To do this, hover over the alert, click its action menu (), and then click Duplicate. You’re taken to the Edit alert page.
Continue with To configure an alert. 👇
To configure an alert
Name the alert
Give your alert a meaningful name.
If your alert is triggered, the name is used as the email subject or Slack heading. A helpful name gives the quick need-to-know-now information and doesn’t use unnecessary words.
Edit the search settings
Query and filters
If you need to change your alert query and filters, do that now.
Your query is an important source of information when you’re investigating a triggered alert. Shorten your query by using filters whenever you can.
Moving down, you’ll come to the Group by setting next.
With Group by, you can choose up to 3 fields to group. The alert will return the aggregated results for each group.
Careful: The order of group by fields matters. Results are grouped by the leftmost field, then the center field, then the right field.
The image above groups results by continent, then country, then city. If we had reversed the order (city, then country, then continent), it would likely generate unintended results.
Accounts to search
Next you’ll choose the Accounts to search.
If you choose All accounts, this alert will query the logs in all the accounts it has access to. This will include future accounts.
To limit the alert to a set list of accounts, click Just these accounts, and add the accounts you want. This list is always limited to your selection, so you’ll need to manually update the list if you need it to change.
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 levels, each with its own severity tag.
(Optional) Set notification details
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 the Alert definitions page.
Who to send it to
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. If you need help adding a new endpoint, see Notification endpoints.
To limit how often recipients are notified, choose a time period to suppress notifications.
When notifications are suppressed, Logz.io will continue to log triggered alerts without sending notifications. You can search triggered alert logs at any time.
Recipients will receive the notification with sample data, so you’ll need to choose whether to send the data as JSON or in a Table.
If you’re sending a sample JSON, you can include All fields or Custom fields. If you’re sending a table with sample data, you can include up to 7 fields.
For custom fields, click Add a field to add the field to your output. You can optionally sort by one field or filter the samples with a regular expression.
If you added any groups or used an aggregated trigger condition (minimum, maximum, average, or sum), the output will include only the grouped or aggregated fields. To change these fields, you’ll need to first change your Group by or Trigger if... settings.
Click Save to save your alert. If the thresholds are passed and the alert is triggered, Logz.io will log the alert and send the configured notifications.