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
Copy file name to clipboardExpand all lines: content/en/real_user_monitoring/connect_rum_and_traces/_index.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -138,6 +138,8 @@ Datadog uses the distributed tracing protocol and sets up the following HTTP hea
138
138
`x-datadog-sampled: 1`
139
139
: Generated from the Real User Monitoring SDK. Indicates this request is selected for sampling.
140
140
141
+
**Note**: These HTTP headers are not CORS-safelisted, so you need to [configure Access-Control-Allow-Headers][17] on your server. The server must also accept [preflight requests][18] (OPTIONS requests).
142
+
141
143
## How are APM quotas affected?
142
144
143
145
The `x-datadog-origin: rum` header specifies to the APM backend that the traces are generated from Real User Monitoring. The generated traces consequently do not impact Indexed Span counts.
@@ -164,3 +166,5 @@ These traces are retained [just like your classical APM traces][16].
0 commit comments