Skip to content

[Feature][Plugin] incident.io integration #9018

Description

@serroba

Search before asking

  • I had searched in the issues and found no similar feature requirement.

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?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions