Should Datadog pivot from agent-based to agentless?
The Architectural Question
Datadog's core observability product is built around the Datadog Agent — open-source software installed on every host/container/Kubernetes pod that emits metrics, logs, traces. Agent is 700+ integration libraries deep; collects sub-second granularity custom metrics + system signals + APM traces.
The Agent is Datadog's competitive moat. Honeycomb + Lightstep (ServiceNow) + Chronosphere lean more agentless; Splunk APM (former SignalFx) has hybrid approach.
Why agentless gains share:
- AWS Lambda + Azure Functions + Google Cloud Run = serverless can't run persistent agent
- AWS EKS Fargate + Azure ACI + GCP Cloud Run = no host-level access
- SaaS apps (Salesforce, Slack, Notion, GitHub) = customer can't install agent on vendor's infra
- Edge/IoT workloads = bandwidth + battery constraints prohibit agent
Why agent-based stays critical:
- Custom application instrumentation requires agent
- System-level metrics (CPU, memory, disk, network) need agent
- Sub-second granularity required by Platform Engineering / SRE buyer
- 700+ pre-built integrations vs nascent OpenTelemetry receivers
The Dual-Mode Recommendation
Keep Agent for depth:
- Custom application APM (700+ integrations)
- Container + Kubernetes deep observability
- Custom-metric collection (DogStatsD)
- High-cardinality data with sub-second resolution
Add aggressive agentless for breadth:
- Cloud-managed services (Lambda, Functions, Cloud Run, EKS Fargate)
- SaaS app monitoring via webhook + API ingestion
- OpenTelemetry receivers (industry standard)
- Edge workloads via lightweight SDK
Dual-mode reference: New Relic + Dynatrace have hybrid agent + agentless. Datadog should match.
The Strategic Roadmap
TAGS: datadog-agent-vs-agentless-2027, dual-mode-observability, opentelemetry-receivers, serverless-observability, saas-app-monitoring, honeycomb-lightstep-chronosphere, 2027
Sources
- Datadog Agent open source: https://github.com/DataDog/datadog-agent
- Datadog Integrations: https://docs.datadoghq.com/integrations/
- OpenTelemetry: https://opentelemetry.io/
- Honeycomb (observability): https://www.honeycomb.io/
- Chronosphere: https://chronosphere.io/
- Lightstep (ServiceNow): https://lightstep.com/
- AWS Lambda observability: https://aws.amazon.com/lambda/
- Splunk APM (SignalFx): https://www.splunk.com/en_us/products/observability.html
Real Numbers (Verified)
| Data | Figure | Source |
|---|---|---|
| Datadog FY24 revenue | $2.7B | DDOG 10-K |
| Datadog Agent integrations | 700+ | Datadog docs |
| OpenTelemetry adoption | CNCF graduated 2024 | CNCF |
| Honeycomb valuation | ~$1B+ | Industry estimates |
| Chronosphere valuation | $1.6B+ (2022 Series C) | TechCrunch |
| Lightstep ServiceNow acquisition (2021) | undisclosed (estimated $300M+) | ServiceNow |
| AWS Lambda monthly invocations | trillions | AWS |
| AWS EKS Fargate + ECS Fargate growth | 30%+ YoY | AWS |
| Datadog APM revenue (segment estimated) | ~25% of total | Industry estimates |
| Datadog Infrastructure revenue (estimated) | ~50% of total | Industry estimates |
| New Relic-Francisco Partners + TPG 2023 acquisition | $6.5B | TechCrunch |
| Dynatrace (NYSE: DT) market cap | ~$16B 2024 | NYSE |
| Splunk-Cisco 2024 | $28B | Cisco |
| OpenTelemetry community contributors | 6,000+ total | OpenTelemetry |
| Datadog DogStatsD custom metrics | Sub-second granularity, high-cardinality | Datadog docs |
| Agent deployment platform support | Windows, Linux, macOS, container, K8s, lambda extension | Datadog |
| Lambda extension support | Datadog Lambda Extension | Datadog |
Dual-mode wins: depth from Agent + breadth from cloud APIs + OpenTelemetry.
Counter-Case
Pivoting fully agentless could simplify product. Reduces engineering investment in agent. Mitigation: agent is the moat — abandoning it cedes depth to New Relic + Dynatrace.
OpenTelemetry standard threatens proprietary agent. As OTel matures, customers may prefer vendor-neutral instrumentation. Mitigation: support OpenTelemetry natively (Datadog already does via OTel collector); keep agent as performance-optimized option.
Customer complexity of dual-mode. Customers confused which mode to use for which workload. Mitigation: clear documentation + sales engineering guidance; "Agent for compute, agentless for serverless/SaaS" rule.
Engineering cost of dual maintenance. Two product lines = 2x engineering investment. Mitigation: shared platform engineering; agent + agentless share data ingestion pipelines.
When agent-only stays-the-course wins. If customers' serverless adoption plateaus or reverses (unlikely), agent-only may be enough. Mitigation: hedge bet by investing in agentless even if usage modest.
Honeycomb + Chronosphere + Lightstep slower than expected. Niche observability players haven't disrupted Datadog meaningfully. Mitigation: don't rush agentless pivot; measured dual-mode investment.
See Also
- q1689 — Datadog moat New Relic + Dynatrace
- q1710 — AI agents triage telemetry 2027
- q1684 — Datadog Cloud SIEM beat Splunk + Sentinel
- q1715 — Datadog M&A strategy