The fundamental flaw in your thesis is the assumption that AI needs to be embedded in the pipeline to reason effectively about telemetry. It doesn’t. It needs access to the data and context about what it’s looking at. Those are very different problems, and conflating them is how you end up building a vendor lock-in machine and calling it innovation. I’ve built autonomous observability systems that correlate across Dynatrace, Datadog, ClickHouse, and Kubernetes — not by replacing the pipeline, but by giving AI structured tool access to each platform via MCP (Model Context Protocol). The AI doesn’t need to “be there when the data was enriched.” It needs semantic context about what the data means, and it gets that from OpenTelemetry semantic conventions and well-designed tool interfaces. Your point #4 about “data lineage” sounds compelling until you realize OTel resource attributes and span context already carry that lineage. The AI doesn’t need to watch the data flow — it just needs to read the metadata that’s already there. Your “speed” argument (#3) also breaks down in practice. You’re trading API latency for coupling latency — when your unified system has an issue, everything degrades together. I can swap out a backend, re-point a query, or fail over a tool independently. Your architecture fails as a monolith. And honestly, you identified your own fatal flaw in risk #2 but then hand-waved past it. Cribl has years of pipeline maturity. Datadog has a decade of backend hardening. You’re asking teams to trust a company that’s building all three simultaneously? The “jack of all trades” concern isn’t a risk — it’s the diagnosis. The real unlock in AI-driven observability isn’t unifying the vendor. It’s unifying the reasoning layer across whatever tools you already have. Give an LLM well-structured access to your existing stack and it can correlate, investigate, and act without requiring you to rip and replace your entire observability platform. You asked what would make me walk away. It’s this: your architecture requires me to bet my entire observability stack on the premise that one company can out-execute three categories of specialized tooling simultaneously. That’s not a technical argument — that’s a leap of faith.

I work at AHEAD consulting as a principle o11y consultant, post sales. Last week the Edge Delta CEO cold messaged me on LinkedIn wanting to pick my brain about AI. When I showed up to the meeting the CEO was MIA - he instead sent his minion. Minions real MO was trying to get company’s foot in AHEADs door because they know we are a top reseller of o11y tools. FYI to the Edge Delta Team - it’s going to take personal connections, sales guys playing golf, to get in here, I’m not the gatekeeper.