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

FAQ

Why is the Datadog Agent described as a competitive moat? The Agent ships with 700+ integration libraries, collects sub-second granularity custom metrics through DogStatsD, and gathers system signals plus APM traces that agentless platforms cannot reach. Honeycomb, Lightstep, and Chronosphere lean more agentless and can't match that depth.

Abandoning the Agent would cede that advantage to New Relic and Dynatrace.

Which workloads actually require an agentless approach? Serverless functions like AWS Lambda, Azure Functions, and Google Cloud Run can't run a persistent agent. Managed Kubernetes such as EKS Fargate and SaaS apps like Salesforce, Slack, and GitHub give no host-level access for an agent.

Edge and IoT devices also have bandwidth and battery limits that prohibit one.

What does the recommended dual-mode strategy actually look like? The Agent stays the deep-mode option for custom application APM, container and Kubernetes internals, and high-cardinality sub-second metrics. Agentless covers breadth through cloud API connectors, OpenTelemetry receivers, and lightweight edge SDKs.

New Relic and Dynatrace already run this hybrid model, and Datadog is advised to match it.

How does OpenTelemetry threaten Datadog's proprietary Agent? OpenTelemetry graduated within the CNCF in 2024 and has 6,000+ community contributors, so as it matures customers may prefer vendor-neutral instrumentation over a proprietary agent. The mitigation is to support OTel natively, which Datadog already does via the OTel collector.

That lets Datadog ingest standard telemetry without losing its own depth.

Roughly how is Datadog's revenue split across its product segments? Industry estimates put Infrastructure at about 50% of total revenue and APM at around 25%, on FY24 revenue of $2.7B. That concentration in infrastructure and APM is exactly where the Agent's depth matters most.

Serverless and SaaS breadth is the growth area agentless would unlock.

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)

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