From 57d7ee0aaa40002b9f0a99878530f220144ada30 Mon Sep 17 00:00:00 2001 From: Omurbek Date: Sat, 2 Oct 2021 23:53:48 +0300 Subject: [PATCH] Added missed "template" settings --- _im-plugin/ism/policies.md | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/_im-plugin/ism/policies.md b/_im-plugin/ism/policies.md index ec4bf737..afad9396 100644 --- a/_im-plugin/ism/policies.md +++ b/_im-plugin/ism/policies.md @@ -558,9 +558,11 @@ The following sample template policy is for a rollover use case. PUT _index_template/ism_rollover { "index_patterns": ["log*"], - "settings": { - "plugins.index_state_management.rollover_alias": "log" - } + "template": { + "settings": { + "opendistro.index_state_management.rollover_alias": "log" + } + } } ``` @@ -586,6 +588,12 @@ The following sample template policy is for a rollover use case. } ``` +5. Verify if the policy is attached to the `log-000001` index: + + ```json + GET _opendistro/_ism/explain/log-000001?pretty + ``` + ## Example policy The following example policy implements a `hot`, `warm`, and `delete` workflow. You can use this policy as a template to prioritize resources to your indices based on their levels of activity.