8 posts tagged with "Logs"

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.

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.

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.

v0.16.0 makes a workload's page on the mesh screen read like the cluster's own record of it, and puts its logs on it — its own lines, and the lines the node proxy and its waypoint wrote about it, joined by the hub that knows its pods.

Installing the Helm chart now deploys a per-node sensor that observes every service on the cluster — eBPF traces, RED metrics and log collection with no SDK, no sidecar, no app changes.

Logs are searchable and wired to traces.