5 posts tagged with "Sustainability"

v0.6.0 is about the two ends of the pipe. Getting data in no longer means re-pointing every sender you own, and getting a second cluster on the screen no longer means a second instance. Adopting avuru obs became a reversible decision instead of a migration.

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.

The green module reported energy only where the hardware exposes RAPL — which excludes the overwhelming majority of public-cloud VMs. An opt-in TDP estimator now models CPU power from utilization on those nodes, so a fleet that runs entirely on cloud instances stops seeing an empty /green.

avuru obs v0.2.0 is tagged. v0.1 proved the wedge — a live service map in under five minutes, zero app changes. v0.2 makes that install one a real team can run every day: secure by default, modular by design, and four new modules that turn the data you already collect into triage, status and accountability.

The new green module turns the pod→service map you already run into per-service energy (Wh) and carbon (gCO2e) — the numbers ESRS E1 / CSRD and internal sustainability targets ask for, without a spreadsheet estimate or a SaaS that wants your telemetry. Energy is measured by CNCF Kepler (from the CPU's RAPL counters); avuru obs already knows which pod is which service, so it attributes joules to the services on your map. Self-hosted, zero app changes, no external API.