FINDING 01·Enterprise observability teams managing large fleets of business-hours apps·1 source
No support for scheduled maintenance windows or business-hours-only monitoring
Teams with apps that don't run 24/7 (e.g., 9-to-5 business apps) cannot properly configure Datadog to avoid false alerts during planned downtime. Maintenance windows exist but cannot be scheduled on a recurring basis, making availability tracking unreliable for non-continuous workloads. This was reported in 2022 and no resolution is indicated in the discussions.
Source
“The vast majority (500+) of the company app don't run 24*7, they have different business hours (like 9-5) but outside of these business hours, apps are shutdown. And Datadog don't support that. It has maintenance window but they can not be scheduled, the same is valid for monitoring mute.”
FINDING 02·Indie developers, small startups, solo builders·3 sources
Datadog pricing is prohibitively expensive for small teams and indie developers
A recurring and strongly-felt frustration — especially prominent in recent discussions (2022–2026) — is that Datadog's pricing model is inaccessible for solo developers, small startups, and low-traffic apps. Even basic APM visibility requires a minimum monthly spend, with no meaningful free tier for low-volume use cases. Synthetic monitoring costs are also called out as steep.
Source
“Is it just me or do you guys think Datadog pricing is crazy? I mean even to SEE APM you have to pay like $50/mo minimum. What if my app has just 10 requests per month, can I get for free? No, pay us. What if it's just me building? No, still pay us.”
Source
“Existing tools like Datadog Synthetic Monitoring are excellent but can be expensive for indie hackers or small startups (often ~$15/check).”
Source
“Datadog browser synthetics: $12/1,000 runs. AWS synthetics is the cost of running a lambda plus whatever logs/metrics you want to retrieve/persist. Worth it? Why? Better alternatives for synthetic testing? Cheaper, faster, hand rolled?”
FINDING 03·E-commerce teams, small dev agencies, indie hackers·1 source
Shallow synthetic monitoring — HTTP 200 OK masks real user-facing failures
Standard uptime/synthetic checks that only verify HTTP status codes miss critical application-layer failures (e.g., broken JavaScript, broken checkout flows). This gap was explicitly called out as a motivation for building an alternative, with a concrete example of lost sales going undetected for hours.
Source
“We had a client whose e-commerce site was 'Up' (returning 200 status codes), but the 'Add to Cart' button was broken due to a silent JavaScript error. They lost sales for 6 hours while our dashboard said 'All Systems Operational.'”
FINDING 04·Developers and engineering teams seeking cost-effective APM·1 source
No open-source, self-hostable APM with full transaction tracing (pre-2023)
As of mid-2020, users found many open-source options for log aggregation or server monitoring but nothing that matched the application-level tracing and transaction instrumentation of commercial APM tools like Datadog or New Relic. This pain drove significant community interest in open-source alternatives. Note: this discussion is from 2020; several open-source APM tools (SigNoz, OpenObserve, etc.) have since emerged to address this gap.
Source
“I'm curious if there is a good open source alternative out there for NewRelic or DataDog's APM service. I see lots of options for log aggregation or server monitoring, but haven't found anything with application integration so you can trace transactions.”
FINDING 05·Backend developers running multi-service local environments·1 source
Lack of a good local development log aggregation experience
Developers who rely on Datadog for cloud log management have no equivalent tool for local development. Switching between terminal windows and using workarounds like `jq` is cumbersome, and Datadog itself is not practical to run locally for dev/test workflows.
Source
“Locally I use a couple of docker-compose files to manage and run the services... running tests or doing dev work locally is a different story, I have to switch between terminal windows to look at various logs, use Find feature of terminal which sometimes can become difficult. I even started using jq to pipe logs to a nicely formatted JSON.”
FINDING 06·Node.js developers, teams with restricted infrastructure·1 source
Datadog Agent dependency is a barrier for certain log ingestion setups
Some users face constraints (infrastructure, security policy, or operational preferences) that prevent them from installing the Datadog Agent on their machines, yet they still need to ship logs to Datadog. This creates friction and drives searches for agent-less integration methods.
Source
“I'm looking for a solution to send logs from a Node.js application to Datadog without relying on the Datadog Agent (Which needs to be installed in machine). Are there alternative integration methods or libraries available for achieving this?”