Repository navigation
[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
Activity
github-actions commentedon May 28, 2025
This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.
jeffschaper commentedon May 29, 2025
This issue is still relevant and should remain in the backlog to be assessed by the maintainers.
github-actions commentedon Jul 29, 2025
This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.
jeffschaper commentedon Aug 5, 2025
This issue is still relevant and should remain in the backlog to be assessed by the maintainers.
petkostas commentedon Aug 12, 2025
Will try to pick this up
csepulveda commentedon Oct 6, 2025
Hello @petkostas , i sent a PR about this:
#8603
Thanks!
petkostas commentedon Oct 9, 2025
Many thanks @csepulveda will try to test it most likely today!
github-actions commentedon Dec 9, 2025
This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.
github-actions commentedon Dec 16, 2025
This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.