From 9a1a8d94339b0da10013d14c08755a23fd76061b Mon Sep 17 00:00:00 2001 From: Luke Whiting Date: Mon, 31 Mar 2025 10:27:20 +0100 Subject: [PATCH] Update missed documentation change for new watcher index settings (#125758) * Update missed documentation change for new watcher index settings * Update docs/reference/rest-api/watcher/update-settings.asciidoc Co-authored-by: Keith Massey --------- Co-authored-by: Keith Massey --- docs/reference/rest-api/watcher/update-settings.asciidoc | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/reference/rest-api/watcher/update-settings.asciidoc b/docs/reference/rest-api/watcher/update-settings.asciidoc index 9ad38064e34ab..c0ab23230d064 100644 --- a/docs/reference/rest-api/watcher/update-settings.asciidoc +++ b/docs/reference/rest-api/watcher/update-settings.asciidoc @@ -11,10 +11,17 @@ For the most up-to-date API details, refer to {api-es}/group/endpoint-watcher[{watcher} APIs]. -- -This API allows a user to modify the settings for the Watcher internal index (`.watches`). Only a subset of settings are allowed to by modified. This includes: +This API allows a user to modify the settings for the Watcher internal index (`.watches`). Only a subset of settings +are allowed to be modified. This includes: - `index.auto_expand_replicas` - `index.number_of_replicas` +- Any setting with the prefix `index.routing.allocation.exclude.` +- Any setting with the prefix `index.routing.allocation.include.` +- Any setting with the prefix `index.routing.allocation.require.` + +Modification of `index.routing.allocation.include._tier_preference` is an exception and is not allowed as the Watcher +shards must always be in the `data_content` tier. An example of modifying the Watcher settings: