Post

Giving an agent read-only access to the telemetry data of a well-instrumented system and asking a question is a wild experience They are very good at this, easily better than the vast majority of engineers, and unlike engineers their attention is very cheap

austin@aparker.io

saw someone say AI can’t write SQL some data for anyone that cares - @honeycomb.io offers agents a query tool against our datastore; it’s a custom JSON schema, which means it’s very unlikely to be something models know very well from the jump

As a corollary to this, observability tools should expect a *lot* of growth in query volume. Users that hook agents up end up doing orders-of-magnitude more queries

0 reposts12 likes

Separating compute and storage goes from a nice-to-have to absolutely necessary FireTiger was recently acquired, but I think their approach of “just give an agent a machine and duckdb and let it go ham” was very underrated bsky.app/profile/jere...

Jeremy Morrell@jeremymorrell.dev

"Land OTLP on an object store as parquet" and then "Give an agent duckdb" is probably the 80-20 galaxy brain move for o11y in 2026

I don’t want to bang on too much about ClickHouse cloud, but it really is magical for this. Whack a read only replica on a warehouse is magic. Things like being able to set profile boundaries like a default max mem of 1GB, but allowing agents to override to 10GB memory is also magic.

I’m more in the DC world these days, but we exposed snapshots of desired state into CH and then have all the telemetry flowing into it too, and the agent harnesses “just work” at locating deltas with JOINs