# Manually trigger sourcemap analysis for existing apm RUM errors

**URL:** <https://discuss.elastic.co/t/manually-trigger-sourcemap-analysis-for-existing-apm-rum-errors/226094>\
**Category:** APM\
**Tags:** rum\
**Created:** [April 1, 2020, 5:06pm UTC](https://discuss.elastic.co/t/manually-trigger-sourcemap-analysis-for-existing-apm-rum-errors/226094 "2020-04-01T17:06:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joren\_Inghelbrecht](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joren_inghelbrecht/32/45922_2.png) [@Joren\_Inghelbrecht](https://discuss.elastic.co/u/Joren_Inghelbrecht)\
**Post date:** [April 1, 2020, 5:06pm UTC](https://discuss.elastic.co/t/manually-trigger-sourcemap-analysis-for-existing-apm-rum-errors/226094/1 "2020-04-01T17:06:52Z")

</div>

I just uploaded a the sourcemaps of our Angular application to Kibana using curl by following this guide: [https://www.elastic.co/guide/en/apm/agent/rum-js/current/sourcemap.html](https://www.elastic.co/guide/en/apm/agent/rum-js/current/sourcemap.html).

It's working fine, my stacktraces in the error tab in APM couldn't be prettier, but I was wondering if I can trigger this pipeline/enrichment (is it a pipeline?) on older documents? I'm still seeing "error": "No Sourcemap available for ServiceName..." for errors that occurred before the upload.

We still have to automatically upload our sourcemaps when we deploy a new version of our application, but in the mean time I would like to be able to see the stacktrace if an error occurs.

---

<div class="post-metadata">

**Author:** ![axw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/axw/32/28197_2.png) [@axw](https://discuss.elastic.co/u/axw)\
**Post date:** [April 2, 2020, 2:31am UTC](https://discuss.elastic.co/t/manually-trigger-sourcemap-analysis-for-existing-apm-rum-errors/226094/2 "2020-04-02T02:31:23Z")

</div>

@Joren_Inghelbrecht welcome to the forum!

I think you could probably do this using the Elasticsearch [update\_by\_query](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-update-by-query.html) API with an ingest node pipeline, using the [Enrich processor](https://www.elastic.co/guide/en/elasticsearch/reference/current/enrich-processor.html), but it's not something we have support for out of the box.

There's [https://github.com/elastic/apm-server/issues/2724](https://github.com/elastic/apm-server/issues/2724), I recommend subscribing if you would like to be updated on this.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 22, 2020, 10:31pm UTC](https://discuss.elastic.co/t/manually-trigger-sourcemap-analysis-for-existing-apm-rum-errors/226094/3 "2020-04-22T22:31:26Z")

</div>

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.