serroba opened a new issue, #9018: URL: https://github.com/apache/devlake/issues/9018
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) 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? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
