We should always create a test environment to test changes before applying them to the production environment, so that, if any change breaks the Elastic Stack setup, we can stop it at the testing level without affecting the production environment. Also, we can use it as a playground to test trivial or nontrivial things, and once it is successful, we can easily replicate it on the production setup.

In Elasticsearch Stack, we have different configuration options to tweak and change some features of the setup and, sometimes, can also break the running application, so it is very necessary to test changes on the test environment first before applying them on the production setup once it is successful on the test environment.

Apart from configuration settings, we have APIs in Elasticsearch, with which we can play around, and once what is tested, we can then just do the same on production setup as well. There are so many things to consider, such as visualization creation...