Comparison — vendor pages read 2026-11-11
Observability Unified vs Datadog
Datadog is a SaaS observability platform run from independent regional sites, covering APM, logs, RUM and session replay, product analytics, Agent Observability, and a Datadog-hosted MCP server.
Observability Unified is a self-hosted platform that connects traces, logs, replay, profiles, and AI agent activity through shared IDs, and gives AI agents evidence with citations through MCP. Each row below says Yes, Partial, or No for both products and links to the page that supports it.
Where Observability Unified differs
- MCP write tools off unless enabled. Writes register only with OBS_MCP_ENABLE_WRITES=true
- MCP results link to source records. Evidence bundles with citations; dashboard deep links when OBS_DASHBOARD_URL is set
- Compacted evidence for AI agents. CCR bundles collapse repeated logs to exemplars within a token budget; refs expand them
- Records what an agent's tool call changed. Before, after, and diff values your app attaches to a tool call, stored as sent
- Fix verified by re-running the failing case. Same eval input fails on the baseline and passes on the candidate
- Points out gaps in your instrumentation. Flags spans with unexplained self-time in the waterfall and in get_trace
- Run the full platform yourself. Docker image, Node + Postgres/S3, or Cloudflare
Where Datadog offers more
- Write your own queries over telemetry. DDSQL Editor: SQL over telemetry, plus natural-language query building
- Vendor-hosted cloud service. Independent regional sites
- Built-in single sign-on. SAML
Capability by capability
Investigating with AI agents
| Capability | Observability Unified | Datadog |
|---|---|---|
| First-party MCP server | Yes Local stdio server, @obsunified/mcp-server our docs | Yes Remote, Datadog-hosted docs.datadoghq.com |
| MCP write tools off unless enabled | Yes Writes register only with OBS_MCP_ENABLE_WRITES=true our docs | Partial Writes need the mcp_write permission and an org setting docs.datadoghq.com |
| MCP results link to source records | Yes Evidence bundles with citations; dashboard deep links when OBS_DASHBOARD_URL is set our docs | Partial A tool that builds DDSQL Editor links docs.datadoghq.com |
| Agent tool calls alongside app traces | Yes Agent Action Graph links tool calls to traces our docs | Yes Agent spans link to APM traces docs.datadoghq.com |
| Compacted evidence for AI agents | Yes CCR bundles collapse repeated logs to exemplars within a token budget; refs expand them our docs | Partial MCP Server truncates responses, has max_tokens and says how to get more docs.datadoghq.com |
| Agent skills for coding agents | Yes Instrument and investigate skills, released as .skill bundles our docs | Yes Pup CLI and Datadog Labs repos ship agent skills (Labs is experimental) github.com |
Observing your own AI agents
| Capability | Observability Unified | Datadog |
|---|---|---|
| Records what an agent's tool call changed | Yes Before, after, and diff values your app attaches to a tool call, stored as sent our docs | Partial Tool spans capture inputs and outputs docs.datadoghq.com |
| MCP calls recorded with trace context | Yes MCP spans join the action graph; an optional allow-listed envelope records the context our docs | Yes MCP client and server calls traced as spans linked to the LLM trace docs.datadoghq.com |
| Production traces become eval cases | Yes Save as eval case from a trace or run; candidate runs compared step by step (HTTP API) our docs | Yes Add production traces to datasets; compare versions in offline experiments docs.datadoghq.com |
Change-aware investigation and remediation
| Capability | Observability Unified | Datadog |
|---|---|---|
| Compare releases and flag variants | Yes Error-rate lift per version and flag variant, normalized for traffic share our docs | Yes Deployment Tracking compares versions docs.datadoghq.com |
| Shared-dependency contention vs code regression | Yes Shared-degradation verdicts separate contention from the new version our docs | Yes Watchdog RCA separates root cause from affected services docs.datadoghq.com |
| Root cause states its level of proof | Yes Proof tier from unverified locus to counterfactual verified, kept apart from link certainty our docs | Yes Bits AI: evidence-backed conclusion or inconclusive docs.datadoghq.com |
| Fix verified by re-running the failing case | Yes Same eval input fails on the baseline and passes on the candidate our docs | Partial Bits remediation PRs and a Verify Resolution check docs.datadoghq.com |
| Remediation behind approval or a policy gate | Yes Approval queue or single-use grant; your runner executes; a watchdog checks recovery our docs | Yes Bits guardrails ask for approval before actions (Preview) docs.datadoghq.com |
| Matches new incidents to past ones | Yes Prior findings matched by fingerprint appear in incident evidence bundles our docs | Yes Bits Investigation reuses memories from past investigations in similar ones docs.datadoghq.com |
Signals
| Capability | Observability Unified | Datadog |
|---|---|---|
| Distributed tracing (OTLP) | Yes OTLP over HTTP; front gRPC with a Collector our docs | Yes OTLP through the Agent, a Collector, or direct intake docs.datadoghq.com |
| Structured logs | Yes Trace-correlated our docs | Yes Ingestion decoupled from indexing docs.datadoghq.com |
| AI / LLM observability | Yes AI calls, agent runs, evals our docs | Yes Agent Observability datadoghq.com |
| Session replay | Yes rrweb, browser DOM only our docs | Yes RUM Session Replay datadoghq.com |
| Browser click linked to its backend trace | Yes x-obs-interaction links a click to its trace, logs, and replay (browser SDK or header) our docs | Yes RUM requests linked to backend APM traces docs.datadoghq.com |
| CPU profile from a trace | Yes When profiling is enabled and samples carry the trace ID our docs | Yes Span to profile in seven languages docs.datadoghq.com |
| One ID chain from user to agent action | Yes user_id → session_id → interaction_id → trace_id → span_id → action_id our docs | Yes RUM links to APM traces; Agent Observability links to APM spans and RUM docs.datadoghq.com |
| Write your own queries over telemetry | Partial Search and filters; no query language or SQL editor our docs | Yes DDSQL Editor: SQL over telemetry, plus natural-language query building docs.datadoghq.com |
| Points out gaps in your instrumentation | Yes Flags spans with unexplained self-time in the waterfall and in get_trace our docs | Partial Tag rules flag telemetry without required tags docs.datadoghq.com |
Deployment and access
| Capability | Observability Unified | Datadog |
|---|---|---|
| Run the full platform yourself | Yes Docker image, Node + Postgres/S3, or Cloudflare our docs | Partial SaaS, with BYOC for logs datadoghq.com |
| Vendor-hosted cloud service | No Self-hosted only our docs | Yes Independent regional sites docs.datadoghq.com |
| Built-in single sign-on | No Front it with Cloudflare Access or oauth2-proxy our docs | Yes SAML docs.datadoghq.com |
Choosing between them
Choose Datadog if you want a managed platform with enterprise controls, broad integrations, and per-host budgeting.
Choose Observability Unified if you want AI agents and engineers to investigate the same production evidence, with the telemetry kept on infrastructure you run. It is early-stage software suited to single-team deployments; the documented trade-offs include no built-in SSO, OTLP over HTTP only, and browser-only session replay.
How these cells were checked
Yes and Partial cells cite the vendor's own docs, pricing, product page, or official repository. No is used only where the cited page says so. Not marketed† means we read the vendor's product pages and found no such capability; it is an inference, not a vendor statement. Not stated means the vendor's docs do not say either way.
Rows for MCP write defaults, MCP links, agent tool calls, CPU profiles, self-hosting, and SSO were read on 2026-11-10 (ledger with excerpts). Rows for release and flag comparison, proof of cause, fix verification, gated remediation, click to trace, and dependency contention were read on 2026-11-11 (ledger with excerpts). Rows for compacted evidence for agents, agent skills, one ID chain, and instrumentation gaps were read on 2026-11-11 (ledger with excerpts). Rows for tool-call side effects, MCP call recording, production traces to eval cases, incident memory, and ad-hoc queries were read on 2026-11-11 (ledger with excerpts). The MCP server row was read on 2026-11-10 (ledger), and the remaining rows on 2026-10-13 (ledger). Vendors change their products often; if a cell is out of date, send a correction. The full comparison covers all nine vendors with excerpts.