Skip to content
Notifications
Clear all

Hot take: All the AI observability vendors are just wrapping OpenTelemetry.

3 Posts
3 Users
0 Reactions
35 Views
(@charliea)
Reputable Member
Joined: 2 months ago
Posts: 247
Topic starter   [#20736]

I've been deep-diving into the new wave of AI-powered observability tools (you know the names). After testing a bunch, I'm seeing a pattern.

They all seem to be:
* A managed OpenTelemetry collector
* With a fancy UI/query layer on top
* Tying it together with AI for "anomaly detection" or "root cause"

It feels like the real differentiation is just:
* The quality of their pre-built dashboards
* How they handle pricing (e.g., per-user vs. per-GB)
* Their specific AI model's accuracy

Am I missing something? What unique value are we actually paying for if the core data is standard OTel? 🤔

Tried:
- Vendor A (good UI, expensive)
- Vendor B (great alerts, poor docs)
- Vendor C (cheap, high latency)

The setup for each was nearly identical: deploy OTel collector, forward traces/metrics/logs.


Demo or it didn't happen


   
Quote
(@cloud_cost_analyst_pro)
Honorable Member
Joined: 6 months ago
Posts: 469
 

You're correct on the technical layer. The cost difference comes from their data handling and pricing models, not the collector.

Managed OTel is a commodity. The premium is for storage and query compute. Vendor A's expensive UI is likely backed by expensive read-optimized storage. Vendor C's low price means high-latency object storage.

The real test: calculate your monthly ingest volume, then price out the equivalent data pipeline on your cloud (S3, Athena, Grafana). The delta is what you're paying for their "AI." Most times, it's a 300-400% markup.


cost per transaction is the only metric


   
ReplyQuote
(@elenab)
Estimable Member
Joined: 2 months ago
Posts: 202
 

You're spot on about the pattern. Where I think you're missing something is the "tying it together" part. That's the expensive glue, and it's where most of them fail.

The unique value isn't in the OTel collector, it's in the contextual stitching of your traces, metrics, and business logic *before* the AI ever looks at it. Most vendors just run anomaly detection on a siloed metric and call it a day. The premium is supposed to be for correlation that saves an engineer time. In practice, I've found you're paying for the *idea* of that correlation, not the execution.

Your test results (expensive UI, poor docs, high latency) are the real differentiators. They're telling you where each vendor cut corners to build their "AI" layer on top of a commodity data pipeline. The question isn't what unique value you're paying for, it's which set of trade-offs you're willing to subsidize.


show me the tco


   
ReplyQuote