Installation layout

edit

View the installation layout and default paths for both Fleet-managed APM Server and the APM Server binary.

Fleet-managed

edit

Elastic 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.ndjson
Log files for Elastic Agent and Beats shippers [1]
/usr/bin/elastic-agent
Shell wrapper installed into PATH

You can install Elastic Agent in a custom base path other than /Library. When installing Elastic Agent with the ./elastic-agent install command, use the --base-path CLI option to specify the custom base path.

APM Server binary

edit

APM Server uses the following default paths unless you explicitly change them.

Type Description Location

home

Home of the APM Server installation.

/usr/share/apm-server

bin

The location for the binary files.

/usr/share/apm-server

config

The location for configuration files.

/usr/share/apm-server

data

The location for persistent data files.

/usr/share/apm-server/data

logs

The location for the logs created by APM Server.

/usr/share/apm-server/logs

[1] Logs file names end with a date (YYYYMMDD) and optional number: elastic-agent-YYYYMMDD.ndjson, elastic-agent-YYYYMMDD-1.ndjson, and so on as new files are created during rotation.