- Legacy APM Server Reference:
- Overview
- Installing APM Server
- Upgrading APM Server
- Setting up and running APM Server
- Configuring APM Server
- General configuration options
- Configure the output
- Parse data by using ingest node
- Specify SSL settings
- Load the Elasticsearch index template
- Configure logging
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Set up Real User Monitoring (RUM) support
- Use environment variables in the configuration
- Set up project paths
- Securing APM Server
- Event Types
- Real User Monitoring (RUM)
- Tune Data Ingestion
- Storage Management
- Intake API
- Exploring data in Elasticsearch
- Exported fields
- Troubleshooting
- Release notes
A newer version is available. For the latest information, see the
current release documentation.
Why is APM Server a separate component?edit
The APM Server is a separate component for the following reasons:
- It helps to keep the agents as light as possible and since the APM Server is a stateless separate component, it can be scaled independently.
- For Real User monitoring data is collected in browsers. APM Server prevents browsers from interacting directly with Elasticsearch (which poses a security risk), and controls the amount of data flowing into Elasticsearch.
- In cases where Elasticsearch becomes unresponsive, APM Server can buffer data temporarily without adding overhead to the agents.
- Acts as a middleware for source mapping for javascript in the browser.
- Provides a JSON API for agents to use thereby improving compatibility across different versions of agents and the Elastic Stack.
Was this helpful?
Thank you for your feedback.