Add incident.io alert provider - #1353
Merged
Merged
Conversation
Add the incidentio Provider type for incident.io. Events are posted to an HTTP alert source endpoint as alert events, authenticated with a bearer token. Error events are sent with status firing, all other severities with status resolved, using the involved object UID as the deduplication key (same as the PagerDuty provider) so that recovery events automatically resolve the alert fired for the same object, and objects with the same kind/namespace/name on different clusters never share a key. Progressing events are skipped, matching the PagerDuty provider behavior. Assisted-by: Claude Code/claude-fable-5 Signed-off-by: Chose Carreras <xchose@gmail.com>
xchose
force-pushed
the
incidentio-provider
branch
from
July 26, 2026 17:19
7052fb9 to
5119753
Compare
stefanprodan
added
enhancement
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1124.
Adds the
incidentioProvider type posting alert events to an incident.io HTTP alert source (bearer-token auth,202 Acceptedresponse).Design decisions
errorevents are sent with statusfiring, all other severities with statusresolved— the same semantics as the PagerDuty provider, enabling automatic alert resolution in incident.io.<kind>/<namespace>/<name>) would collide across clusters reporting to the same alert source (every cluster firesKustomization/flux-system/flux-system), letting an info event from one cluster resolve another cluster's alert. Changed after review feedback.Progressingevents are skipped, matching the PagerDuty provider behavior.eventSeverity: erroron an Alert disables auto-resolution (info events must flow for recovery to be delivered).Testing
deduplication_key, and a second object gets its own UID key (no sharing). Screenshots in the review thread show the alert detail with the UID key.Alert fired for the broken GitRepository branch:
Automatically resolved after the recovery event (same deduplication key):
Alert detail with event message, deduplication key and firing→resolved timeline:
Step-by-step testing procedure on a kind cluster:
INCIDENTIO_E2E_REPORT.md
🤖 Generated with Claude Code