Sentry support in Module Federation

[geralt-debugs]

Feature request

What is the expected behavior?
Sentry intercepts errors at a global level. That error is tagged with a release version and the sourcemaps related to that release is used for displaying the real source.

But now since an error source can be any part of the code and that part can have different release versions(since they are deployed separately), how I can communicate the release version to sentry so that my error can get successfully decoded by the source map. Basically, the core problem is, I want to get the source of the error so that I can successfully identify the name of the federated app from where the error was thrown.

How should this be implemented in your opinion?
In my opinion, if somehow webpack can tag the error with the federated app somehow, it might be possible to get more details about that error

Are you willing to work on this yourself?
I am willing to contribute if there are any changes required here.

Issue in sentry's repository getsentry/sentry-javascript#3268

[sokra]

Afaik it's not technically possible to tag errors thrown by the source. You need to get that from the stack trace.

[geralt-debugs]

That's what I thought. Traces are mangled in production mode. Is there any federation plugin configuration through which I can get the source application from where the error originated(through stack traces itself or any other way)?

[ScriptedAlchemy]

You'd need to tag it somehow or wrap some kind of boundary which labels the remote and labels the current host

[ScriptedAlchemy]

DefinePlugin(CURRENT_HOST) would work in defining "who am i"

[geralt-debugs]

@ScriptedAlchemy that would work for synchronous errors, but async errors would get lost

[ScriptedAlchemy]

I've published a post detailing how to handle distributed logging. We have implemented it with sentry hub and custom use of the low level apis