- Observability: other versions:
- What is Elastic Observability?
- What’s new in 8.14
- Get started
- Observability AI Assistant
- Application performance monitoring (APM)
- Self manage APM Server
- Data Model
- Features
- Navigate the APM UI
- Perform common tasks in the APM UI
- Configure APM agents with central config
- Control access to APM data
- Create an alert
- Create and upload source maps (RUM)
- Create custom links
- Filter data
- Find transaction latency and failure correlations
- Identify deployment details for APM agents
- Integrate with machine learning
- Explore mobile sessions with Discover
- Observe Lambda functions
- Query your data
- Storage Explorer
- Track deployments with annotations
- OpenTelemetry integration
- Manage storage
- Configure
- Advanced setup
- Secure communication
- Monitor
- APM Server API
- APM UI API
- Troubleshoot
- Upgrade
- Release notes
- Known issues
- Log monitoring
- Infrastructure monitoring
- AWS monitoring
- Azure monitoring
- Synthetic monitoring
- Get started
- Scripting browser monitors
- Configure lightweight monitors
- Manage monitors
- Work with params and secrets
- Analyze monitor data
- Monitor resources on private networks
- Use the CLI
- Configure projects
- Configure Synthetics settings
- Grant users access to secured resources
- Manage data retention
- Use Synthetics with traffic filters
- Migrate from the Elastic Synthetics integration
- Scale and architect a deployment
- Synthetics support matrix
- Synthetics Encryption and Security
- Troubleshooting
- Uptime monitoring
- Real user monitoring
- Universal Profiling
- Alerting
- Service-level objectives (SLOs)
- Cases
- CI/CD observability
- Troubleshooting
- Fields reference
- Tutorials
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.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.
-
/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.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 /opt. When installing Elastic Agent with the ./elastic-agent install
command, use the --base-path CLI option to specify the custom base 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.ndjson - Log files for Elastic Agent and Beats shippers [1]
You can install Elastic Agent in a custom base path other than C:\Program Files. When installing Elastic Agent with the .\elastic-agent.exe install
command, use the --base-path CLI option to specify the custom base 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.ndjson - Log files for Elastic Agent and Beats shippers [1]
-
/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.ndjson - Log files for Elastic Agent and Beats shippers [1]
-
/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.
YYYYMMDD) and optional number: elastic-agent-YYYYMMDD.ndjson, elastic-agent-YYYYMMDD-1.ndjson, and so on as new files are created during rotation.
On this page