T

ci / vet (pull_request) Successful in 59s

Details

fix: Kuma heartbeat status enum — 0 is DOWN, not 2

Live-path debug found the bridge silently ignored real Kuma down-events:
Kuma heartbeat.status is 0=down/1=up/2=pending, not the webhook-doc
guess used earlier. DOWN now keyed on 0.
Ticket: https://projects.knownelement.com/issues/824

2026-09-06 15:29:48 -05:00

.gitea/workflows

CI: install nodejs before checkout; recovery followup via ITILFollowup

2026-09-06 13:00:55 -05:00

cmd/bridge

fix: Kuma heartbeat status enum — 0 is DOWN, not 2

2026-09-06 15:29:48 -05:00

bridge

fix: Kuma heartbeat status enum — 0 is DOWN, not 2

2026-09-06 15:29:48 -05:00

Dockerfile

CI: install nodejs before checkout; recovery followup via ITILFollowup

2026-09-06 13:00:55 -05:00

go.mod

kuma-glpi-bridge: webhook receiver opening GLPI incident tickets

2026-09-06 12:30:48 -05:00

README.md

kuma-glpi-bridge: webhook receiver opening GLPI incident tickets

2026-09-06 12:30:48 -05:00

README.md

KNELKumaGlpiBridge

Uptime Kuma -> GLPI incident bridge. Kuma webhook POSTs land on /webhook; DOWN opens a GLPI incident ticket (deduped per monitor), UP posts a recovery followup and solves the ticket with evidence.

Deployed on pfv-k8s via flux (NodePort 30801). GLPI tokens come from a k8s Secret created imperatively — never in git.

Redmine: https://projects.knownelement.com/issues/824
Discourse: incident-response category (outage flow)