<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Datadog on CSP Guide</title>
    <link>https://csp-guide.com/tags/datadog/</link>
    <description>Recent content in Datadog on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 13 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/datadog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP for Datadog RUM and Synthetics: A Real-World Fix</title>
      <link>https://csp-guide.com/posts/csp-for-datadog-rum-and-synthetics/</link>
      <pubDate>Mon, 13 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-datadog-rum-and-synthetics/</guid>
      
      <description>&lt;p&gt;I’ve seen this pattern a lot: a team adds Datadog RUM, turns on Synthetic Monitoring, and suddenly the browser console lights up with CSP violations. The app still loads, mostly. Dashboards stay empty, session replay breaks, synthetic tests look flaky, and everyone starts guessing which domain needs to be whitelisted.&lt;/p&gt;
&lt;p&gt;Guessing is how CSP turns into a junk drawer.&lt;/p&gt;
&lt;p&gt;Here’s a cleaner way to do it, based on a realistic setup and the exact kinds of changes teams end up making in production.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
