[Feature][PagerDuty] Add Scope Config for PagerDuty Connection #8367
Description
Search before asking
- I had searched in the issues and found no similar feature requirement.
Use case
As a member of an Engineering Enablement team supporting DORA metrics, I want to integrate with the out-of-the-box PagerDuty data connections with an option to set a scope config, so that I can filter for specific incident data on a PagerDuty service for a DevLake project.
Description
The problem I'm experiencing with the current PagerDuty connection is that it collects all incidents for a given PagerDuty service and doesn't allow for a scope config to filter out incidents or alerts that are not relevant to the project. This leads to inflated Change Failure Rate in our DORA metrics.
For additional context, at my company, users can open lower severity incidents in PagerDuty to facilitate time sensitive work to be completed by an engineering team. Because of this, it would be beneficial to include and/or exclude certain priority and/or severity statuses in a scope config. Alternatively, we're looking into utilizing webhooks to get the filtered data from a ServiceNow API, which isn't ideal.
Additional context can be found in #8362
Related issues
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct