Installation layout
editInstallation layout
editView the installation layout and default paths for both Fleet-managed APM Server and the APM Server binary.
Fleet-managed
editElastic Agent files are installed in the following locations. You cannot override these installation paths because they are required for upgrades.
-
/Library/Elastic/Agent/*
- Elastic Agent program files
-
/Library/Elastic/Agent/elastic-agent.yml
- Main Elastic Agent configuration
-
/Library/Elastic/Agent/fleet.enc
- Main Elastic Agent Fleet encrypted configuration
-
/Library/Elastic/Agent/data/elastic-agent-*/logs/elastic-agent-json.log
- Log files for Elastic Agent[1]
-
/Library/Elastic/Agent/data/elastic-agent-*/logs/default/*-json.log
- Log files for Beats shippers[1]
-
/usr/bin/elastic-agent
- Shell wrapper installed into PATH
-
/opt/Elastic/Agent/*
- Elastic Agent program files
-
/opt/Elastic/Agent/elastic-agent.yml
- Main Elastic Agent configuration
-
/opt/Elastic/Agent/fleet.enc
- Main Elastic Agent Fleet encrypted configuration
-
/opt/Elastic/Agent/data/elastic-agent-*/logs/elastic-agent-json.log
- Log files for Elastic Agent[1]
-
/opt/Elastic/Agent/data/elastic-agent-*/logs/default/*-json.log
- Log files for Beats shippers
-
/usr/bin/elastic-agent
- Shell wrapper installed into PATH
-
C:\Program Files\Elastic\Agent*
- Elastic Agent program files
-
C:\Program Files\Elastic\Agent\elastic-agent.yml
- Main Elastic Agent configuration
-
C:\Program Files\Elastic\Agent\fleet.enc
- Main Elastic Agent Fleet encrypted configuration
-
C:\Program Files\Elastic\Agent\data\elastic-agent-*\logs\elastic-agent-json.log
- Log files for Elastic Agent[1]
-
C:\Program Files\Elastic\Agent\data\elastic-agent-*\logs\default\*-json.log*
- Log files for Beats shippers
-
/usr/share/elastic-agent/*
- Elastic Agent program files
-
/etc/elastic-agent/elastic-agent.yml
- Main Elastic Agent configuration
-
/etc/elastic-agent/fleet.enc
- Main Elastic Agent Fleet encrypted configuration
-
/var/lib/elastic-agent/data/elastic-agent-*/logs/elastic-agent-json.log
- Log files for Elastic Agent[1]
-
/var/lib/elastic-agent/data/elastic-agent-*/logs/default/*-json.log*
- Log files for Beats shippers
-
/usr/bin/elastic-agent
- Shell wrapper installed into PATH
-
/usr/share/elastic-agent/*
- Elastic Agent program files
-
/etc/elastic-agent/elastic-agent.yml
- Main Elastic Agent configuration
-
/etc/elastic-agent/fleet.enc
- Main Elastic Agent Fleet encrypted configuration
-
/var/lib/elastic-agent/data/elastic-agent-*/logs/elastic-agent-json.log
- Log files for Elastic Agent[1]
-
/var/lib/elastic-agent/data/elastic-agent-*/logs/default/*-json.log*
- Log files for Beats shippers
-
/usr/bin/elastic-agent
- Shell wrapper installed into PATH
APM Server binary
editAPM Server uses the following default paths unless you explicitly change them.
Type | Description | Location |
---|---|---|
home |
Home of the APM Server installation. |
|
bin |
The location for the binary files. |
|
config |
The location for configuration files. |
|
data |
The location for persistent data files. |
|
logs |
The location for the logs created by APM Server. |
|
For the ZIP, tar.gz, or TGZ distributions, these paths are based on the location of the extracted binary file. This means that if you start APM Server with the following simple command, all paths are set correctly:
./apm-server
Type | Description | Location |
---|---|---|
home |
Home of the APM Server installation. |
|
bin |
The location for the binary files. |
|
config |
The location for configuration files. |
|
data |
The location for persistent data files. |
|
logs |
The location for the logs created by APM Server. |
|
Type | Description | Location |
---|---|---|
home |
Home of the APM Server installation. |
|
bin |
The location for the binary files. |
|
config |
The location for configuration files. |
|
data |
The location for persistent data files. |
|
logs |
The location for the logs created by APM Server. |
|
For the deb and rpm distributions, these paths are set in the init script or in
the systemd unit file. Make sure that you start the APM Server service by using
the preferred operating system method (init scripts or systemctl
).
Otherwise the paths might be set incorrectly.