- 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
- Manual index lifecycle management
- 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
- APM Server version 6.8
- APM Server version 6.8.23
- APM Server version 6.8.22
- APM Server version 6.8.21
- APM Server version 6.8.20
- APM Server version 6.8.19
- APM Server version 6.8.18
- APM Server version 6.8.17
- APM Server version 6.8.16
- APM Server version 6.8.15
- APM Server version 6.8.14
- APM Server version 6.8.13
- APM Server version 6.8.12
- APM Server version 6.8.11
- APM Server version 6.8.10
- APM Server version 6.8.9
- APM Server version 6.8.8
- APM Server version 6.8.7
- APM Server version 6.8.6
- APM Server version 6.8.5
- APM Server version 6.8.4
- APM Server version 6.8.3
- APM Server version 6.8.2
- APM Server version 6.8.1
- APM Server version 6.8.0
- 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
- APM Server version 6.8
NOTE: You are looking at documentation for an older release. For the latest information, see the current release documentation.
Sourcemap Upload APIedit
You must enable RUM support in the APM Server for this endpoint to work.
The APM Server exposes an API endpoint to upload source maps for real user monitoring (RUM).
Upload endpointedit
Send a HTTP POST request with the Content-Type header set to multipart/form-data to the source map endpoint:
http(s)://{hostname}:{port}/assets/v1/sourcemaps
The URL for uploading sourcemaps was previously /v1/rum/sourcemaps. It was deprecated in v6.5,
and will be removed in v7.0 in favor of /assets/v1/sourcemaps.
Request Fieldsedit
The request must include some fields needed to identify source map correctly later on:
-
service_name -
service_version -
bundle_filepath: needs to be the absolute path of the final bundle as it is used in the web application
The source map must follow the
Source map revision 3 proposal spec and be attached as a file upload.
You can configure a secret token to upload sourcemaps.
Exampleedit
Example source map request including an optional secret token "mysecret":
curl -X POST http://127.0.0.1:8200/assets/v1/sourcemaps \ -H "Authorization: Bearer mysecret" \ -F service_name="test-service" \ -F service_version="1.0" \ -F bundle_filepath="http://localhost/static/js/bundle.js" \ -F sourcemap=@bundle.js.map
On this page