- Legacy APM Server Reference:
- Overview
- Getting Started With APM Server
- Setting up APM Server
- Upgrading APM Server
- Configuring APM Server
- General configuration options
- Configure the output
- Parse data using ingest node pipelines
- SSL/TLS settings
- Load the Elasticsearch index template
- Index lifecycle management (ILM)
- Configure logging
- Set up Real User Monitoring (RUM) support
- Use environment variables in the configuration
- Configure 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.
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
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
Was this helpful?
Thank you for your feedback.