Dynatrace RUM Configuration Question for Micro‑Frontend Setup

[riship1699]

I have a question about how to best configure Dynatrace RUM for our micro-frontend architecture.

Our shell application loads the DynatraceRUM cookie globally through a shared footer, and the individual MFEs are deployed independently and mounted into the shared shell.

Given this setup, should each MFE be configured as its own Web Application in Dynatrace, or is it better to keep everything under a single Web Application? I want to follow best practices before making any changes, especially since each MFE is owned by a different team in our org.

[t_pawlak]

Hi,
IMO single Web Application works best. 

From the end-user and browser perspective, this is still one continuous application and one user journey.

All MFEs share the same session cookie, so splitting into multiple web apps often breaks session continuity and makes analysis harder. You keep full end-to-end visibility (navigation, errors, performance, conversions) across MFEs.
Instead of creating multiple web apps,

You can add a custom session property, e.g. mfeName, set by each MFE (via route, JS variable, or some CSS selector)
You can also standardize user action naming to include the MFE name.