- Legacy APM Server Reference:
- Overview
- Get started
- Set up
- How-to guides
- Configure
- Secure
- Monitor
- API
- Explore data in Elasticsearch
- Exported fields
- General APM fields
- APM Error fields
- APM Profile fields
- APM Sourcemap fields
- APM Span fields
- APM Transaction fields
- APM Transaction Metrics fields
- APM Transaction Metrics fields
- Beat fields
- Cloud provider metadata fields
- Docker fields
- ECS fields
- Host fields
- Kubernetes fields
- Process fields
- APM System Metrics fields
- Troubleshoot
- Upgrade
- Release notes
- APM Server version 7.8
- APM Server version 7.7
- 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
A newer version is available. For the latest information, see the
current release documentation.
Update existing dataedit
You might want to update documents that are already indexed. For example, if you your service name was set incorrectly.
To do 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.
On this page
Was this helpful?
Thank you for your feedback.