- 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
Configure project paths
editConfigure project paths
edit
This documentation is only relevant for APM Server binary users. Fleet-managed paths are defined in Installation layout.
The path section of the apm-server.yml config file contains configuration
options that define where APM Server looks for its files. For example, APM Server
looks for the Elasticsearch template file in the configuration path and writes
log files in the logs path.
Please see the Installation layout section for more details.
Here is an example configuration:
path.home: /usr/share/beat path.config: /etc/beat path.data: /var/lib/beat path.logs: /var/log/
Note that it is possible to override these options by using command line flags.
Configuration options
editYou can specify the following options in the path section of the apm-server.yml config file:
home
editThe home path for the APM Server installation. This is the default base path for all other path settings and for miscellaneous files that come with the distribution (for example, the sample dashboards). If not set by a CLI flag or in the configuration file, the default for the home path is the location of the APM Server binary.
Example:
path.home: /usr/share/beats
config
editThe configuration path for the APM Server installation. This is the default base path for configuration files, including the main YAML configuration file and the Elasticsearch template file. If not set by a CLI flag or in the configuration file, the default for the configuration path is the home path.
Example:
path.config: /usr/share/beats/config
data
editThe data path for the APM Server installation. This is the default base path for all
the files in which APM Server needs to store its data. If not set by a CLI
flag or in the configuration file, the default for the data path is a data
subdirectory inside the home path.
Example:
path.data: /var/lib/beats
When running multiple APM Server instances on the same host, make sure they
each have a distinct path.data value.
logs
editThe logs path for a APM Server installation. This is the default location for APM Server’s
log files. If not set by a CLI flag or in the configuration file, the default
for the logs path is a logs subdirectory inside the home path.
Example:
path.logs: /var/log/beats
system.hostfs
editSpecifies the mount point of the host’s file system for use in monitoring a host.
This can either be set in the config, or with the --system.hostfs CLI flag. This is used for cgroup self-monitoring.
Example:
system.hostfs: /mount/rootfs