From e61224778f306d9dd4c9c5d9e67fe3cf7aef82a6 Mon Sep 17 00:00:00 2001 From: Clinton Gormley Date: Fri, 28 Apr 2017 12:34:53 +0200 Subject: [PATCH] Fixed bad link Original commit: elastic/x-pack-elasticsearch@f7ab965eba51e07b7a2718344cd670bef4a7026b --- .../example-watches/example-watch-clusterstatus.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/watcher/example-watches/example-watch-clusterstatus.asciidoc b/docs/en/watcher/example-watches/example-watch-clusterstatus.asciidoc index dfc3c2c6f2f..7eef62a8831 100644 --- a/docs/en/watcher/example-watches/example-watch-clusterstatus.asciidoc +++ b/docs/en/watcher/example-watches/example-watch-clusterstatus.asciidoc @@ -101,7 +101,7 @@ PUT _xpack/watcher/watch/cluster_health_watch It would be a good idea to create a user with the minimum privileges required for use with such a watch configuration. Depending on how your cluster is configured, there may be additional settings required before the watch can access your cluster such as keystores, truststores or certificates. -See the {ref}//notification-settings.html[Notification Settings] section of the X-Pack Settings documentation. +See the <> section of the X-Pack Settings documentation. If you check the watch history, you'll see that the cluster status is recorded