- Legacy APM Server Reference:
- Overview
- Getting Started With APM Server
- Setting up APM Server
- Upgrading APM Server
- Configuring APM Server
- General configuration options
- Configure the output
- Parse data using ingest node pipelines
- SSL/TLS settings
- Load the Elasticsearch index template
- Index lifecycle management (ILM)
- Configure logging
- Configure the Kibana endpoint
- Set up Real User Monitoring (RUM) support
- Jaeger integration
- Use environment variables in the configuration
- Configure project paths
- Securing APM Server
- Monitoring APM Server
- Real User Monitoring (RUM)
- Tune Data Ingestion
- Storage Management
- API
- Exploring data in Elasticsearch
- Exported fields
- Troubleshooting
- Release notes
- APM Server version 7.6
- APM Server version 7.5
- APM Server version 7.4
- APM Server version 7.3
- APM Server version 7.2
- APM Server version 7.1
- APM Server version 7.0
- APM Server version 6.8
- APM Server version 6.7
- APM Server version 6.6
- APM Server version 6.5
- APM Server version 6.4
- APM Server version 6.3
- APM Server version 6.2
- APM Server version 6.1
Directory layoutedit
The directory layout of an installation is as follows:
Type | Description | Default Location | Config Option |
---|---|---|---|
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. |
|
|
You can change these settings by using CLI flags or setting path options in the configuration file.
Default pathsedit
APM Server uses the following default paths unless you explicitly change them.
deb and rpmedit
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.
dockeredit
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. |
|
zip, tar.gz, or tgzedit
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
brewedit
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. |
|