FINDING 01·Enterprise observability teams managing large fleets of business-hours apps·1 source
No support for scheduled maintenance windows / non-24×7 app monitoring
Datadog's availability monitoring does not support apps that run on business-hour schedules. Maintenance windows cannot be scheduled, and monitoring mutes cannot be automated, making it unsuitable for enterprises with hundreds of non-continuous services.
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·Ops teams running 24/7 infrastructure (circa 2014)·1 source
Unreliable alerting from incumbent monitoring tools
An older (2014) complaint about CopperEgg — a Datadog-era competitor — highlights that missed alerts and phantom alerts from monitoring services are a foundational pain that drove users to seek alternatives. While this is a dated discussion, it reflects a persistent baseline expectation for monitoring reliability.
Source
“I didn't get an alert when I should have done. One server had high CPU for over 5 mins when the alert should be triggered after 1 minute. The Copperegg support weren't not all that helpful, merely agreeing that an alert should have been triggered.”
FINDING 03·Indie hackers, solo developers, small startups·3 sources
Prohibitive pricing for small teams and low-traffic apps
Users — especially indie hackers, solo developers, and small startups — find Datadog's pricing model inaccessible. Even minimal APM usage requires a paid plan, with no meaningful free tier for low-volume workloads. This is a recurring and recent complaint (2022–2026).
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
“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?”
Source
“Existing tools like Datadog Synthetic Monitoring are excellent but can be expensive for indie hackers or small startups (often ~$15/check).”
FINDING 04·Developers and DevOps engineers seeking cost-free or self-hosted observability·1 source
Lack of open-source / self-hostable APM with full transaction tracing
Users seeking open-source alternatives to Datadog's APM find plenty of log aggregation or server monitoring tools, but very few that offer application-level integration with distributed tracing. This gap has driven multiple open-source projects to emerge (SigNoz, Coroot, OpenObserve, OneUptime).
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·E-commerce teams, small dev agencies, indie hackers·1 source
Synthetic monitoring only checks HTTP status, misses real user-flow failures
Standard uptime/synthetic monitoring tools (including Datadog's) report a site as 'up' based on HTTP 200 responses, while actual user-facing flows (e.g., checkout, login) can be silently broken. This gap caused real revenue loss for at least one user.
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 06·Backend/full-stack developers doing local development with Docker·2 sources
No good local development log aggregation experience
Developers running services locally via Docker Compose lack a lightweight, Datadog-equivalent UI for aggregating, filtering, and searching container logs. They resort to switching between terminal windows or piping logs through CLI tools like jq.
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.”
Source
“I even started using jq to pipe logs to a nicely formatted JSON.”
FINDING 07·Node.js / cloud developers with restricted deployment environments·1 source
Agent-based log shipping is a deployment constraint
Some users cannot or prefer not to install the Datadog Agent on their machines, and seek alternative methods to ship logs (e.g., directly from Node.js). The agent requirement is seen as an operational burden in constrained environments.
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?”