0a8a668b05
kb/services/fleet-prometheus.md (Stack, Placement & exposure, Data, Next steps)
kb/decisions/fleet-prometheus-osobny-od-prom.md ("Why separate from the home prom")
kb/runbooks/fleet-prometheus-deploy.md (Configuration, Verify)
Wzajemne links. Tresc sekcji nietknieta; kontrola: multizbior niepustych
linii czesci == oryginal z HEAD.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
29 lines
898 B
Markdown
29 lines
898 B
Markdown
---
|
|
okf: "0.1"
|
|
type: decision
|
|
visibility: private
|
|
status: active
|
|
updated: 2026-06-24
|
|
links:
|
|
- ../services/fleet-prometheus.md
|
|
- ../runbooks/fleet-prometheus-deploy.md
|
|
---
|
|
|
|
# fleet-prometheus — dlaczego osobny od domowego `prom`
|
|
|
|
## Why separate from the home `prom`
|
|
|
|
The home `prom` on **PIHA** is LAN-only and monitors the home network. This
|
|
instance is intentionally a **distinct** Prometheus dedicated to the distributed
|
|
fleet — hence the `fleet-` naming. The split is made explicit in every series:
|
|
|
|
- `external_labels: { fleet: "homelab-codex" }`
|
|
- job names prefixed/scoped for the fleet (`prometheus`, `fleet-node`)
|
|
|
|
It also avoids two anti-patterns the home `prom` has:
|
|
|
|
- **No `:latest`** — the image is pinned to `prom/prometheus:v3.5.0` (LTS).
|
|
- **No inline secrets** — `prometheus.yml` is secret-free by contract (the home
|
|
prom embeds a plaintext HAOS token; we do not).
|
|
|