Search before asking
Use case
As an engineering leader using DevLake for DORA metrics, I want to ingest incidents from incident.io so that change failure rate and failed-deployment recovery time can be computed from our real incident register — with its operationally accurate declared/resolved timestamps — rather than from issue-tracker labels or manual webhooks.
Description
incident.io is a widely adopted incident management platform (Slack-native, similar space to PagerDuty/Opsgenie/Rootly, which DevLake already supports). A plugin would:
- Connection: single API key (Bearer), endpoint
https://api.incident.io/
- Scope: incident types (
GET /v2/incident_types), analogous to the service-scoped incident plugins
- Entities: incidents (
GET /v2/incidents, cursor pagination) → domain-layer issues/incidents with type INCIDENT; severity, status, and the incident_timestamp_values (Declared/Resolved) mapped to created/resolution dates; test/tutorial mode incidents excluded
- This feeds the existing DORA incident-to-deployment correlation with no framework changes
We have validated the field mapping against a production incident.io workspace via the generic webhook plugin, and have a working local prototype modeled on the rootly plugin.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
Search before asking
Use case
As an engineering leader using DevLake for DORA metrics, I want to ingest incidents from incident.io so that change failure rate and failed-deployment recovery time can be computed from our real incident register — with its operationally accurate declared/resolved timestamps — rather than from issue-tracker labels or manual webhooks.
Description
incident.io is a widely adopted incident management platform (Slack-native, similar space to PagerDuty/Opsgenie/Rootly, which DevLake already supports). A plugin would:
https://api.incident.io/GET /v2/incident_types), analogous to the service-scoped incident pluginsGET /v2/incidents, cursor pagination) → domain-layer issues/incidents with type INCIDENT; severity, status, and theincident_timestamp_values(Declared/Resolved) mapped to created/resolution dates;test/tutorialmode incidents excludedWe have validated the field mapping against a production incident.io workspace via the generic webhook plugin, and have a working local prototype modeled on the rootly plugin.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct