Cloudflare sits in front of an application: DNS, CDN caching, TLS, DDoS and bot protection, a web application firewall and edge compute with Workers. Sentry sits inside the application: it captures errors, stack traces, releases, performance traces and session replays so developers can fix what broke. They are rarely substitutes; choose by the blind spot, and run both when delivery and code failures each have an owner.12345678

  • Write down the incident you cannot explain today: traffic, latency and attacks at the edge, or exceptions and slow code in the app.
  • If you run code on Cloudflare Workers, confirm how errors from Workers reach Sentry before launch.
  • Decide which team owns edge rules and which owns application alerts, so each alert lands with someone who can act.
  • Re-check current plan limits for requests, events, traces and data retention on official documentation.