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

   ### 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
   
   DORA has introduced a patch to the definition of CFR in its 2023 report:
   > For the primary application or
   service you work on, how long does it generally take
   to restore service **after a change to production or
   release to users results in degraded service (for
   example, lead to service impairment or service
   outage) and subsequently require remediation
   (for example, require a hotfix, rollback, fix
   forward, or patch)**
   
   The definition has changed to only consider those downtimes as incidents, 
caused by a deployment. That is for example, if we have two consecutive 
deployments with 12 hours between them, and some incidents happened after 6 
hours after the first deployment, we shouldn't count that incident as a change 
that led to a failure.
   
   However, in the DORA plugin in Devlake, we match any incident with the 
latest deployment before it, ignoring the time length between them. This leads 
to imprecise metrics.
   
   ### What do you expect to happen
   
   I think a preferred solution is to configure the time length between a 
deployment and an incident, which we consider as a software fault. That is, 
having some variable in code that is configurable and user can configure it 
based on their needs.
   
   ### How to reproduce
   
   Create one deployment and an incident far after it, that incident will match 
the deployment.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   v1.0.1@e061ef2
   
   ### Are you willing to submit PR?
   
   - [X] 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: dev-unsubscr...@devlake.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to