Backend, storage & operations
View All TagsTrying 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.
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?
Until now the product opened on a screen that needed you to already have a hypothesis. The new Dashboard gives you one, and it is where the app now lands.
Deciding what Avuru Obs collects used to mean editing values.yaml, running
helm upgrade, and holding the cluster permissions to do it — so in practice
collection stayed whatever it was on install day. Now an admin changes it from
the app, and the sensor follows within seconds.
GET /api/v1/green/summary, /green/budgets and /green/report were
registered without the session middleware that every other signal route uses.
On an install with authentication enabled, all three answered 200 to a
caller with no session at all.
Deciding that payments is your most critical service used to mean editing
values.yaml, running helm upgrade, and holding the cluster permissions to do
it. So in practice it never happened: the Service Health board showed one
auto-discovered group per namespace and the tier lanes sat empty. Groups are now
authored in the app.
Two questions an operator asks in the first week — where is my telemetry actually stored? and what can this role do? — now have a screen each.
v0.4.0 finishes the account lifecycle you started in v0.2: users can now be edited, reset and deleted from the UI, and anyone can change their own password. Reviewing that surface turned up three ways to get into an account that shouldn't have worked — all three are closed. Alongside them, an install that silently lost its schema migration now heals itself.
avuru obs v0.3.0 is tagged. v0.2 secured the read side — login, roles, per-project grants, SSO. v0.3 closes the write side and turns the project into something you actually administer.
v0.3.1 is a patch: it fixes the chart's image defaults, which never pointed at the images the release workflow actually publishes. Nothing else changes — no schema migration, no API or configuration surface.