Puvendhan opened a new issue, #7766:
URL: https://github.com/apache/incubator-devlake/issues/7766

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   Hi Everyone, The PagerDuty connection is pulling incident data but this is 
not being reflected in metrics.
   Devlake is running on v1.0.0-beta11.
   The PagerDuty connection is pulling incident data but this is not being 
reflected in metrics. Where configured Jira data is acting as an incident count 
but from PagerDuty it is possible to see incidents in DevLake but these are not 
impacting the counts.
   
   ### What do you expect to happen
   
   Hi Everyone, The PagerDuty connection is pulling incident data but this is 
not being reflected in metrics.
   Devlake is running on v1.0.0-beta11.
   The PagerDuty connection is pulling incident data but this is not being 
reflected in metrics. Where configured Jira data is acting as an incident count 
but from PagerDuty it is possible to see incidents in DevLake but these are not 
impacting the counts.
   
   ### How to reproduce
   
   Hi Everyone, I deployed the devlake and added pagerduty data connection.
   Added the dashboards in grafana. 
   
   ### Anything else
   
   Hi Everyone, The PagerDuty connection is pulling incident data but this is 
not being reflected in metrics.
   Devlake is running on v1.0.0-beta11.
   The PagerDuty connection is pulling incident data but this is not being 
reflected in metrics. Where configured Jira data is acting as an incident count 
but from PagerDuty it is possible to see incidents in DevLake but these are not 
impacting the counts.
   
   ### Version
   
   v1.0.0-beta11
   
   ### Are you willing to submit PR?
   
   - [ ] 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]

Reply via email to