v0.10.0 answers a question that comes from outside the platform team: what is this cluster costing, and how much of it is buying nothing? A Kubernetes cluster is sized by what its workloads reserve, not by what they use — and until now avuru obs only knew the second half of that sentence.

v0.9.0 is for clusters where the network is not a straight line. A service mesh intercepts every call, so a dependency graph either draws hops that are not dependencies or draws nothing at all — and the kernel underneath has been seeing faults nobody was asking it for.

v0.8.0 is about the screen people actually look at. The service map has been the product's front page since v0.1 and a graph of circles for just as long. This release taught it to say more — and it needed no new collection: everything below is drawn from telemetry that was already arriving.

v0.7.0 is about the words your data is filed under and the surfaces that read it. v0.6 opened both ends of the pipe; what arrived was only as useful as the vocabulary available to slice it — and, it turned out, as truthful as the map drawing it.

Observing a second cluster used to mean running a second instance — its own store, its own UI, its own login. Projects now stretch across clusters instead: one screen, one store, and an install that can be just the ingest half.

v0.6.0 is about the two ends of the pipe. Getting data in no longer means re-pointing every sender you own, and getting a second cluster on the screen no longer means a second instance. Adopting avuru obs became a reversible decision instead of a migration.

Trying a new observability backend used to mean re-pointing or re-instrumenting every sender first. The gateway now speaks the protocols your fleet already emits, and can forward everything to your current backend at the same time.

Two gaps closed in Settings → Access: the identity-provider group mapping is no longer a value only a helm upgrade could change, and scripts get a credential of their own instead of a borrowed session cookie.

v0.5.0 closes the gap between running avuru obs and changing it. Nearly everything an operator used to reach through values.yaml and a redeploy — collection, service groups, the SSO role mapping, API credentials — now lives in the app, and the app itself opens on a screen that answers how is the estate doing?

A node used to turn red the moment any error happened in the window — never telling you whether the service was actually in trouble. The service map now answers that question, and a few more.