Correlate RUM traces with OpenTelemetry backends

kloudmate's rum lets you connect requests from your web apps to their related backend traces this integration provides a unified view of both your frontend and backend data and helps to identify issues throughout your stack and gain insight into your users' experiences the rum sdk by default adds context propagation headers (w3c) to fetch and xhr requests made to the same origin if you want to propagate these headers to a different origin, it can be configured at initialization for example, if you want to propagate trace context headers to https //api example com , the rum sdk would be initialized as shown below kloudmaterum init({ endpoint 'https //otel kloudmate dev 4318', rumaccesstoken '(your public api key>', applicationname 'my app', version '1', deploymentenvironment 'prod', sessionrecorder { enabled true, } instrumentations { fetch { propagatetraceheadercorsurls \[new regexp('https //api example com ')] }, xhr { propagatetraceheadercorsurls \[new regexp('https //api example com ')] } } }); this will add context propagation headers to backend requests the backend can then generate its spans using this context you can find examples of context extraction on the backend here https //opentelemetry io/docs/languages/js/propagation/#generic example sample integration 1\ once the rum and backend are integrated you can view the corresponding backend trace of a frontend request 2\ you can identify the same in apm traces related resources what is real user monitoring (rum)? https //docs kloudmate com/what is real user monitoring rum kloudmate rum interface https //docs kloudmate com/rum interface