Skip to main content

DORA @ Middleware

Middleware is designed to help engineering leaders measure and analyze the effectiveness of their teams using the DORA metrics. The DORA metrics are a set of four key values that provide insights into software delivery performance and operational efficiency. They are:

  • Deployment Frequency: The frequency of code deployments to production or an operational environment.
  • Lead Time for Changes: The time it takes for a commit to make it into production.
  • Mean Time to Restore (MTTR): The time it takes to restore service after an incident or failure.
  • Change Failure Rate (CFR): The percentage of deployments that result in failures or require remediation.

Middleware collaborated with Google to publish the 2024 DORA Report as the Gold Sponsor.

image

Middleware DORA Integrations​

image

Middleware provides a range of integrations to sync data, ensuring accurate DORA metrics calculation:

  • Code and PR Data:
    • GitHub
    • GitLab
    • Bitbucket
    • Self-hosted agent
  • Incident Data:
    • PagerDuty
    • Zenduty
    • Opsgenie
  • Deployment Data:
    • Azure DevOps
    • GitHub Actions
    • Custom deployments webhook

How Metrics Are Calculated​

Lead Time for Changes​

  • With Deployment and PR Data: The lead time of a pull request (PR) is calculated as the time from the first commit to the successful deployment in which the PR was pushed to production. This includes:
    • First Commit to PR Open Time
    • First Response Time
    • Rework Time
    • Merge Time
    • Merge to Deploy Time

You can configure workflows to sync for repository deployments or decide whether to use PR merges or actual deployments as the basis for your team’s deployment metrics.

Deployment Frequency​

  • This metric measures how frequently code changes are deployed to production.
  • Deployment frequency represents the number of successful deployments to production during the interval. It is represented in terms of daily, weekly or monthly deployments over an interval.
  • If PR merges are treated as deployments, it reflects the daily, weekly, or monthly frequency of PR merges.

Mean Time to Restore (MTTR)​

  • MTTR measures how quickly a team restores service after a failure in production.
  • The average resolution time for incidents fetched from linked services (e.g., PagerDuty, Zenduty) is used to calculate the MTTR for that interval.

Change Failure Rate (CFR)​

CFR quantifies the percentage of changes that lead to service impairment or outages in production.

  • CFR is calculated by linking incidents to deployments over a specific interval.
  • Deployments associated with incidents are considered failures.
  • CFR is the ratio of failed deployments to the total deployments in the interval.