- 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 using ingest node pipelines
- 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
- Monitoring APM Server
- 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.
Update existing dataedit
You might want to update documents already indexed, for example if you your service name was set incorrectly.
For this, you can use the Update By Query API.
Rename a serviceedit
To rename a service send the following request:
POST /apm-*/_update_by_query { "query": { "term": { "context.service.name": { "value": "old-service-name" } } }, "script": { "source": "ctx._source.context.service.name = 'new-service-name'", "lang": "painless" } }
Remember to also change the service name in the APM agent configuration accordingly.
On this page
Was this helpful?
Thank you for your feedback.