@@ -211,27 +211,21 @@ minute during the weekend:
211
211
// NOTCONSOLE
212
212
213
213
[[croneval]]
214
- ===== Verifying Cron Expressions
214
+ ===== Verifying cron expressions
215
215
216
- The {es} {alert-features} provide a `elasticsearch-croneval` command line tool
217
- that you can use to verify that
218
- your cron expressions are valid and produce the expected results. This tool is
219
- provided in the `$ES_HOME/bin` directory.
216
+ The {es} {alert-features} provide a
217
+ {ref}/elasticsearch-croneval.html[`elasticsearch-croneval`] command line tool
218
+ that you can use to verify that your cron expressions are valid and produce the
219
+ expected results. This tool is provided in the `$ES_HOME/bin` directory.
220
220
221
- To verify a cron expression, simply pass it in as a parameter to `elasticsearch-croneval`:
221
+ To verify a cron expression, simply pass it in as a parameter to
222
+ `elasticsearch-croneval`:
222
223
223
224
[source,bash]
224
225
--------------------------------------------------
225
226
bin/elasticsearch-croneval "0 0/1 * * * ?"
226
227
--------------------------------------------------
227
228
228
- If the cron expression is valid, `elasticsearch-croneval` displays the next 10 times that the
229
- schedule will be triggered.
230
-
231
- You can specify the `-c` option to control how many future trigger times are
232
- displayed. For example, the following command displays the next 20 trigger times:
233
-
234
- [source,bash]
235
- --------------------------------------------------
236
- bin/elasticsearch-croneval "0 0/1 * * * ?" -c 20
237
- --------------------------------------------------
229
+ If the cron expression is valid, `elasticsearch-croneval` displays the next 10
230
+ times that the schedule will be triggered. You can specify the `-c` option to
231
+ control how many future trigger times are displayed.
0 commit comments