just figured out a way to bridge the gap btwn my existing sentry setup and datadog for better observability. if you are already using sentry in your route handlers, you do not need to overhaul everything. i just built a small fetch-based logger utility that handles both destinations at once. it basically intercepts the log event and pushes it to the datadog endpoint via a standard fetch request. it works surprisingly well without adding much latency to the edge functions.
>the trick is keeping the payload lightweight so you don't blow up your execution limitsi was worried about double logging or breaking the existing sentry traces, but the logic is pretty isolated. you just wrap your error handling in that custom utility class. it makes debugging much easier when you have the full trace in datadog instead of just a cryptic alert.
it took me three hours to debug a single typo in the headers so hopefully you guys save some time. has anyone else tried moving their entire monitoring stack away from sentry yet, or is the dual setup the new standard? __definitely worth checking out if you need more granular metrics
full read:
https://webflowmarketingmain.com/blog/error-tracking-webflow-cloud-sentry-datadog