Azure-docs: Application Insights source map with Azure blob only uses root folder

[thoo1]

According to this: https://docs.microsoft.com/en-us/azure/azure-monitor/app/source-map-support#push-your-source-maps-to-your-blob-container it says we should not add sourcemaps in a subfolder to the storage account but put them in the root folder

I was wondering if it is on the roadmap to support atleast, telling the application insights UI, which folder in blob to look for the sourcemaps

The scenario is that our frontend application has many versions, all pushing to the same application insights instance, and pushing all sourcemaps into subfolders tagged by their version number into blob. Thus we need subfolders since we have different sourcemaps for each version of our app

Thank you, let me know if you need more clarification

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 0c820ae7-4107-902c-7458-a7cfe17e6bc1
• Version Independent ID: 631e0cbe-d72e-76bb-cb6f-05b42490f03b
• Content: Source map support for JavaScript applications - Azure Monitor Application Insights - Azure Monitor
• Content Source: articles/azure-monitor/app/source-map-support.md
• Service: azure-monitor
• Sub-service: application-insights
• GitHub Login: @markwolff
• Microsoft Alias: marwolff

[BhargaviAnnadevara-MSFT]

@thoo1 Thanks for the question! We're investigating this and will get back to you shortly.

[markwolff]

Hi @thoo1 uploading source maps to subfolders as you've described should work as expected. The documentation reflects the original state of the feature, which has since been updated to support scenarios exactly like yours. e.g. you upload a folder structure like this sourcemaps/1.2.3/foo/bar.js.map and your webpage serves bar.js via 1.2.3/foo/bar.js, then we will search for the following files and unminify with whichever one exists.

sourcemaps/1.2.3/foo/bar.js.map
sourcemaps/foo/bar.js.map
sourcemaps/bar.js.map

I'll update the documentation to match the true behavior -- thanks for the report!

[BhargaviAnnadevara-MSFT]

@markwolff Thanks for the inputs and updates.

@thoo1 Thanks for the feedback. I have submitted a PR to fix the issue, the change is merged internally and will go-live in the public docs shortly.