📚 Unlock the full potential of Digital Experience Monitoring with the new RUM experience

Platform Real User Monitoring
, , ,
41

Hello @AurelienGravier ! Please create a thread in the future inside the community group.

As of now, you can influence the resulting page names and view names via the eventModifier API.

You’d need to modify the page.detected_name

Which then results in a change of the page.name on ingest.

paul_kapeller_0-1762510947393.png
paul_kapeller_0-1762510947393.png1054×508 43.9 KB

Via an OpenPipeline processing step, you can also enrich your own field with the page name you’d like to have. However, direct modification of these fields is not possible on ingest yet, but it’s planned.

Hope this helps!

42

HI

Since the RUM data would be in Grail, will the useractions, usersessions be “linked” to the span data that is stored for services ?

Thank you

43

Linking frontend to backend data basically follows the Otel-standards and the context is enriched on user event level as well as spans. A request includes a trace-id which is stored on spans as well. You can - soon after our GA  in January e.g. go to the trace

- from a user event within the user session in the Users & Sessions app

- a request error in Error Inspector

- or a waterfall view in Experience Vitals

Also from the span/trace-view users can go to the user event triggering it,

- on DQL level

- in future within the Distributed Tracing app.

44

Hi @paul_kapeller,

Do you know if security context can be applied to RUM data in Grail already? I can see a product idea about that.

Best regards

45

Thanks for adding the comment - I have replied to the product idea.