Replace Grafana for host monitoring with Beszel #27

Closed
opened 2026-05-23 20:54:30 +00:00 by coilysiren · 1 comment
Owner

Originally filed by @coilysiren on 2026-05-22T08:25:49Z - https://github.com/coilysiren/infrastructure/issues/241

Problem - Grafana usability is poor and the only thing Kai actually wants from it is multi-host CPU, memory, and disk at a glance.

Plan:

  • Deploy a Beszel hub on k3s, agent on each machine. Beszel is a lightweight Go + SQLite monitoring hub with a clean flat green/red/yellow UI.
  • Once Beszel covers the need, decommission Grafana or simply stop opening it.

Fallback option if Beszel falls short: Netdata (per-host deep metrics, near-zero config).

Recommendation: Beszel.

Origin: self-hosted chat sweep, 2026-05-21.

_Originally filed by @coilysiren on 2026-05-22T08:25:49Z - [https://github.com/coilysiren/infrastructure/issues/241](https://github.com/coilysiren/infrastructure/issues/241)_ **Problem** - Grafana usability is poor and the only thing Kai actually wants from it is multi-host CPU, memory, and disk at a glance. Plan: - Deploy a **Beszel** hub on k3s, agent on each machine. Beszel is a lightweight Go + SQLite monitoring hub with a clean flat green/red/yellow UI. - Once Beszel covers the need, decommission Grafana or simply stop opening it. Fallback option if Beszel falls short: **Netdata** (per-host deep metrics, near-zero config). Recommendation: Beszel. Origin: self-hosted chat sweep, 2026-05-21.
Author
Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.
coilysiren 2026-06-17 08:22:57 +00:00
Sign in to join this conversation.
No description provided.