Event webhooks: game_server.started and game_server.stopped

Sent for every Fragnet game server seen turned on or off, whatever the notification switch says, with the server, game, account and, when a power signal sent from here caused it, which signal and who sent it.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5.5 committed 2026-11-14 22:59:40 +01:00
1 parent 2986734196
commit 25183c0320
10 files changed
+127 -9

No files matched your search

+5
View File
@@ -51,6 +51,10 @@ Administrators: **Settings → API and webhooks → Event webhooks → Add a web
| `alert.resolved` | A problem ends. |
| `maintenance.started` | A maintenance window begins — by hand, in bulk, from a recurring schedule, or mirrored from Uptime Kuma. |
| `maintenance.ended` | A maintenance window finishes, on its own or ended early. |
| `game_server.started` | A game server (Infrastructure → Game servers) is seen turned on — starting or running after being off. |
| `game_server.stopped` | A game server is seen turned off — stopping or offline after being on. |
**Game servers.** The accounts are read every five minutes, so `at` is to the nearest five minutes and a server that is switched off and on again between two reads is not seen at all. *Starting* counts as on and *stopping* as off, so a start is announced once, when it begins, not again when it has finished. A server read for the first time, one being installed or moved, and one whose state is unknown are not announced. Unlike the chat notification, these are **not** held back by the *Game servers turned on or off* switch in Settings → Notifications: a machine hears every change. A receiver that itself sent the power signal can tell its own doing by `signal`/`by`.
**What counts as an alert here.** `alert.opened` and `alert.resolved` are sent for the alerts that go through the health-style bookkeeping — server offline, disks, failed services, SMART and ZFS problems, new
ports, network devices offline, your own [alert rules](MONITORING.md#your-own-alert-rules), endpoint checks, heartbeats, and automation failures — on the **same terms as a notification**: a problem
@@ -92,6 +96,7 @@ X-HLM-Signature: sha256=9f2c… (only if the webhook
| `alert.resolved` | `alert.key`, `alert.message` (what it said when it opened) |
| `maintenance.started` | `window`: `id`, `targetType` (`server`, `integration`, `dns_provider`, `device`), `targetId`, `targetName`, `reason`, `startedAt`, `endsAt`, `source` (`null` for one started by hand, `schedule:…` for a recurring one, `kuma:…` for one mirrored from Uptime Kuma) |
| `maintenance.ended` | the same `window`, plus `endedAt` — one ended early has its `endsAt` brought forward |
| `game_server.started` / `game_server.stopped` | `gameServer`: `id` (the panel's id), `name`, `game`, `integrationId`, `integrationName`, `on` (`true` for started), `at` (when the read saw it), `signal` (`start`, `stop`, `restart` or `kill` when the change followed a power signal sent from this app, else `null`) and `by` (who sent that signal, else `null`) |
| `test` | `message` |
A captured test message, as a receiver sees it (headers lower-cased by the receiving server):