Comparison — vendor pages read 2026-11-11
Observability Unified vs Uptrace
Uptrace is an OpenTelemetry-native platform offered as Uptrace Cloud, as AGPL open source to self-host, or as a licensed on-prem install, with an MCP server built in.
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
- Agent tool calls alongside app traces. Agent Action Graph links tool calls to traces
- Compacted evidence for AI agents. CCR bundles collapse repeated logs to exemplars within a token budget; refs expand them
- Agent skills for coding agents. Instrument and investigate skills, released as .skill bundles
- Records what an agent's tool call changed. Before, after, and diff values your app attaches to a tool call, stored as sent
- MCP calls recorded with trace context. MCP spans join the action graph; an optional allow-listed envelope records the context
- Production traces become eval cases. Save as eval case from a trace or run; candidate runs compared step by step (HTTP API)
- Compare releases and flag variants. Error-rate lift per version and flag variant, normalized for traffic share
- Shared-dependency contention vs code regression. Shared-degradation verdicts separate contention from the new version
- Root cause states its level of proof. Proof tier from unverified locus to counterfactual verified, kept apart from link certainty
- Fix verified by re-running the failing case. Same eval input fails on the baseline and passes on the candidate
- Remediation behind approval or a policy gate. Approval queue or single-use grant; your runner executes; a watchdog checks recovery
- Matches new incidents to past ones. Prior findings matched by fingerprint appear in incident evidence bundles
- AI / LLM observability. AI calls, agent runs, evals
- Session replay. rrweb, browser DOM only
- Browser click linked to its backend trace. x-obs-interaction links a click to its trace, logs, and replay (browser SDK or header)
- CPU profile from a trace. When profiling is enabled and samples carry the trace ID
- One ID chain from user to agent action. user_id → session_id → interaction_id → trace_id → span_id → action_id
- Points out gaps in your instrumentation. Flags spans with unexplained self-time in the waterfall and in get_trace
Where Uptrace offers more
- Write your own queries over telemetry. Span query language with group-by and aggregates; PromQL-compatible
- Vendor-hosted cloud service. Uptrace Cloud
- Built-in single sign-on. Business and Enterprise editions
Capability by capability
Investigating with AI agents
| Capability | Observability Unified | Uptrace |
|---|---|---|
| First-party MCP server | Yes Local stdio server, @obsunified/mcp-server our docs | Yes Built into Uptrace uptrace.dev |
| MCP write tools off unless enabled | Yes Writes register only with OBS_MCP_ENABLE_WRITES=true our docs | Partial OAuth read or write scopes, plus write permission uptrace.dev |
| MCP results link to source records | Yes Evidence bundles with citations; dashboard deep links when OBS_DASHBOARD_URL is set our docs | Not stated Not stated on the MCP page uptrace.dev |
| Agent tool calls alongside app traces | Yes Agent Action Graph links tool calls to traces our docs | Partial OpenTelemetry GenAI instrumentation guides uptrace.dev |
| Compacted evidence for AI agents | Yes CCR bundles collapse repeated logs to exemplars within a token budget; refs expand them our docs | Partial MCP tools aggregate spans and logs into groups; list tools return records uptrace.dev |
| Agent skills for coding agents | Yes Instrument and investigate skills, released as .skill bundles our docs | Partial MCP server serves skill guides as resources uptrace.dev |
Observing your own AI agents
| Capability | Observability Unified | Uptrace |
|---|---|---|
| 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 Guides record tool calls as spans with input and output uptrace.dev |
| MCP calls recorded with trace context | Yes MCP spans join the action graph; an optional allow-listed envelope records the context our docs | Not marketed† MCP pages cover Uptrace's own MCP server uptrace.dev |
| 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 | Not marketed† Not found on the AI and LLM pages read uptrace.dev |
Change-aware investigation and remediation
| Capability | Observability Unified | Uptrace |
|---|---|---|
| Compare releases and flag variants | Yes Error-rate lift per version and flag variant, normalized for traffic share our docs | Partial Group by service version; deploy and flag annotations uptrace.dev |
| Shared-dependency contention vs code regression | Yes Shared-degradation verdicts separate contention from the new version our docs | Partial Service graph with per-edge errors and latency uptrace.dev |
| Root cause states its level of proof | Yes Proof tier from unverified locus to counterfactual verified, kept apart from link certainty our docs | Partial AI incident analysis with its evidence uptrace.dev |
| Fix verified by re-running the failing case | Yes Same eval input fails on the baseline and passes on the candidate our docs | Not marketed† Not in the Uptrace docs we read uptrace.dev |
| Remediation behind approval or a policy gate | Yes Approval queue or single-use grant; your runner executes; a watchdog checks recovery our docs | Partial AI incident recommendations you accept or reject uptrace.dev |
| Matches new incidents to past ones | Yes Prior findings matched by fingerprint appear in incident evidence bundles our docs | Partial Groups similar logs and exceptions uptrace.dev |
Signals
| Capability | Observability Unified | Uptrace |
|---|---|---|
| Distributed tracing (OTLP) | Yes OTLP over HTTP; front gRPC with a Collector our docs | Yes OTLP over gRPC and HTTP uptrace.dev |
| Structured logs | Yes Trace-correlated our docs | Yes Logs alongside traces and metrics uptrace.dev |
| AI / LLM observability | Yes AI calls, agent runs, evals our docs | Partial OpenTelemetry GenAI instrumentation guides uptrace.dev |
| Session replay | Yes rrweb, browser DOM only our docs | Not marketed† Not in the product pages we read github.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 | Partial Browser OpenTelemetry spans correlated with backend uptrace.dev |
| CPU profile from a trace | Yes When profiling is enabled and samples carry the trace ID our docs | No Profiles are not ingested yet uptrace.dev |
| One ID chain from user to agent action | Yes user_id → session_id → interaction_id → trace_id → span_id → action_id our docs | Partial LLM spans nest in the app trace with user ID attributes uptrace.dev |
| Write your own queries over telemetry | Partial Search and filters; no query language or SQL editor our docs | Yes Span query language with group-by and aggregates; PromQL-compatible uptrace.dev |
| Points out gaps in your instrumentation | Yes Flags spans with unexplained self-time in the waterfall and in get_trace our docs | Not marketed† Not found on the trace feature, reference, and MCP pages read uptrace.dev |
Deployment and access
| Capability | Observability Unified | Uptrace |
|---|---|---|
| Run the full platform yourself | Yes Docker image, Node + Postgres/S3, or Cloudflare our docs | Yes Community and paid self-hosted editions uptrace.dev |
| Vendor-hosted cloud service | No Self-hosted only our docs | Yes Uptrace Cloud github.com |
| Built-in single sign-on | No Front it with Cloudflare Access or oauth2-proxy our docs | Yes Business and Enterprise editions uptrace.dev |
Choosing between them
Choose Uptrace if you want an OpenTelemetry-native backend with per-GB pricing and a built-in MCP server.
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.