feature request: sourcemap support

[aroman]

many javascript environments are written using source code files that don't map 1:1 with the codebase used at runtime, due to typescript and/or minification

this makes viewing logs not such a great experience — it would be awesome if betterstack supported JS sourcemaps, particularly for environments like cloudflare workers where all your code gets bundled up into a single giant JS file

[curusarn]

Hi @aroman,

Thanks for reaching out.
This sounds like a useful feature. I'm adding it to our internal ticketing system.
I'll make sure to keep you updated.

Also we are always grateful for contributions.
This looks like a library we could use:
https://www.npmjs.com/package/source-map#consuming-a-source-map

Thanks again for raising this. 🙏

[aroman]

Hi @aroman,

Thanks for reaching out. This sounds like a useful feature. I'm adding it to our internal ticketing system. I'll make sure to keep you updated.

Also we are always grateful for contributions. This looks like a library we could use: https://www.npmjs.com/package/source-map#consuming-a-source-map

Thanks again for raising this. 🙏

@curusarn that would be great. it's worth pointing out — i think this feature would require support from the logtail API/backend team. actually uploading the sourcemap via logtail-js should be pretty trivial as you pointed out, but those sourcemaps would actually need to be uploaded somewhere presumably stored by logtail and used to display in e.g. the logtail UI, or possibly via API access to logs.

Consider how Sentry does sourcemaps for logs (for JS in the browser and the backend): https://docs.sentry.io/product/cli/releases.

z