Files

T

Frank 90c4ac69a7 Doc audit: fix all broken links + correct stale facts across the KB

Fanned out 5 read-only doc-auditor subagents (one per service group) that
fact-checked the knowledge base against the live system + repo config,
researched official setup docs online, and verified progress. Applied:
- All 34 broken links fixed (real pages / external URLs / correct relative
  paths); 0 broken links remain. No .AGENTTRASH links (the 4 mentions are
  accurate descriptive text, not links).
- Fact-check fixes: Readarr retired (May 2026), Radarr v4->v6, Calibre
  9.2.1 live, Calibre-Web 0.6.25 live, Copyparty v1.20.21, LLM index
  ncmoe 38 + 786432 ctx, frank-default-small active (not frank-pp-worker),
  Hermes/SearXNG/Grafana hostnames, Loki/Alloy local images, Observability
  diagram (Promtail->Alloy), VLLM retired note, DFlash status, benchmark
  live-drift notes, Homepage test count 116.

2026-08-24 01:10:44 -07:00

1.4 KiB

Raw Blame History

Grafana

Grafana visualizes the metrics that Prometheus collects from every service. It runs on Dankclaw and is reachable at grafana.franksdank.cloud (via Caddy, with basicauth).

Host: Dankclaw — Hostname: grafana.franksdank.cloud — Port: 3002 (internal) — Docs: https://grafana.com/docs

Facts

Item	Value
Image	`docker.io/grafana/grafana:latest`
Port	3002 (host) → 3000 (container)
Data volume	dashboards, users, datasource config
Datasource	Prometheus (on the same host)
Provisioning	dashboards in `/etc/grafana/provisioning/dashboards`

Configuration

environment:
  GF_SECURITY_ADMIN_USER: "${GRAFANA_ADMIN_USER}"
  GF_SECURITY_ADMIN_PASSWORD: "${GRAFANA_ADMIN_PASSWORD}"
  GF_SERVER_ROOT_URL: "https://grafana.franksdank.cloud"
volumes:
  - /opt/grafana/data:/var/lib/grafana
  - /opt/grafana/provisioning:/etc/grafana/provisioning:ro

Datasource

Point Grafana at the Prometheus service by name (http://prometheus:9090) on the shared podman network.

Healthcheck

Grafana responds on /api/health with 200 and "database":"ok".

Gotchas

Change the default admin credentials at first boot (env or UI).
Dashboards provisioned as YAML survive container recreation; UI-created ones live in the data volume — back it up.

1.4 KiB Raw Blame History