Get on with your day, with peace of mind until Grafana needs you.
I run my own Grafana, and most days I need one answer: is anything on fire? Not the cathedral of panels I built at 1am while pretending this was a normal hobby. Just yes or no.
It is a homelab, not a $100k incident room with someone saying “customer impact” into a headset, but it is still my stuff. I want to know before my wife asks why Netflix is not working, which is how this house files support tickets.
The alert apps I tried wanted dashboards, phone-app cosplay, or Prometheus algebra. Beacon does the opposite: stays quiet, then gets impossible to miss when something actually needs me.
What Beacon does
It immediately tells you whether things are all clear, warning, critical, or unreachable. That last one matters, because a monitor that is dead but still smiling at you is not monitoring, it is interior decoration.
All clear
Warning
Critical
Unreachable
Set up in two fields
Paste your Grafana URL and a token. That’s the whole setup, no onboarding pilgrimage.
Act from the notification
Silence it, open its dashboard, or jump to the runbook, straight from the notification. Staring at it first is also allowed. We all do that.
Silent by default
A monitor that nags gets muted. Beacon follows the old Unix rule of silence: when there’s nothing surprising to say, say nothing.
If you run a serious on-call operation with escalation policies, paging schedules, and a room full of people saying “customer impact,” use a serious on-call tool. If you live inside Prometheus label matchers across twelve backends, Beacon will feel too simple by lunch. It is for one person, or a small Mac-heavy team, watching their own Grafana without turning monitoring into a second job.