Why People Are Still Using Datadog in 2025: Real Conversations and Hard Truths from Engineering Teams

## The Familiar Devil Everyone Knows “Yeah, Datadog’s expensive, but it’s the devil we know.” It’s the kind of thing you hear quietly passed between engineers after a particularly expensive billing cycle—or after yet another migration discussion gets shelved. Despite all the gripes, Datadog continues to be the default monitoring choice for modern engineering teams. And it’s not because it’s flawless. It’s because when systems crash and dashboards light up like Christmas trees, Datadog is the one tool everyone can rely on to make sense of the chaos. … ## The Promise and Pain of Alternatives “We tried moving to Prometheus, and… the observability just dropped. We lost visibility.” This wasn’t an isolated complaint. Prometheus is powerful, yes—but it’s also fragmented. You stitch together monitoring with Grafana dashboards, node exporters, alert managers, and suddenly you’re not monitoring your app—you’re maintaining the observability stack. Engineers love Prometheus in theory. In practice? They’re exhausted. One founder put it simply: “Prometheus is like LEGO. Datadog is like IKEA. I know what I’m getting, and it mostly just works.” … ## Hacking Around the Edges “For logs, honestly, we still export to S3 and run our own analysis. Datadog’s pricing just doesn’t scale.” Let’s talk about cost. Because that’s where the love fades fast. Logs in Datadog can get expensive—fast. Teams have been caught off-guard by ballooning ingestion costs. The reaction? Workarounds. Custom exporters. DIY S3 buckets. Keeping Datadog lean and using cheaper tools for bulk storage. … ## Why It’s Still Winning “It’s not about laziness—it’s about risk. Nobody wants to wake up at 3 am wondering if the new monitoring tool missed something critical.” This was the most recurring theme across every conversation: risk. In theory, there are better tools. In practice, switching tools introduces risk. A missing alert. A broken dashboard. A blind spot in a fire. When the margin for error is zero, most engineers would rather deal with Datadog’s billing than gamble on missing a P1 alert. That trust, however reluctant, is what keeps Datadog at the center of most monitoring stacks. ## The Real Reason Teams Don’t Leave There are cheaper tools. There are faster tools. There are prettier tools. But the reason engineers stay with Datadog comes down to three things: **Everyone knows how to use it.** **It covers just enough to be dangerous.** **And it’s already there.** … ## TL;DR **Datadog continues to dominate not out of love, but necessity.** **Migration is expensive—not in money, but in time, trust, and operational risk.** **Engineers find creative ways to make Datadog work—like exporting logs to S3.** **It’s the one monitoring tool everyone can agree on when things go wrong.** **Until a risk-free alternative appears, Datadog stays put.**