stigi-work opened a new pull request, #9406: URL: https://github.com/apache/devlake/pull/9406
### Summary Adds a data source plugin for [Datadog Incident Management](https://docs.datadoghq.com/service_management/incident_management/). It is in the same category as the PagerDuty, Opsgenie, Rootly and incident.io plugins, and it feeds the existing DORA incident metrics. - **Connection:** API key and application key (`DD-API-KEY` / `DD-APPLICATION-KEY`). The endpoint is configurable for each Datadog site (US1, EU1, …). A separate web URL builds the incident links. - **Scopes:** incident types (`/api/v2/incidents/config/types`), with remote-scope listing. - **Collection:** incidents from `/api/v2/incidents` with `page[size]`/`page[offset]` pagination and `include=users` for the commander. - **Extraction:** test incidents (`is_test`) are skipped. - **Conversion to the ticket domain:** - `issues` with type `INCIDENT`, plus `boards` and `board_issues` for each incident type. - `issue_labels` from select-type custom fields, written as `field:value`. - `issue_assignees` from the incident commander. - `lead_time_minutes` uses Datadog's `time_to_repair` and falls back to created → resolved. A zero value or a negative duration does not count as an instant restore. - **Scope config:** `componentField` maps a custom field (for example `services`) to `issues.component`. The optional `severityField` replaces the native SEV severity with a custom field. - **config-ui:** connection form, scope selection, transformation form and a placeholder icon. The icon is not the Datadog logo, which is a trademark. Closes #9124 ### Tests - Unit tests for the collector, extractor, converter and incident-type extractor. - An e2e data-flow test with snapshot tables for `issues`, `boards`, `board_issues`, `issue_labels` and `issue_assignees`. - We have run the plugin since September 2026 against a production Datadog org in our self-hosted DevLake. The DORA dashboards read its incidents next to CircleCI, GitHub and Linear. <details> <summary>Notes for reviewers</summary> - The plugin has two migration scripts (`20260907` init and `20261103` commander columns), not one init script. Our deployment already applied both, so I did not merge them. - The `docLink` is empty until a Datadog page exists on the DevLake website. I can open that docs PR, and a Grafana dashboard, as follow-ups. - I could not add the `pr-type/feature-development` label myself. A maintainer has to add it. </details> 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
