dosubot[bot] commented on issue #8362: URL: https://github.com/apache/incubator-devlake/issues/8362#issuecomment-2752577201
<!-- Answer --> The current implementation of the PagerDuty data connection in DevLake does not include a scope config, which means it lacks built-in data filtering capabilities. This can indeed lead to challenges like the one you're experiencing, where all incidents, regardless of priority, are ingested into DevLake, potentially skewing your stability metrics. The specific reasons for the removal or incomplete implementation of the scope config in PagerDuty are not documented in the available resources, including PR 5326 and PR 5369 <sup>[[1]](https://github.com/apache/incubator-devlake/blob/main/config-ui/src/plugins/register/pagerduty/config.tsx)</sup><sup>[[2]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v0.15/Plugins/pagerduty.md)</sup>. However, the current setup does allow for some configuration through the API, such as setting a `start_date` for incident collection, but it does not provide granular filtering based on incident priority or other criteria <sup>[[1]](https://github.com/apache/incubator-devlake/blob/main/config-ui/src/plugins/register/pagerduty/config.tsx)</sup>. If data filtering is crucial for your use case, you might consider proposing a feature request to reintroduce or implement a scope config for PagerDuty. This could help address the issue of filtering out lower-priority incidents directly within DevLake, rather than relying on external solutions like webhooks. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/d321e8f2-54f9-4d0e-b90a-98d35047aa0a?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/d321e8f2-54f9-4d0e-b90a-98d35047aa0a?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/d321e8f2-54f9-4d0e-b90a-98d35047aa0a?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/d321e8f2-54f9-4d0e-b90a-98d35047aa0a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d321e8f2-54f9-4d0e-b90a-98d35047aa0a?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/d321e8f2-54f9-4d0e-b90a-98d35047aa0a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/d321e8f2-54f9-4d0e-b90a-98d35047aa0a?feedback_type=other)</sup> -- 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: dev-unsubscr...@devlake.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
