Hi,
Does unpacking of X-Pack bundle overwrites the existing config files of installed ELK setup?
Thanks!
Hi,
X-Pack installation will not overwrite your elasticsearch.yml, kibana.yml or logstash.yml respectively. In the case of Elasticsearch, it will also create an x-pack directory within your $ES_CONFIG_PATH with some x-pack related config files.
Hope this answers your question.
Thanks Ioannis. However, I learnt from elastic documentation that all X-Pack features are enabled (by default). Please confirm.
Hi,
I am sorry but I'm not sure I understand how your two posts are connected or what the actual question is. X-Pack features are enabled by default and X-Pack installation doesn't overwrite your existing config files.
okay, sorry to bother you here. Do you mean the implementer has to configure the respective YML files that do not have all the x-pack parameters?
and if we have to configure – the implementer has to go through documentation, copy paste the parameters and configure them. There are too many factors that can possibly go wrong during copy/paste or typing in, as YML looks for proper indentation. Is this the way to set the x-pack features working? (such as alerting - watcher configuration, security - user & roles setup).
You're not bothering anyone of us @maheshm, apologies if it felt this way.
You don't have to explicitly set any of the settings to true. These are true by default as the documentation you posted in the screenshot above also suggests. You don't have to go through them one by one and enable them. These are assumed true, unless explicitly set to false.
Does my answer cover this part of your question?
Okay. Thanks for clarifying.
Cheers,
Mahesh.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.