Datadog Problems & Issues
Real user-reported problems, complaints, and limitations for Datadog. Based on analysis of 14 signals.
Issues by Category
Bills can be 3-12x higher than initial estimates
Pricing data from 47 companies shows a consistent pattern where initial estimates miss by 3-12x. One VP of Engineering budgeted $12,000/month but received an actual invoice of $147,000. The multi-dimensional, usage-based model makes it nearly impossible to predict costs accurately. Teams regularly experience 'bill shock' when the invoice arrives.
Custom metrics pricing can explode costs without warning
The billing model is complex, and you have to be extremely careful with custom metrics and log indexing, or the cost will explode. Custom metrics are charged per metric per host, and enabling features like APM or custom instrumentation can quickly multiply your bill. Users report turning on 'all the things' and getting massive surprise bills at the end of the month.
Usage-based billing escalates costs as infrastructure scales
The per-host pricing model ($15-$27/host for Infrastructure, $31-$40/host for APM) quickly adds up as your infrastructure scales. Adding containers, serverless functions, or microservices multiplies costs. Organizations that started small find Datadog becoming prohibitively expensive as they scale. Costs require constant attention and strategic planning to control.
Sales and billing team accused of questionable tactics
Trustpilot reviews report dissatisfaction with Datadog's billing practices, accusing the company of employing questionable tactics such as hidden costs and not allowing users to remove their payment method or downgrade or end their subscription. Users advise being very careful about what is going to be charged and double-checking what is said even by their engineers.
Log management costs $0.10/GB indexed, retention adds more
Log Management has complex pricing: ingestion is one cost, indexing is $0.10/GB, and retention policies add additional charges. Users struggle to understand index logs vs non-index logs vs retention pricing. It's very flexible, which creates many confusing options when trying to control costs. Many teams accidentally index more logs than needed.
Vendor lock-in through proprietary agent makes migration painful
A significant issue with Datadog is vendor lock-in, driven by its proprietary agent. To use Datadog, you must embed their agent throughout your infrastructure. If you ever decide to switch platforms, you face a major migration project. The agent deployment and custom dashboards don't transfer to other platforms.
Aggressive marketing and sales outreach annoys users
Trustpilot reviews mention the company harassing customers with unsolicited marketing emails and phone calls, with no intention to stop. Users who signed up for trials or evaluated the product report persistent sales outreach even after declining. This aggressive approach damages trust.
Steep learning curve overwhelms new users with complex UI
Datadog offers a wide range of features that can be overwhelming for new users. The UI is dense and configuration steps are overwhelming - especially when setting up multi-service tracing, infrastructure maps, or custom metrics dashboards. Creating custom dashboards and metrics isn't straightforward, with what should be simple configurations often turning into time-consuming projects.
Setting up dashboards and monitors requires significant expertise
Setting up dashboards, tuning alert rules, building monitors, navigating between products, and optimizing usage takes considerable time and expertise. Getting the full benefit of Datadog requires significant technical expertise. The setup process can be time-consuming and may require dedicated resources or experienced personnel.
Documentation is vague on pricing and metric rate changes
Some areas are too vague, with no reply on issues like metric rate changes by time window, custom metrics insights, APM changes, and pricing structure. Users report that pricing details can be intricate and often require careful monitoring to avoid unexpected charges. The lack of clear documentation makes cost prediction nearly impossible.
Support unhelpful and stonewalls with tickets
Users report that Datadog's support is not very helpful, with one Reddit user stating 'Support is utter sh*t... they stonewall you with tickets and miss half the questions.' Capterra reviews mention experiences with support have been continuously negative, with the company going out of its way to avoid direct communication and offering irrelevant answers.
Billing disputes and deployment mistakes hard to resolve
Users have reported difficulties in resolving deployment mistakes and billing issues, with frustration about the lack of support and inability to remove metrics from agents or adjust billing accordingly. Once you've turned on features that generate costs, getting them reversed or corrected is extremely difficult.
Platform has become significantly slower over the past year
Datadog has become significantly slower over the last year, with performance potentially affected by ongoing feature work. Users report slow dashboard loading times, delayed metric queries, and lag in the interface. The biggest drawback is the relatively slow pace at which performance issues are addressed.
OpenTelemetry implementation is incomplete and inconsistent
The incomplete and sometimes inconsistent implementation of OpenTelemetry compatibility is a significant issue, especially noticeable with features such as handling 'resources' in APM. Teams wanting to use open standards find Datadog's OTel support lacking compared to competitors. This creates vendor lock-in concerns for those wanting to maintain flexibility.
Regret Patterns
Common reasons users regret choosing Datadog.
Bill shock: invoice was 3-12x higher than budgeted
Teams budget based on per-host pricing but receive invoices 3-12x higher due to custom metrics, log indexing, APM spans, and other usage-based charges. The VP of Engineering who budgeted $12K/month and got a $147K bill is a common pattern. By the time they see the bill, they've already incurred the costs.
Enabled 'all the things' and costs exploded
Teams excited about Datadog's features enable APM, logs, custom metrics, RUM, and synthetics without understanding the cost implications. It's easy to turn everything on - the surprise bill comes later. Some organizations see 10x cost increases within a quarter.
Underestimated learning curve, can't get value from investment
Organizations purchase Datadog expecting quick value but find the steep learning curve prevents effective use. Dashboards remain unconfigured, alerts are noisy, and teams struggle to navigate the complex UI. The investment doesn't pay off because they can't use it effectively.
Locked in and can't afford to switch
Teams that deployed Datadog agents everywhere and built extensive dashboards find migration prohibitively expensive. The proprietary agent, custom configurations, and institutional knowledge create strong lock-in. Even when costs become unbearable, switching feels impossible.
Free tier was useless, forced to upgrade immediately
Teams that signed up for the free tier expecting useful monitoring find it's essentially a demo. The 5-host limit and 1-day retention make it impossible to troubleshoot real issues. They're forced to upgrade almost immediately, often without budget approval.
Infrastructure scaled and Datadog costs became prohibitive
Teams that started with manageable Datadog costs find bills growing exponentially as infrastructure scales. Adding microservices, containers, and hosts multiplies costs linearly. What was affordable at 20 hosts becomes prohibitive at 200.
When Datadog Breaks Down
Specific scenarios where Datadog fails or underperforms.
Infrastructure grows beyond initial estimate
Per-host pricing means every new server, container, or instance increases costs. Teams that started small find costs scaling linearly with infrastructure. A 10x growth in hosts means 10x in Datadog costs - often unexpected when planning expansion.
Custom metrics explode from microservices architecture
Each custom metric costs $0.05, and microservices architectures can generate thousands. Teams instrumenting 50 services with 100 custom metrics each face $250+/month in metrics alone. The costs compound quickly without aggressive metric management.
Log volume spikes from application issue
An application bug or infrastructure issue causes log volume to spike 10-100x. Since logs are billed per GB indexed, a spike can result in a massive unexpected bill. Without proper exclusion filters and alerts, costs can spiral before anyone notices.
Need to enable APM for troubleshooting
Teams using Datadog for infrastructure monitoring discover they need APM to diagnose application issues. Enabling APM adds $31-40/host ON TOP of existing infrastructure costs, potentially doubling the bill overnight for comprehensive coverage.
Annual contract ends and on-demand pricing kicks in
Teams that locked in annual pricing face 20% higher on-demand rates when contracts expire. If budget approval for renewal is delayed, costs spike immediately. The pressure to renew quickly can lead to unfavorable contract terms.
New team member can't configure dashboards effectively
A new DevOps hire struggles with Datadog's steep learning curve. Dashboards remain unconfigured, alerts are too noisy, and the team can't diagnose issues effectively. The investment in Datadog doesn't pay off without experienced users.
Need to migrate away but proprietary agent is everywhere
Leadership decides to switch monitoring platforms for cost reasons, but the Datadog agent is deployed on every host, and years of dashboard configurations exist. The migration project is estimated at months of work, effectively trapping the organization.
Support can't resolve billing dispute
A configuration mistake or unexpected usage spike results in a large unexpected bill. Support stonewalls with tickets and offers no meaningful resolution. The organization is stuck paying for charges they didn't anticipate or understand.