You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: explore-analyze/alerts-cases/alerts.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ For example, when monitoring a set of servers, a rule might:
28
28
29
29
Each project type supports a specific set of rule types. Each *rule type* provides its own way of defining the conditions to detect, but an expression formed by a series of clauses is a common pattern. For example, in an {{es}} query rule, you specify an index, a query, and a threshold, which uses a metric aggregation operation (`count`, `average`, `max`, `min`, or `sum`):
:alt: UI for defining rule conditions in an {{es}} query rule
33
33
:screenshot:
34
34
:::
@@ -56,14 +56,14 @@ Each action uses a connector, which provides connection information for a {{kib}
56
56
57
57
After you select a connector, set the *action frequency*. If you want to reduce the number of notifications you receive without affecting their timeliness, some rule types support alert summaries. For example, if you create an {{es}} query rule, you can set the action frequency such that you receive summaries of the new, ongoing, and recovered alerts on a custom interval:
:alt: UI for defining rule conditions in an {{es}} query rule
61
61
:screenshot:
62
62
:::
63
63
64
64
Alternatively, you can set the action frequency such that the action runs for each alert. If the rule type does not support alert summaries, this is your only available option. You must choose when the action runs (for example, at each check interval, only when the alert status changes, or at a custom action interval). You must also choose an action group, which affects whether the action runs. Each rule type has a specific set of valid action groups. For example, you can set *Run when* to `Query matched` or `Recovered` for the {{es}} query rule:
@@ -93,7 +93,7 @@ To get notified only once when a server exceeds the threshold, you can set the a
93
93
94
94
You can pass rule values to an action at the time a condition is detected. To view the list of variables available for your rule, click the "add rule variable" button:
@@ -110,7 +110,7 @@ Using the server monitoring example, each server with average CPU > 0.9 is track
110
110
111
111
A rule consists of conditions, actions, and a schedule. When conditions are met, alerts are created that render actions and invoke them. To make action setup and update easier, actions use connectors that centralize the information used to connect with {{kib}} services and third-party integrations. The following example ties these concepts together:
Copy file name to clipboardExpand all lines: explore-analyze/alerts-cases/alerts/alerting-getting-started.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ navigation_title: Getting started with alerts
9
9
10
10
Alerting enables you to define *rules*, which detect complex conditions within different {{kib}} apps and trigger actions when those conditions are met. Alerting is integrated with [**{{observability}}**](../../../solutions/observability/incident-management/alerting.md), [**Security**](security-docs://reference/prebuilt-rules/index.md), [**Maps**](../../../explore-analyze/alerts-cases/alerts/geo-alerting.md) and [**{{ml-app}}**](../../../explore-analyze/machine-learning/anomaly-detection/ml-configuring-alerts.md). It can be centrally managed from **{{stack-manage-app}}** and provides a set of built-in [connectors](../../../deploy-manage/manage-connectors.md) and [rules](../../../explore-analyze/alerts-cases/alerts/rule-types.md#stack-rules) for you to use.
@@ -89,15 +89,15 @@ When checking for a condition, a rule might identify multiple occurrences of the
89
89
90
90
Using the server monitoring example, each server with average CPU > 0.9 is tracked as an alert. This means a separate email is sent for each server that exceeds the threshold whenever the alert status changes.
:alt: {{kib}} tracks each detected condition as an alert and takes action on each alert
94
94
:::
95
95
96
96
## Putting it all together [_putting_it_all_together]
97
97
98
98
A rule consists of conditions, actions, and a schedule. When conditions are met, alerts are created that render actions and invoke them. To make action setup and update easier, actions use connectors that centralize the information used to connect with {{kib}} services and third-party integrations. The following example ties these concepts together:
Copy file name to clipboardExpand all lines: explore-analyze/alerts-cases/alerts/alerting-troubleshooting.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ The following debugging tools are available:
31
31
32
32
**{{rules-ui}}** in **{{stack-manage-app}}** lists the rules available in the space you’re currently in. When you click a rule name, you are navigated to the [details page](create-manage-rules.md#rule-details) for the rule, where you can see currently active alerts. The start date on this page indicates when a rule is triggered, and for what alerts. In addition, the duration of the condition indicates how long the instance is active.
@@ -40,7 +40,7 @@ The following debugging tools are available:
40
40
41
41
When creating or editing an index threshold rule, you see a graph of the data the rule will operate against, from some date in the past until now, updated every 5 seconds.
Copy file name to clipboardExpand all lines: explore-analyze/alerts-cases/alerts/create-manage-rules.md
+11-11Lines changed: 11 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ The **{{stack-manage-app}}** > **{{rules-ui}}** UI provides a cross-app view of
12
12
13
13
You can find **Rules** in **Stack Management** > **Alerts and insights** > **Rules** in {{kib}} or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
@@ -43,7 +43,7 @@ Depending on the {{kib}} app and context, you might be prompted to choose the ty
43
43
44
44
Each rule type provides its own way of defining the conditions to detect, but an expression formed by a series of clauses is a common pattern. For example, in an {{es}} query rule, you specify an index, a query, and a threshold, which uses a metric aggregation operation (`count`, `average`, `max`, `min`, or `sum`):
:alt: UI for defining rule conditions in an {{es}} query rule
48
48
:screenshot:
49
49
:::
@@ -68,14 +68,14 @@ If you choose a custom action interval, it cannot be shorter than the rule’s c
68
68
69
69
For example, if you create an {{es}} query rule, you can send notifications that summarize the new, ongoing, and recovered alerts on a custom interval:
:alt: UI for defining alert summary action in an {{es}} query rule
73
73
:screenshot:
74
74
:::
75
75
76
76
When you choose to run actions for each alert, you must specify an action group. Each rule type has a set of valid action groups, which affect when an action runs. For example, you can set **Run when** to `Query matched` or `Recovered` for the {{es}} query rule:
@@ -105,7 +105,7 @@ To get notified only once when a server exceeds the threshold, you can set the a
105
105
106
106
You can pass rule values to an action at the time a condition is detected. To view the list of variables available for your rule, click the "add rule variable" button:
@@ -116,13 +116,13 @@ For more information about common action variables, refer to [*Rule action varia
116
116
117
117
The rule listing enables you to quickly snooze, disable, enable, or delete individual rules. For example, you can change the state of a rule:
118
118
119
-
![Use the rule status dropdown to enable or disable an individual rule](../../../images/kibana-individual-enable-disable.png"")
119
+
![Use the rule status dropdown to enable or disable an individual rule](/explore-analyze/images/kibana-individual-enable-disable.png"")
120
120
121
121
If there are rules that are not currently needed, disable them to stop running checks and reduce the load on your cluster.
122
122
123
123
When you snooze a rule, the rule checks continue to run on a schedule but alerts will not generate actions. You can snooze for a specified period of time, indefinitely, or schedule single or recurring downtimes:
124
124
125
-
![Snooze notifications for a rule](../../../images/kibana-snooze-panel.png"")
125
+
![Snooze notifications for a rule](/explore-analyze/images/kibana-snooze-panel.png"")
126
126
127
127
When a rule is in a snoozed state, you can cancel or change the duration of this state.
128
128
@@ -143,16 +143,16 @@ You can determine the health of a rule by looking at the **Last response** in **
143
143
144
144
Click the rule name to access a rule details page:
In this example, the rule detects when a site serves more than a threshold number of bytes in a 24 hour period. Four sites are above the threshold. These are called alerts - occurrences of the condition being detected - and the alert name, status, time of detection, and duration of the condition are shown in this view. Alerts come and go from the list depending on whether the rule conditions are met. For more information about alerts, go to [*View alerts*](view-alerts.md).
152
152
153
-
If there are rule actions that failed to run successfully, you can see the details on the **History** tab. In the **Message** column, click the warning or expand icon ![double arrow icon to open a flyout with the document details](../../../images/kibana-expand-icon-2.png"") or click the number in the **Errored actions** column to open the **Errored Actions** panel. In this example, the action failed because the [`xpack.actions.email.domain_allowlist`](kibana://reference/configuration-reference/alerting-settings.md#action-config-email-domain-allowlist) setting was updated and the action’s email recipient is no longer included in the allowlist:
153
+
If there are rule actions that failed to run successfully, you can see the details on the **History** tab. In the **Message** column, click the warning or expand icon ![double arrow icon to open a flyout with the document details](/explore-analyze/images/kibana-expand-icon-2.png"") or click the number in the **Errored actions** column to open the **Errored Actions** panel. In this example, the action failed because the [`xpack.actions.email.domain_allowlist`](kibana://reference/configuration-reference/alerting-settings.md#action-config-email-domain-allowlist) setting was updated and the action’s email recipient is no longer included in the allowlist:
:alt: Creating a tracking containment rule in Kibana
22
22
:screenshot:
23
23
:::
@@ -41,7 +41,7 @@ For each action, you must choose a connector, which provides connection informat
41
41
42
42
After you select a connector, you must set the action frequency. You can choose to create a summary of alerts on each check interval or on a custom interval. Alternatively, you can set the action frequency such that actions run for each alert. Choose how often the action runs (at each check interval, only when the alert status changes, or at a custom action interval). You must also choose an action group, which indicates whether the action runs when the containment condition is met or when an entity is no longer contained. Each connector supports a specific set of actions for each action group. For example:
@@ -52,7 +52,7 @@ You can further refine the conditions under which actions run by specifying that
52
52
53
53
You can pass rule values to an action to provide contextual details. To view the list of variables available for each action, click the "add rule variable" button. For example:
Copy file name to clipboardExpand all lines: explore-analyze/alerts-cases/alerts/maintenance-windows.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ mapped_urls:
9
9
10
10
# Maintenance windows
11
11
12
-
This content applies to: [![Observability](../../../images/serverless-obs-badge.svg"")](../../../solutions/observability.md)[![Security](../../../images/serverless-sec-badge.svg"")](../../../solutions/security/elastic-security-serverless.md)
12
+
This content applies to: [![Observability](/explore-analyze/images/serverless-obs-badge.svg"")](../../../solutions/observability.md)[![Security](/explore-analyze/images/serverless-sec-badge.svg"")](../../../solutions/security/elastic-security-serverless.md)
13
13
14
14
15
15
::::{warning}
@@ -40,7 +40,7 @@ In **Management > {{stack-manage-app}} > Maintenance Windows** or **{{project-se
40
40
41
41
When you create a maintenance window, you must provide a name and a schedule. You can optionally configure it to repeat daily, monthly, yearly, or on a custom interval.
0 commit comments