Faros CE comes with 2 DORA dashboards:
The former leverages a much bigger slice of the underlying schema (cicd_deployment, ims_incident and compute_application). Its metrics align closely with the state of DevOps reports. It requires however a source for those entities to be configured.
Deployments can be ingested into Faros CE through:
- the Harness Source
- CD Events
- Data Transforms with dbt that transform the cicd_Build extracted from GitHub, GitLab, Bitbucket, Jenkins or Buildkite that are actually Deployments into cicd_Deployment entities
Incident can be ingested into Faros CE through:
- the PagerDuty Source , Statuspage Source or VictorOps Source
- Data Transforms with dbt that transform a tms_Task extracted from Jira, GitHub, GitLab or Bitbucket that are actually Incidents into ims_Incident entities
Applications are automatically created based on what Deployments and Incidents refer to when those datums are ingested. That means that unless the dashboard is modified, those references need have the same names: if your incidents refer to a
foobar service, your deployments need to refer to
foobar as well for the Change Failure Rate to be accurate.
The DORA - Releases and Bugs dashboard on the other hand leverages cicd_Release and tms_Task that contain the word 'bug'. All of those entities are extracted by our GitHub, GitLab and Bitbucket sources, which means that this dashboard will not require any additional sources to be ingested to light up. The metrics are broken down by repository. Note that the metrics are not as faithful to the industry benchmark definition however.
- PR Review Time: time between the PR was open and its first Review
- PR Merge Time: time between a PR first Review and its merge
- [Releases only] Wait time: time between a PR merged and the next Release (chronologically)
- [Deployments only] Time in Dev: time between a PR merged and the next deployment of an application tied to the repository in dev chronologically (for more information, see here)
- [Deployments only] Time in QA: similar to above
- [Deployments only] Time in Staging: similar to above
As you can see, Faros CE assumes deployments and releases are made from a single main line.
Change Failure Rate:
Computed as the ratio over a time period of Incidents to Deployments, or Bugs (tasks that contain the string
bug in their title) to Releases. The time period is either the one specified by the dashboard filter, or a week (for the middle chart).
Updated 3 months ago