我的书签
添加书签
移除书签Defining alerts
Kibana alerts can be created in a variety of apps including APM, Metrics, SIEM, Uptime and from Management UI. While alerting details may differ from app to app, they share a common interface for defining and configuring alerts that this section describes in more detail.
Alert flyout
When an alert is created in an app, the app will display a flyout panel with three main sections to configure:
General alert details
All alert share the following four properties in common:
Name
The name of the alert. While this name does not have to be unique, the name can be referenced in actions and also appears in the searchable alert listing in the management UI. A distinctive name can help identify and find an alert.
Tags
A list of tag names that can be applied to an alert. Tags can help you organize and find alerts, because tags appear in the alert listing in the management UI which is searchable by tag.
Check every
This value determines how frequently the alert conditions below are checked. Note that the timing of background alert checks are not guaranteed, particularly for intervals of less than 10 seconds. See Scale and performance for more information.
Notify every
This value limits how often actions are repeated when an alert instance remains active across alert checks. See Suppressing duplicate notifications for more information.
Alert type and conditions
Depending upon the Kibana app and context, you may be prompted to choose the type of alert you wish to create. Some apps will pre-select the type of alert for you.
Each alert type provides its own way of defining the conditions to detect, but an expression formed by a series of clauses is a common pattern. Each clause has a UI control that allows you to define the clause. For example, in an index threshold alert the WHEN clause allows you to select an aggregation operation to apply to a numeric field.
Action type and action details
To add an action to an alert, you first select the type of action:
Each action must specify a connector instance. If no connectors exist for that action type, click “Add new” to create one.
Each action type exposes different properties. For example an email action allows you to set the recipients, the subject, and a message body in markdown format. See Action and connector types for details on the types of actions provided by Kibana and their properties.
Using the Mustache template syntax {{variable name}}, you can pass alert values at the time a condition is detected to an action. Available variables differ by alert type, and a list can be accessed using the “add variable” button.
You can attach more than one action. Clicking the “Add action” button will prompt you to select another alert type and repeat the above steps again.
Actions are not required on alerts. In some cases you may want to run an alert without actions first to understand its behavior, and configure actions later.
Managing alerts
To modify an alert after it was created, including muting or disabling it, use the alert listing in the Management UI.
