dosubot[bot] commented on issue #7766: URL: https://github.com/apache/incubator-devlake/issues/7766#issuecomment-2238738303
<!-- Answer --> The issue you're experiencing with PagerDuty incident data not being reflected in the metrics is likely due to how the incidents are classified and processed. Here are a few steps to ensure proper configuration: 1. **Classification of Incidents**: Ensure that the incidents are correctly classified and stored in the `issues` table with the type set to 'INCIDENT'. The incidents are extracted from the `issues` table in MySQL with the condition `type = 'INCIDENT'`. 2. **PagerDuty Plugin Invocation**: As of v0.15.x, the `PagerDuty` plugin can only be invoked through the DevLake API, and its support in Config-UI is still a work in progress. Make sure you have correctly set up the PagerDuty data connection and created a blueprint to collect data from PagerDuty using the DevLake API. 3. **Data Processing**: If the data is visible in DevLake but not in the metrics, it is likely that the data is not being correctly processed or classified for the metrics computation. Verify the data flow and ensure that the incidents are being processed correctly. For more detailed debugging, you can use the `TestIncidentDataFlow` function in the `incident_test.go` file, which demonstrates the use of the `e2ehelper.DataFlowTester` to trace the data flow from PagerDuty to the metrics computation. This tool allows you to import raw data into tables, verify the extraction and transformation of data, and compare the results with expected CSV snapshots <sup>[[1]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v0.15/Plugins/pagerduty.md)</sup><sup>[[2]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v0.16/Plugins/pagerduty.md)</sup><sup>[[3]](https://github.com/apache/incubator-devlake/blob/main/backend/plugins/pagerduty/e2e/incident_test.go)</sup>. If you need further assistance, please provide more details about your setup and any logs that might help diagnose the issue. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* -- 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
