Files
serverAppConfigs/serverAppConfigs-docs/Infrastructure/Node-Exporter.md
T
Frank 93d1181fee docs: OKF v0.1 compliance pass + fact-check + 3 research briefs
- Migrate all 127 non-reserved docs to OKF v0.1 frontmatter (type/description/tags/timestamp); fix 13 YAML issues, 2 duplicate-FM blocks, strip reserved-page FM
- Restructure log.md to OKF (## YYYY-MM-DD, newest-first)
- Fact-check against scripts/AGENTS.md ground truth: fix 6 false 'Active' banners on retired runbooks, 96->114 GiB GTT, deployment.md vs deploy-plan.py/deploy-remote.sh, Deployment Flow frank-medium=Quadlet, Calibre 9.9.0->9.15.0 + CVE-2025-7404 conflation, Copyparty v1.20.24, RomM 5.3.0 breaking change
- Move *arr docs to new FrankBook-Pro/ section (git mv, link-safe)
- Write active runbook bodies from ground truth (frank-large, frank-small)
- Add 3 research briefs + HTML report: Local TTS and Voice Cloning, AI Job Search and Resume Tools, Most Popular Self-Hosted AI Apps (Jun-Sep 2026)
- Add upstream-version rows to ComfyUI/OpenWebUI/Hermes app docs
- All 336 tests pass; 136 pages, 0 unresolved wikilinks
2026-09-22 02:09:41 -07:00

2.6 KiB

type, description, tags, timestamp
type description tags timestamp
reference Node-Exporter exposes host metrics (CPU, RAM, disk, network) to Prometheus.
infrastructure
2026-09-11

Node-Exporter

Node-Exporter exposes host metrics (CPU, RAM, disk, network) to Prometheus. One instance runs per host, each in its own container.

Hosts: Dankclaw (unit) + Dankserver (compose service) — Docs: https://prometheus.io/docs/guides/node-exporter

Facts

Item Value
Image prom/node-exporter:latest
Listen addresses 127.0.0.1:9100 and 192.168.0.143:9100 (Dankclaw)
Network Network=host + --pid=host
Unit dankclaw/observability/quadlet/node-exporter.container → node-exporter.service
Paths --path.procfs=/host/proc --path.sysfs=/host/sys --path.rootfs=/rootfs
Auth none — it is an unauthenticated metrics endpoint by design

Why it is the one LAN listener

Every other observability service publishes on loopback. This one cannot:

  • Prometheus runs in a container on the dankclaw_default network and cannot reach the host's loopback address, so it needs the host's LAN IP; shared/prometheus/prometheus.yml scrapes 192.168.0.143:9100 under the node-dankclaw job.
  • The homepage status timer runs on the host and probes 127.0.0.1:9100.

The unit therefore binds exactly those two addresses with two --web.listen-address flags — never the wildcard. It has no authentication, so it is never vhosted and never published beyond the LAN.

Mounts

Container path Host path
/host/proc /proc (read-only)
/host/sys /sys (read-only)
/rootfs / (read-only)

The mount paths and the --path.* flags are a pair: changing one without the other gives an exporter that starts cleanly and reports nothing.

Prometheus Targets

Host Target
Dankclaw 192.168.0.143:9100
Dankserver 192.168.0.235:9100

The scrape jobs live in shared/prometheus/prometheus.yml; see Prometheus. The tests/observability_quadlet.bats seam pins the Dankclaw address to this unit's listen address so the two cannot drift apart.

Gotchas

  • Host networking is required (or a published port); the deploy's health wait probes 127.0.0.1:9100/metrics.
  • The /proc, /sys and root mounts must be read-only.
  • Each host's instance reflects only its own host; do not try to share one.
  • Collectors are the image defaults — no per-collector tuning and no textfile collector for custom metrics.

See Also