21 posts tagged with "UI"

Until now, a gateway believed whatever project a sender claimed. Now you can issue per-project ingest API keys and have the key decide instead — with a default that changes nothing until you are ready.

Projects are no longer only a deployment setting: admins can create, rename and delete them directly in Settings → General, and the switcher updates to match — while the built-in default and config-defined projects stay read-only.

You can now explore a live avuru obs without installing anything: one click on "Try the demo" signs you in as a read-only viewer against a running multi-service app, with real data across every module.

avuru obs now ships secure by default: the hub requires login, users carry fixed roles — Admin, Editor, Viewer — granted per project, and enterprise SSO works with any OpenID Connect identity provider (Keycloak, Microsoft Entra ID, Okta, Google, Dex) — in open source, not behind an enterprise tier, and with no auth proxy to deploy.

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.

avuru obs v0.1.0 is tagged: install the Helm chart on a fresh Kubernetes cluster and watch a live service map appear in under five minutes, zero app changes — a promise enforced in CI, not a demo.

The Profiling screen is live: cluster-wide CPU flame graphs, sampled by eBPF with zero app changes and stored in the same ClickHouse as your traces, logs and metrics. Experimental and opt-in for v0.1 (sensor.profiler.enabled=true) — the upstream alpha loader does not support every kernel yet.

The Nodes screen is live: CPU, memory and network per node, with the busiest pods underneath — collected by the sensor's node agent (kubeletstats), stored in the same ClickHouse as everything else.

The Metrics screen is live: request rate, error percentage and latency percentiles over time for the busiest services of the window — derived from the same spans the trace explorer uses, so there is nothing extra to instrument or operate.

The Services screen is live: every service seen in the selected window — auto-discovered zero-code on Kubernetes or sending OTLP directly — with its rate, error percentage and latency percentiles in one sortable table.