feat(incidentio): add incident.io data source plugin - #9023
Merged
Conversation
Adds a datasource plugin for incident.io (https://incident.io), an incident management platform, following the structure of the rootly plugin: - Connection with Bearer-token auth against https://api.incident.io/ - Scopes are incident types (v1/incident_types); remote-scope listing included - Collects incidents (v2/incidents, cursor pagination), extracts to _tool_incidentio_* tables (test/tutorial-mode incidents excluded), converts to ticket domain issues with type INCIDENT for DORA CFR/MTTR correlation - Timestamps mapped from incident_timestamp_values: 'Declared at' drives the created date, 'Resolved at' (falling back to 'Closed at') the resolution date; retrospective incidents keep their resolution date even when it precedes the declaration - Unit tests, e2e snapshot tests, config-ui registration, Grafana dashboard Validated end-to-end against a production incident.io workspace via the in-memory test server (50 incidents, field-level match with reference data). Closes apache#9018 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
klesh
approved these changes
Jul 30, 2026
klesh
left a comment
klesh
left a comment
Contributor
There was a problem hiding this comment.
LGTM.
Thanks for your contribution.
klesh
pushed a commit
to apache/devlake-website
that referenced
this pull request
Jul 31, 2026
Companion to apache/devlake#9023 (feat(incidentio): add incident.io data source plugin): adds the Configuration/Incidentio page referenced by the plugin's config-ui DOC_URL, and lists incident.io in the supported data sources table. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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
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.
Summary
Adds a datasource plugin for incident.io, an incident management platform (same category as the existing PagerDuty/Opsgenie/Rootly plugins). Closes #9018.
https://api.incident.io/v1/incident_types), with remote-scope listingv2/incidents(cursor pagination);test/tutorialmode incidents excluded at extractionINCIDENT, feeding the existing DORA incident↔deployment correlation;Declared at→ created date,Resolved at(fallbackClosed at) → resolution date; retrospective incidents keep their resolution date even when it precedes declarationTesting
Beyond the unit/e2e suites, the plugin was validated end-to-end against a production incident.io workspace using the in-memory test server from
DevelopmentManual.md: 50 real incidents collected, extracted, and converted with field-level verification against independently ingested reference data. That testing surfaced (and this PR includes fixes for) the v1-vs-v2incident_typesendpoint and the retrospective-incident timestamp ordering.Other information
Docs for
Configuration/Incidentiowill need a companion PR to the website repo — happy to follow up with it.