> For the complete documentation index, see [llms.txt](https://typo.gitbook.io/typo-help-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://typo.gitbook.io/typo-help-docs/engineering-metrics/deployment-metrics/deployment-failure.md).

# Deployment - Failure

Deployment Failure represents the percentage of deployments that failed during the deployment runs in the production environment.

By integrating with your CI/CD tool, Typo tracks all your production deployments across repos & workflows as configured by you. During these runs, the total number of deployments that fail represents the Deployment Failure.\
These are identified based on the status received from your CI/CD tool.

<div align="left"><figure><img src="/files/VtAS8dmIvGWOExfsevdB" alt=""><figcaption></figcaption></figure></div>

> Benchmarking deployment failures enables the tech team to pinpoint systemic weaknesses, prioritise improvements, and streamline the deployment pipeline, ultimately enhancing system stability and minimising disruptions in service delivery.

<div align="left"><figure><img src="/files/731gTz7kum3SX8suxMBR" alt=""><figcaption></figcaption></figure></div>

### **How does measuring Deployment failure help in improving the Engineering teams' efficiency?**

1. **Identifying Weaknesses:** Tracking deployment failures helps identify patterns and root causes of failures, such as configuration errors, compatibility issues, or infrastructure problems.
2. **Prioritizing Improvements:** By understanding the frequency and impact of deployment failures, teams can prioritize improvements to processes, tools, and infrastructure to prevent future failures.
3. **Enhancing Automation:** Analyzing deployment failures can highlight opportunities for automating manual tasks, reducing human error, and improving the reliability of deployment processes.
4. **Optimizing Testing Strategies:** Insights from deployment failures can inform adjustments to testing strategies, such as expanding test coverage, implementing more robust regression testing, or enhancing integration testing.