You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently a custom ILM policy must be created using the Elasticsearch REST API call after started. It is rather difficult to implement in a docker-compose application.
It would make the devops's life much easier if the default-ilm-policy.json could be replaced by some configuration option.
This is the relevant code snippet from the elasticsearch plugin:
def policy_payload
policy_path = ::File.expand_path(ILM_POLICY_PATH, ::File.dirname(__FILE__))
LogStash::Json.load(::IO.read(policy_path))
end
The new feature would allow to set policy_path from a new elasticsearch output option, in a similar way as the ILM template may be set with the template option.
The text was updated successfully, but these errors were encountered:
Hello,
currently a custom ILM policy must be created using the Elasticsearch REST API call after started. It is rather difficult to implement in a docker-compose application.
It would make the devops's life much easier if the default-ilm-policy.json could be replaced by some configuration option.
This is the relevant code snippet from the elasticsearch plugin:
The new feature would allow to set policy_path from a new elasticsearch output option, in a similar way as the ILM template may be set with the template option.
The text was updated successfully, but these errors were encountered: