Fix Frigate metrics scraping and rebuild Grafana dashboard
Frigate moved from minikube to ringtail but the Prometheus scrape target still pointed at the old cluster-internal DNS. Route via Caddy on indri (nvr.ops.eblu.me) which already proxies to ringtail. Rebuild the Grafana dashboard for Frigate 0.17 metrics: add GPU usage, GPU memory, device temperature, skipped FPS, and detection event rate panels. Update stale metric names (service_info → uptime_seconds, detection_total_fps → detection_fps). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
dda7d719b3
commit
51875b24b3
3 changed files with 258 additions and 106 deletions
1
docs/changelog.d/fix-frigate-metrics-dashboard.infra.md
Normal file
1
docs/changelog.d/fix-frigate-metrics-dashboard.infra.md
Normal file
|
|
@ -0,0 +1 @@
|
|||
Fix Frigate Prometheus scrape target to route via Caddy (nvr.ops.eblu.me) after migration to ringtail, and rebuild Grafana dashboard with updated Frigate 0.17 metrics (GPU usage, temperature, skipped FPS, detection events).
|
||||
Loading…
Add table
Add a link
Reference in a new issue