Datadog

32 engineers on Hacker News describe using Datadog first-hand: 6 endorse it, 7 regret it, 6 are mixed.

48%trust
32first-hand users
32in production
endorse 6mixed 6regret 7uses, no opinion

“we get loads of value out of it since we leaned so heavily into it as a central platform.”

endorse · production · Hovertruck · 2026-02-20 · source ↗ · wrong label?

“We had a latency spike that all the usual polling tools missed — top, CloudWatch, Datadog, everything looked normal.”

regret · production · parth21shah · 2025-11-20 · source ↗ · wrong label?

“Datadog is really good at identifying anomalies, but the cost for logs is so high there's a non-trivial amount of savings”

mixed · production · blyry · 2025-11-07 · source ↗ · wrong label?

“i honestly don't miss datadog at all at this point.”

regret · production · drzaiusx11 · 2025-06-17 · source ↗ · wrong label?

“I don't think I'd ever let datadog slurp everything from AWS cloudwatch again. the amount of pure useless noise there far outweighs the value.”

regret · production · inhumantsar · 2025-01-25 · source ↗ · wrong label?

“after a few years of this the startup I worked for was paying Datadog more money per-month than the highest-paid salaries on the team.”

regret · production · 3 yr · talldayo · 2024-07-30 · source ↗ · wrong label?

“costs were more controllable, but you have to learn their billing world, which is in itself very painful.”

mixed · production · robertlagrant · 2024-06-17 · source ↗ · wrong label?

“Out of all commercial providers, Datadog is the worst one to show traces properly.”

regret · production · CSDude · 2023-01-27 · source ↗ · wrong label?

“DD has a lot going for it that I don't see in New Relic... DD has no incentive to add such a feature.”

mixed · production · hosh · 2023-01-27 · source ↗ · wrong label?

“All the free, open-source ones have absolutely nothing on Datadog and New Relic (which is what we use).”

endorse · production · icelancer · 2022-12-28 · source ↗ · wrong label?

“we use DD's JVM agent and we get lots of integrations for free (JVM metrics, tarcing for http calls, tracing for DB queries...)”

endorse · production · SubMachineGhost · 2022-12-27 · source ↗ · wrong label?

“I can already compare for example Datadog to our own dedicated Monitoring stack... despite it being 10x better than generic solution.”

regret · production · pojzon · 2022-06-10 · source ↗ · wrong label?

“dd was ridiculously expensive and resource hungry in kubernetes environment”

mixed · production · dilyevsky · 2021-05-04 · source ↗ · wrong label?

“I use this in prod; it's great. Expensive though.”

mixed · production · theptip · 2021-03-10 · source ↗ · wrong label?

“we switched over from one to another because NewRelic doesn't really support Rust and DD supports StatsD and there is no lock-in.”

endorse · production · cfabianski · 2020-06-16 · source ↗ · wrong label?

“We migrated to Datadog which charges based on cardinality so we actively avoid useful tags that have too much cardinality.”

mixed · production · sa46 · 2020-05-30 · source ↗ · wrong label?

“the cost of data collection is beginning to scale out of hand.”

regret · production · kairuiz · 2020-01-28 · source ↗ · wrong label?

“I've used Datadog in production for 3+ years (starting from a headcount of 10) and can honestly say they've been worth every penny.”

endorse · production · 3 yr · gamache · 2019-11-06 · source ↗ · wrong label?

“we use datadog and I generally find it excellent. Alerts to hipchat, pagerduty, etc, with AWS Cloudwatch integration.”

endorse · production · Rapzid · 2015-07-31 · source ↗ · wrong label?

“we migrated all of our observability from Datadog to Grafana/AMP because it's much much cheaper”

neutral · production · zaptheimpaler · 2026-02-05 · source ↗ · wrong label?

“all of ours logs to Datadog, Sentry, Snowflake, and more.”

neutral · production · dukeyukey · 2025-12-20 · source ↗ · wrong label?

“One such thing was interacting with Datadog which, unsurprisingly, doesn't provide OCaml SDK.”

neutral · production · xlii · 2024-12-03 · source ↗ · wrong label?

“we already had a GCP->Datadog log syncer for some other GCP infra logs, so re-using the GCP-based pipeline was the easiest way”

neutral · production · bhyolken · 2023-11-17 · source ↗ · wrong label?

“We just moved away from Datadog because their log storage pricing is too high for us.”

neutral · production · GeneralTspoon · 2021-02-01 · source ↗ · wrong label?

“at a prev job we switched _to_ ddlogs from sumologic because ddlogs was so much cheaper.”

neutral · production · dalyons · 2020-08-11 · source ↗ · wrong label?

“Teams here that use serverless have shifted to DataDog APM for this purpose.”

neutral · production · angerbot · 2019-12-09 · source ↗ · wrong label?

“We currently use Datadog, so we use their API for publishing events.”

neutral · production · sciurus · 2018-12-13 · source ↗ · wrong label?

“Monitoring with Datadog”

neutral · production · ksajadi · 2018-07-12 · source ↗ · wrong label?

“We've built automation around ... our monitoring (Datadog-based)”

neutral · production · chrissnell · 2016-10-13 · source ↗ · wrong label?

“Now that we expose the codecache size in Datadog, I may try plotting code size vs codecache size for a variety of our apps.”

neutral · production · billsmithaustin · 2016-09-15 · source ↗ · wrong label?

“It was the main dashboard before we moved to Datadog.”

neutral · production · stevesun21 · 2016-07-07 · source ↗ · wrong label?

“we use the datadog reporter & alert on time since last success.”

neutral · production · NightMKoder · 2015-10-17 · source ↗ · wrong label?