Beszel¶
Server monitoring dashboard at
monitor.448.global. The single pane that says "are our boxes alive and what are they doing?".
| Field | Value |
|---|---|
| Public URL | https://monitor.448.global |
| Audience | engineers / ops |
| Criticality | medium-high — its failure means we're flying blind |
| Maturity | [INFO NEEDED] |
| Owner | [INFO NEEDED] |
| Last reviewed | 2026-05-05 |
1. At a glance¶
Beszel is a lightweight server-monitoring tool. It shows CPU, memory, disk, and container status across all the servers running our self-hosted apps. If Beszel is broken, we can still operate — but we lose the early-warning signal that catches problems before users do.
2. Business purpose¶
- Real-time view of server health across the estate.
- Early warning for disk fills, memory leaks, runaway containers.
- Historical metrics to validate capacity decisions.
3. Audience¶
Engineering / ops staff.
4. Hosting & cloud infrastructure¶
Infrastructure map¶
| Item | Value | Notes |
|---|---|---|
| Public hostname | monitor.448.global | |
| Public IP(s) | [INFO NEEDED] |
|
| Private/internal IP | [INFO NEEDED] |
|
| Open ports | 443 [CONFIRM] |
|
| TLS cert | [INFO NEEDED] |
|
| Reverse proxy | [INFO NEEDED] |
|
| Container image / version | henrygd/beszel:[INFO NEEDED] |
|
| Host server name | [INFO NEEDED] |
|
| Number of agents (monitored hosts) | [INFO NEEDED] |
|
| Database | SQLite (Beszel default) [CONFIRM] |
Credentials in Vault¶
| Secret type | Vault path / link | Last rotated |
|---|---|---|
| Beszel admin login | [INFO NEEDED] |
|
| Per-agent registration tokens | [INFO NEEDED] |
5. Technology behind it¶
- Type: off-the-shelf
- Product: Beszel (open-source, beszel.dev)
- Stack: Go + SQLite
6. Data it handles¶
- System metrics (CPU, memory, disk, network, container counts).
- Agent connection metadata (hostnames, IPs).
- Alert history.
- Operator credentials.
7. External dependencies¶
- Email / push for notifications (likely Gotify integration
[INFO NEEDED]). - The Beszel agents on every monitored host (one-way push).
8. Authentication & access¶
- End-user login: Beszel local accounts
[CONFIRM] - OIDC / Authentik?
[INFO NEEDED] - MFA?
[INFO NEEDED]
9. Maturity assessment¶
| Dimension | Status | Evidence |
|---|---|---|
| Backups | [INFO NEEDED] |
SQLite file is small; should be backed up regularly |
| Monitoring (of Beszel itself) | [INFO NEEDED] |
who watches the watcher? |
| Alerting | [INFO NEEDED] |
configured alert channels (Gotify, email) |
| Redundancy | [INFO NEEDED] |
typically single |
| Coverage | [INFO NEEDED] |
does every host run an agent? |
10. Known risks & vulnerabilities¶
[INFO NEEDED]Coverage gaps — a host without an agent is invisible. This is the most common monitoring failure mode.[INFO NEEDED]No alerting → silent failures — Beszel can show problems on its dashboard but if alerts aren't wired to a channel humans actually watch (Gotify, email, Slack), the dashboard becomes a "nobody looked" artefact.[INFO NEEDED]Beszel's own monitoring — is anything alerting on Beszel-down? If not, "Beszel is broken" is itself an undetected failure.[INFO NEEDED]Public exposure of operator UI — should be Wireguard-only or SSO-protected.
11. Impact if it goes down¶
Loss of visibility, not loss of service. But: degraded incident response.
12. Owner & on-call¶
[INFO NEEDED]
13. References & links¶
- Public URL: https://monitor.448.global
- Vendor docs: https://beszel.dev
- Pairs with: Gotify for alert delivery
- Domain: see domains.md