Skip to content

MFE Configuration. Service/Version used for sourcemaps resolution. #4922

Description

@Asiratlan

What are you trying to achieve and what is your issue? Please describe.

We use multiple micro-frontend with a "portal" merge everything together using single-spa. For the sake of this explanation, let's say that portal serve a single service.

We initiated DatadogRum following the single-spa recipe found in the documentation and uploaded our sourcemaps properly on datadog using datadog-ci.

In Datadog, my logs are all marked with the "Unminification failed" box. They have two sets of version/service written on them. In the Tags we have the values from the portal service set in the javascript init's function parameter and in the log itself we can find another set that contains our single service's name and version which is set by the beforeSend method added into our init.

When I click on the "RUM Debug Symbols page" it opens filtered using the log's service (so the right service), but it also filter using the tag's version which is the version of our portal and not our service.

Both parts has it's own version number which is the following [application_version]-[pipeline_number]. So our Portal and Service can never have the same version. I did some test by enforcing the same version in both tags and logs and it was resolving properly. Any idea how to either change de tag version or force sourcemaps resolution to use the logs' version as it is already using the log's service?

Describe the solution you'd like
If my portal's version is 1.2.3-12345 and my service is 1.2.3-23456, I want my sourcemaps for logs occuring in the service to be resolved using the service: service and version: 1.2.3-23456.

Describe alternatives you've considered
Tried multiple MFE Recipe from the doc, even tried the automatic registration using the webpack plugin. The problem is still there.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions