Skip to main content

v0.17.0 — Explorer: the map is the front door, every signal one click away

avuru obs team
Maintainers

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.

  • Explorer. Selecting a node keeps the map visible and opens an inspector with callers, dependencies and links to service details, traces and logs. The selection is shareable in the URL and a keyboard-accessible selector offers the same path. Inferred dependencies keep their own latency and health unavailable and point at the callers' evidence instead. A new installation explains how to connect eBPF and OTLP; a failed read offers retry.
  • Themes across the application. Sage and forest surfaces replace the previous palette, with lime accents in dark mode and separate status colours. Light is the new default and an existing preference is kept. Mobile navigation exposes the same module-aware destinations and project controls.
  • Errors, logs and levels. Shipped in the same line and described in their own entries: the Errors screen's summary band, issues grouped by error again, a service's Logs tab resolving its workload, and log copy and download, and container log bodies yielding a severity.
  • Security floor. gRPC-Go raised to v1.83.2 in the gateway and node-agent distributions, and the MCP tools reach a service that ships logs but no traces.

See Service map and the release artifacts.