Quick answer: Connect PagerDuty (an Events API v2 integration key) or Opsgenie (an API integration key) under Integrate > Integrations in Bugnet and set the priority filter to critical only. Each critical bug opens one incident or alert keyed to the bug, so a crash hit by thousands of players pages once; resolving, closing or won't-fixing the bug resolves it, and reopening triggers it again. US and EU regions are supported, on every Bugnet plan.
Live games have outages that are not server outages: a patch that crashes on launch for every player with a certain GPU, a save migration that corrupts progress, a store update that breaks login. Those should wake someone up. Ordinary bug noise should not. Here is how to route only the bugs that matter to your on-call rotation.
How it works
- One incident per bug. Each bug is one PagerDuty incident or Opsgenie alert, keyed by the bug. Repeat crashes stack onto the same bug in Bugnet, so they never page twice.
- It follows the bug. Resolving, closing or marking the bug won't fix resolves the incident; reopening the bug triggers it again.
- Nothing else is sent. No comments, no minor edits, no digests. Only the page.
- Severity maps across. PagerDuty: critical → critical, high → error, medium → warning, low → info. Opsgenie: critical → P1 through low → P4.
Setting up PagerDuty
- On the PagerDuty service that should be paged, add an Events API V2 integration and copy its integration key.
- In Bugnet, open Integrate > Integrations > PagerDuty, choose your region (US or EU), paste the key and set the priority filter. Critical only is the suggested default.
- Choose Connect, then Send test: Bugnet raises a test event and resolves it straight away.
Setting up Opsgenie
- In Opsgenie, add an API integration with create and update access and copy its API key.
- In Bugnet, open Integrate > Integrations > Opsgenie, choose US or EU, paste the key and set the priority filter.
- Connect and send a test alert.
What should page someone?
The integration pages on priority, so the quality of your paging depends on how bugs get their priority:
- Auto-captured fatal crashes arrive as critical in several SDKs (for example Godot fatal errors, Pygame uncaught exceptions and Unreal fatal errors), so a crash-on-launch after a patch pages immediately.
- Player reports keep the priority the player chose. If they leave category and priority at the defaults, Bugnet infers both from the text, and a report that reads like a crash is filed as a critical crash. That catches crashes the SDK could not, but it also means a critical-only filter can page on a player's description. Because repeat reports stack onto one bug, a wave of identical reports still pages only once.
- Adjust deliberately. Lower the priority of a bug that does not need a human tonight, and raise a reported bug to critical when it blocks progress for many players.
Pair paging with alert rules (checked hourly, they email your team when new reports or the crash rate cross a threshold you set) and with the crash-free rate per version on the Release Health tab, and you will know about a broken patch before the reviews do.
On-call basics for small teams
You do not need a large rotation to benefit: two people alternating weeks, a clear rule for what counts as critical, and a runbook for rolling back a patch cover most indie live games. Read how to set up an on-call rotation for your game for more. Team chat alerts belong elsewhere: see Microsoft Teams alerts or Discord notifications.
Create a free Bugnet project to connect PagerDuty or Opsgenie; both are included on every plan.
Frequently asked questions
Can I page on-call engineers when my game crashes?
Yes. Connect PagerDuty or Opsgenie in Bugnet with a critical-only priority filter, and each critical bug opens one incident or alert that resolves itself when the bug is fixed.
Will a crash hit by thousands of players page thousands of times?
No. Each bug is one incident keyed by the bug, and repeat crashes stack onto the same bug, so it pages once.
How do Bugnet priorities map to PagerDuty severities?
Critical maps to critical, high to error, medium to warning and low to info.
How do Bugnet priorities map to Opsgenie?
Critical maps to P1 through low to P4.
Do PagerDuty and Opsgenie need a paid Bugnet plan?
No. Both integrations are available on every Bugnet plan, including the free plan.
Page on what breaks the game for many players. Everything else can wait until morning.