KNEL/KNELKumaGlpiBridge
9
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
3 Commits 6 Branches 0 Tags
ic-builder/up-solve-search
T
Clone
Open with VS Code Open with VSCodium Open with Intellij IDEA
Download ZIP Download TAR.GZ Download BUNDLE
ic-builder de9b9c4a35
ci / vet (pull_request) Successful in 47s
Details
UP events solve open tickets even after bridge restarts 
In-memory dedupe resets on pod restart; recovery then no-ops and leaves
stale open tickets. UP now falls back to a GLPI search for an unsolved
ticket for that monitor.
Ticket: https://projects.knownelement.com/issues/824
2026-09-06 13:09:34 -05:00
.gitea/workflows
CI: install nodejs before checkout; recovery followup via ITILFollowup
2026-09-06 13:00:55 -05:00
cmd/bridge
UP events solve open tickets even after bridge restarts
2026-09-06 13:09:34 -05:00
bridge
UP events solve open tickets even after bridge restarts
2026-09-06 13:09:34 -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.

Reference in New Issue View Git Blame Copy Permalink
S
Description
Kuma-to-GLPI incident bridge: webhook receiver that opens GLPI tickets for Uptime Kuma outages. Flux-deployed on pfv-k8s.
Readme
30 MiB
Languages
Go 95.9%
Dockerfile 4.1%