You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, RUM events sent through the Web View bridge (i.e. web views configured with WKUserContentController.trackDatadogEvents) don't include attributes defined via Global.rum.addAttribute. This is somewhere in between a bug report and a feature request but it'd be great if the iOS RUM attributes could be combined with the browser RUM attributes. Without this in place, Datadog appears to non-deterministically(!) nuke iOS attributes from app sessions because it looks to be using a heuristic (last/most frequent view?) to determine which set of view attributes it should apply to the session as a whole.
I'm currently getting around this with a hacky redefinition of window.DatadogEventBridge.send but I have a feeling an in-tree fix could be a lot cleaner, by merging the browser and iOS attributes in DefaultWebRUMEventConsumer.map(event:with:).
The text was updated successfully, but these errors were encountered:
At the moment, RUM events sent through the Web View bridge (i.e. web views configured with
WKUserContentController.trackDatadogEvents
) don't include attributes defined viaGlobal.rum.addAttribute
. This is somewhere in between a bug report and a feature request but it'd be great if the iOS RUM attributes could be combined with the browser RUM attributes. Without this in place, Datadog appears to non-deterministically(!) nuke iOS attributes from app sessions because it looks to be using a heuristic (last/most frequent view?) to determine which set of view attributes it should apply to the session as a whole.I'm currently getting around this with a hacky redefinition of
window.DatadogEventBridge.send
but I have a feeling an in-tree fix could be a lot cleaner, by merging the browser and iOS attributes inDefaultWebRUMEventConsumer.map(event:with:)
.The text was updated successfully, but these errors were encountered: