A design note ranks where a classifier that answers with a calibrated probability, never with text, would fit avuru obs, and what each use would cost the promise that nothing leaves the cluster. An offline harness measures the first case before any model is ever called from the product.

Pick the services and workloads you care about, choose which sources to read, and follow their logs as one merged stream or as side-by-side panels — from Signals → Logs and from the new Service Mesh → Logs tab.

Inspect Node and Pod placement in an interactive 3D view, then follow the connections recorded in your traces.

The service map becomes the application entry point: select a service, keep the map in view, and step into its callers, dependencies, traces and logs from one inspector.

A service's Logs tab no longer comes up empty when the pod files its lines under a different name, and every log table can now copy, select and download the lines it shows. Both are on main for the next release.

An error issue is meant to be one failure with an occurrence count beside it. For errors derived from log lines it had quietly become one issue per request — and chasing that turned up two more fixes.

The Errors screen showed a page of fingerprints and nothing about the shape of them — and on a busy install, most of those fingerprints could not be reached at all.

Two changes to logs, both on main for the next release: a line tailed from a pod's stdout now carries a severity, and a workload's Logs tab on the mesh screen starts from the workload's own lines.

A namespace row that says STRICT is reporting a claim. A strict policy that is enforced and one that is not — a workload that never enrolled, a selector that matches nothing, a rule disabling TLS underneath — look identical from configuration and from traces. Only the proxy that terminated the connection knows, and until now nothing asked it.

v0.15.0 puts, on one row, what your mesh's configuration says about a workload and what its proxy actually did — and gives every workload the cluster runs a row, whether or not it ever sent a span.