mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 01:13:23 -04:00
[Alerting][Docs] Updating docs for notify only on action group change (#92084)
* Updating docs for notify only on state change * PR fixes * Update docs/user/alerting/defining-alerts.asciidoc Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>
This commit is contained in:
parent
0c2495a7e1
commit
192f19e30c
4 changed files with 6 additions and 2 deletions
|
@ -22,12 +22,16 @@ image::images/alert-flyout-sections.png[The three sections of an alert definitio
|
|||
All alert share the following four properties in common:
|
||||
|
||||
[role="screenshot"]
|
||||
image::images/alert-flyout-general-details.png[alt='All alerts have name, tags, check every, and notify every properties in common']
|
||||
image::images/alert-flyout-general-details.png[alt='All alerts have name, tags, check every, and notify 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 <<alerting-production-considerations>> for more information.
|
||||
Notify every:: This value limits how often actions are repeated when an alert instance remains active across alert checks. See <<alerting-concepts-suppressing-duplicate-notifications>> for more information.
|
||||
Notify:: This value limits how often actions are repeated when an alert instance remains active across alert checks. See <<alerting-concepts-suppressing-duplicate-notifications>> for more information. +
|
||||
- **Only on status change**: Actions are not repeated when an alert instance remains active across checks. Actions run only when the alert status changes.
|
||||
- **Every time alert is active**: Actions are repeated when an alert instance remains active across checks.
|
||||
- **On a custom action interval**: Actions are suppressed for the throttle interval, but repeat when an alert instance remains active across checks for a duration longer than the throttle interval.
|
||||
|
||||
|
||||
[float]
|
||||
[[defining-alerts-type-conditions]]
|
||||
|
|
Binary file not shown.
Before Width: | Height: | Size: 182 KiB After Width: | Height: | Size: 171 KiB |
Binary file not shown.
Before Width: | Height: | Size: 33 KiB After Width: | Height: | Size: 249 KiB |
Binary file not shown.
Before Width: | Height: | Size: 46 KiB After Width: | Height: | Size: 60 KiB |
Loading…
Add table
Add a link
Reference in a new issue