Pages that mean something, at 3am.
An alert that fires for every known warning trains you to ignore it. bughq tells you when an issue is genuinely new or spiking, and stays quiet for the errors you have already seen and handled.
This week, by alert reasonSample data
How on-call teams use it
01
Route alerts to the channel you watch
Send new and spiking issues to the on-call channel or pager. Known and resolved issues stay off the rotation until they come back.
02
Triage by impact, not by timestamp
Issues sort by affected-user count and rate, so the fault hitting the most people is at the top, not buried in a scrolling log.
03
Hand off with a clear trail
Each issue keeps its history, release, and status, so the next shift picks up exactly where the last one left off.
Signal
Alerts for new and spiking issues, silence for the known and handled.
By impact
Sort a queue by affected users and rate, not by raw event time.
Clean handoff
Status, history, and release travel with every issue across shifts.