Insights Events (a subset of Lifecycle Events) are what the CTO.ai platform collects to measure the effectiveness of your DevOps practices—how often you deploy, the length of your development cycle, and how often your deployments fail—with DORA Metrics. Insights Events represent your team’s activity on the CTO.ai platform and integrated development tools, such as GitHub.
We classify Insights Events into two types: Deployment Events and Change Events. Generally speaking, Change Events represent activity within a codebase (such as the stages of the development cycle within your team’s GitHub repository), while Deployment Events represent activity on your infrastructure (such as the process that deploys your code to your application environment).
As a team grows, it becomes more difﬁcult to measure the effectiveness of processes. Likewise, as infrastructure complexity grows, “reliability” becomes a complicated concept on its own, and consistently measuring infrastructure performance in this way is difﬁcult. Insights Events serve as data points to assess how your processes enable developer productivity and infrastructure reliability.
We use Insights Events to calculate DORA Metrics, a research-backed set of indicators for measuring the effectiveness of your DevOps processes. The four metrics we derive from Insights Events are defined in this table:
|Average number of deployments per day.
|Change Lead Time
|Average amount of time required for a commit to be deployed.
|Change Failure Rate
|Percentage of deployments that fail to complete successfully.
|Failed Deployment Recovery Time
|Average amount of time required to roll back a change.
Our DORA Metrics page has a deeper explanation of how these metrics are calculated and the potential problems they can surface.