eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions
blumeops/docs/how-to/alerts/runbook-frigate-camera-down.md
Erich Blume 2fa536e547 C2(deploy-infra-alerting): impl add textfile staleness and Frigate alerts 
- TextfileStale: fires when a .prom textfile on indri hasn't been
  updated in 1 hour (node_textfile_mtime_seconds). Covers borgmatic,
  zot, minikube, jellyfin exporters.
- FrigateCameraDown: fires when frigate_camera_fps drops to 0 for 5m.
- Add runbooks for both alerts.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-22 13:43:16 -07:00

1.2 KiB
Raw Blame History

title modified tags
Runbook: Frigate Camera Down 2026-03-22
how-to
alerting
runbook

Runbook: Frigate Camera Down

Alert name: FrigateCameraDown

A Frigate camera has reported 0 FPS for 5+ minutes, meaning the camera feed is not being received.

Diagnostic Steps

  1. Check Frigate UI — https://nvr.ops.eblu.me — look at the camera thumbnail and status
  2. Check Frigate API stats: 
    curl -s https://nvr.ops.eblu.me/api/stats | python3 -m json.tool
  3. Check Frigate pod logs on ringtail: 
    kubectl logs -n frigate -l app=frigate --context=k3s-ringtail --tail=30
  4. Check the camera itself — verify it's powered on and network-connected. Try accessing the RTSP stream directly.

Common Causes

  • Camera offline — power outage, network issue, or camera crash
  • NFS mount lost — Frigate storage on sifaka; if the NFS mount drops, recording stops and FPS may drop
  • Frigate pod restart — during restart, camera FPS briefly drops to 0
  • RTSP stream timeout — camera firmware issue; power cycle the camera

Related