Changing the location of Elasticsearch index data - Online help | EventLog Analyzer

Changing the location of Elasticsearch index data

Follow the steps below to move the log indices to a different location:
  1. Stop the EventLog Analyzer service.
  2. Open the command prompt with admin privileges.
  3. Navigate to <dir>:\ManageEngine\elasticsearch\ES\bin and execute stopES.bat.
  4. Make a backup of the <dir>:\ManageEngine\elasticsearch\ES\config\elasticsearch.yml file.
  5. In the command prompt, navigate to <dir>:\ManageEngine\elasticsearch\ES\config and execute write elasticsearch.yml.
  6. Update the path.data and path.repo parameters with the new location, and save the file.
  7. Start EventLog Analyzer to complete the process. 
Changing location of index (ES) data

Note: For Linux local storage, use the following format:
  1. path.data : ["/opt/ManageEngine/EventLog Analyzer/ES/data"]
  2. path.repo : ["/opt/ManageEngine/EventLog Analyzer/ES/repo"

                  New to ADManager Plus?

                    New to ADSelfService Plus?

                      • Related Articles

                      • No data from Syslog devices

                        No data from Syslog devices Ensure that the Syslog device is configured to forward the logs to EventLog Analyzer Server. Click here to know more about Syslog configuration in the respective devices. In both Hardware and Software Firewall, ensure that ...
                      • What to do if the EventLog Analyzer failed to update the IP's geolocation data due to network issue?

                        This occurs when there is no internet connection on the EventLog Analyzer server or if the creator server is unreachable. Domains/sites to be whitelisted: https://creator.zoho.com https://creatorexport.zoho.com The geolocation feature is used by ...
                      • DAE service failure during startup

                        Open the <dir>:\ManageEngine\EventLog Analyzer\logs\wrapper.log file. Search for DAEService status in the wrapper file. If it hasn't been created, look for the serverout_yyyy-mm-dd.txt file from the same day in the logs folder. Check whether the ...
                      • Efficient Solutions for Disk Space Management

                        Please gather the below details to narrow down the root cause of the issue: Build number: If the EventLog Analyzer GUI is accessible, log onto the GUI, click on ? at the right-top corner, and check the build number. If the EventLog Analyzer GUI is ...
                      • Growth in CachedRecord files

                        Growth in CachedRecord files generally occurs due to high hardware utilization while processing these files. To resolve this issue, begin by verifying whether the prerequisites and hardware requirements are met. Check the total number of configured ...