[DOCS] Updates terminology for alerting features (#43945)
This commit is contained in:
parent
c00b082701
commit
753da8feac
|
@ -37,10 +37,10 @@ All of these use-cases share a few key properties:
|
||||||
3rd party system is notified, or the query results are stored.
|
3rd party system is notified, or the query results are stored.
|
||||||
|
|
||||||
[float]
|
[float]
|
||||||
=== How Watches Work
|
=== How watches work
|
||||||
|
|
||||||
{xpack} provides an API for creating, managing and testing _watches_. A watch
|
The {alert-features} provide an API for creating, managing and testing _watches_.
|
||||||
describes a single alert and can contain multiple notification actions.
|
A watch describes a single alert and can contain multiple notification actions.
|
||||||
|
|
||||||
A watch is constructed from four simple building blocks:
|
A watch is constructed from four simple building blocks:
|
||||||
|
|
||||||
|
|
|
@ -3,7 +3,7 @@
|
||||||
|
|
||||||
[partintro]
|
[partintro]
|
||||||
--
|
--
|
||||||
{xpack} alerting is a set of administrative features that enable you to watch
|
The {alert-features} enable you to watch
|
||||||
for changes or anomalies in your data and perform the necessary actions in
|
for changes or anomalies in your data and perform the necessary actions in
|
||||||
response. For example, you might want to:
|
response. For example, you might want to:
|
||||||
|
|
||||||
|
@ -38,10 +38,10 @@ All of these use-cases share a few key properties:
|
||||||
3rd party system is notified, or the query results are stored.
|
3rd party system is notified, or the query results are stored.
|
||||||
|
|
||||||
[float]
|
[float]
|
||||||
=== How Watches Work
|
=== How watches work
|
||||||
|
|
||||||
{xpack} provides an API for creating, managing and testing _watches_. A watch
|
The {alert-features} provide an API for creating, managing and testing _watches_.
|
||||||
describes a single alert and can contain multiple notification actions.
|
A watch describes a single alert and can contain multiple notification actions.
|
||||||
|
|
||||||
A watch is constructed from four simple building blocks:
|
A watch is constructed from four simple building blocks:
|
||||||
|
|
||||||
|
|
|
@ -1,5 +1,5 @@
|
||||||
[[schedule-cron]]
|
[[schedule-cron]]
|
||||||
==== `cron` Schedule
|
==== `cron` schedule
|
||||||
|
|
||||||
A <<trigger-schedule, `schedule`>> trigger that enables you to use a
|
A <<trigger-schedule, `schedule`>> trigger that enables you to use a
|
||||||
https://en.wikipedia.org/wiki/Cron[cron] style expression to specify when you
|
https://en.wikipedia.org/wiki/Cron[cron] style expression to specify when you
|
||||||
|
@ -213,7 +213,8 @@ minute during the weekend:
|
||||||
[[croneval]]
|
[[croneval]]
|
||||||
===== Verifying Cron Expressions
|
===== Verifying Cron Expressions
|
||||||
|
|
||||||
{xpack} ships with a `elasticsearch-croneval` command line tool that you can use to verify that
|
The {es} {alert-features} provide a `elasticsearch-croneval` command line tool
|
||||||
|
that you can use to verify that
|
||||||
your cron expressions are valid and produce the expected results. This tool is
|
your cron expressions are valid and produce the expected results. This tool is
|
||||||
provided in the `$ES_HOME/bin` directory.
|
provided in the `$ES_HOME/bin` directory.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue