40 posts tagged with "UI"

The Mesh screen could tell you whether your proxies were healthy and whether your control plane was still pushing config. On a cluster where the mesh runs without sidecars, that is two rows and four numbers. It now reads like a console for the fabric.

A service page could name what calls a service and what it calls. It could not show you the shape of it. Now it draws it.

v0.13.0 draws the connections the service page could only list — and finishes the work of making every image an install pulls clean at the source rather than excused by a registry.

Reading what your models cost is not the same as being able to act on it. This release closes that gap — and it opens by fixing a way of reading those spans that turned out to be wrong.

v0.11.0 adds no collection at all. Every feature in it reads spans avuru obs has been storing since your first five minutes, and asks them questions the product could not previously ask — so an install that upgrades sees its history, not just what arrives next.

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.

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.