dncrews opened a new issue, #8876: URL: https://github.com/apache/incubator-devlake/issues/8876
### 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 Teams using Rootly for incident response should be able to collect Rootly service and incident data in Apache DevLake and analyze incident volume, resolution status, and MTTR alongside the rest of their engineering metrics. This would give Rootly users similar DevLake coverage to the existing PagerDuty and Opsgenie integrations. ### Description Add a Rootly data-source plugin to Apache DevLake. Proposed scope: - Support Rootly API token authentication. - Discover Rootly services as DevLake data scopes. - Collect Rootly services and incidents. - Map Rootly services to DevLake boards. - Map Rootly incidents to DevLake ticket issues and board issues. - Preserve incident status, severity, timestamps, creator, and responder/role users where available. - Add config-ui registration for Rootly connections and service scope selection. - Add a Rootly Grafana dashboard for incident resolution status and MTTR metrics. Data model mapping: - Rootly Service → DevLake Board - Rootly Incident → DevLake Issue - Rootly Incident Service relationship → DevLake BoardIssue - Rootly incident role users → DevLake User and IssueAssignee ### Related issues No related issue found. ### 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]
