Add VictoriaLogs for centralized journald across all hosts

control runs VictoriaLogs (:9428, 30d, mesh-scoped) with a matching
Grafana datasource. Each host ships journald via systemd's own
journald.upload to the /insert/journald endpoint -- no extra agent.
control uploads over loopback so its logs survive a mesh outage; ns1
and ns2 push over the mesh.
This commit is contained in:
Berwn
2026-06-17 16:53:52 +07:00
parent c7b0f206c8
commit d4a171640b
4 changed files with 72 additions and 7 deletions
+8 -2
View File
@@ -57,7 +57,13 @@ ns1/ns2: SOA + DNSKEY succeed on both servers over v4 and v6.
- [ ] A secondary nameserver on a different provider/network so a single-provider
outage doesn't take all authoritative DNS down (architectural — new machine)
## 5. Centralized logs
## 5. Centralized logs (done — pending deploy)
- [ ] VictoriaLogs on control to grep journald across all three hosts, pairing
VictoriaLogs on control (`:9428`, 30d retention, mesh-scoped) in
`modules/monitoring/server.nix`, plus a VictoriaLogs Grafana datasource. All
three hosts ship journald with systemd's own `services.journald.upload` to the
`/insert/journald` endpoint (`modules/monitoring/exporters.nix`) — no extra
agent. control uploads over loopback; ns1/ns2 over the mesh.
- [x] VictoriaLogs on control to grep journald across all three hosts, pairing
with the existing VictoriaMetrics setup