Skip to content

Commit de3ca4d

Browse files
authored
Merge pull request DataDog#10985 from DataDog/hdelaby/apm-rum-cors
[rum] add cors warning for apm<>rum link
2 parents 305e617 + 05eb4c2 commit de3ca4d

File tree

1 file changed

+4
-0
lines changed
  • content/en/real_user_monitoring/connect_rum_and_traces

1 file changed

+4
-0
lines changed

content/en/real_user_monitoring/connect_rum_and_traces/_index.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -138,6 +138,8 @@ Datadog uses the distributed tracing protocol and sets up the following HTTP hea
138138
`x-datadog-sampled: 1`
139139
: Generated from the Real User Monitoring SDK. Indicates this request is selected for sampling.
140140

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+
141143
## How are APM quotas affected?
142144

143145
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].
164166
[14]: /tracing/setup_overview/setup/dotnet-core/
165167
[15]: https://github.com/DataDog/dd-trace-dotnet/releases/tag/v1.18.2
166168
[16]: /tracing/trace_retention_and_ingestion/
169+
[17]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Headers
170+
[18]: https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request

0 commit comments

Comments
 (0)