> ## Documentation Index
> Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Discovering Pipeline Health including monitoring Failure Rate Duration Flaky Tests
> This guide covers monitoring pipeline health in Azure DevOps, focusing on key metrics like failure rate, duration, and flaky tests for efficient software delivery.
Welcome to this guide on **Discovering Pipeline Health in Azure DevOps**. In modern CI/CD workflows, maintaining pipeline health ensures reliable, efficient software delivery. Whether you’re preparing for the [AZ-400 exam](https://learn.microsoft.com/en-us/certifications/exams/az-400/) or optimizing your DevOps practice, monitoring key pipeline metrics is essential.
Pipeline health monitoring means regularly tracking metrics to catch issues early, reduce failures, and accelerate feedback loops.
## Key Metrics for Pipeline Health
Track these three primary metrics to understand your pipeline’s reliability, speed, and stability:
* **Failure Rate**: Percentage of runs that fail.
* **Duration**: Total time from commit to deployment.
* **Flaky Tests**: Tests with intermittent pass/fail results.
| Metric | Definition | Impact |
| ------------ | ----------------------------------- | -------------------------------------------- |
| Failure Rate | % of runs that end in error or fail | High rate → Low confidence & slower delivery |
| Duration | Time taken for pipeline execution | Long durations → Delayed feedback & releases |
| Flaky Tests | Tests that pass/fail unpredictably | Flakes → Noise in test results & maintenance |
```bash theme={null}
$ yarn test
127 passing (19m)
1 failing
1) Some test suite
Some test:
```
Review your test run logs regularly. Early detection of failures or performance issues helps maintain pipeline health.
***
## Monitoring Failure Rate
Failure rate measures how often your builds or deployments do not succeed. A low failure rate indicates a stable pipeline, whereas a consistently high failure rate signals deeper issues.
Common causes of high failure rates:
* Unstable dependencies
* Misconfigured environments
* Incomplete or missing test coverage
A sustained high failure rate can block releases and erode trust in your CI/CD process. Investigate immediately.
***
## Monitoring Duration
Pipeline duration affects how quickly developers receive feedback. Long-running pipelines slow down releases and lower developer productivity.
Use **Azure DevOps Analytics** to track duration and pinpoint bottlenecks:
1. In Azure DevOps, go to **Pipelines**.
2. Select the **Analytics** tab.
3. Install the [Analytics extension](https://marketplace.visualstudio.com/items?itemName=ms.vss-analytics) if required.
***
## Mitigating Flaky Tests
Flaky tests are those that pass or fail without code changes. They undermine confidence in your test suite and waste developer time.
### Strategies to Handle Flaky Tests
1. **Identify and Isolate**\
Use test-history tracking in CI to flag and quarantine flaky tests.
2. **Investigate Root Causes**\
Examine environmental factors (databases, networks), concurrency issues, or timeouts.
3. **Improve Test Design**
* Use stable test data (avoid timestamps).
* Mock external dependencies.
* Assert specific outputs only.
4. **Automatic Reruns**\
Configure retries for failed tests to distinguish real failures from flakes.
5. **Prioritize and Quarantine**\
Move flaky tests into a quarantine suite and schedule regular fixes.
6. **Select Robust Tools**\
Choose test frameworks and CI platforms with built-in stability and analytics.
***
## Azure Test Plans for CI/CD
[Azure Test Plans](https://learn.microsoft.com/en-us/azure/devops/test/overview) offers integrated test management and analytics to unify test efforts in your pipelines.
Key benefits:
* **Integration** with Azure Pipelines for live insights
* **Collaboration** via shared test plans and results
* **Traceability** linking tests to builds and releases
By leveraging Azure Test Plans, teams can manage flaky tests effectively and keep CI/CD processes stable.
***
## Best Practices for Pipeline Health
* Continuously monitor failure rates, durations, and flaky tests
* Triage and resolve issues as they arise
* Optimize build scripts and test suites
* Use Azure DevOps tools for feedback loops and ongoing improvements
***
## Links and References
* [Azure DevOps Analytics Overview](https://learn.microsoft.com/en-us/azure/devops/report/analytics/overview)
* [Analytics extension for Azure DevOps](https://marketplace.visualstudio.com/items?itemName=ms.vss-analytics)
* [Azure Test Plans Documentation](https://learn.microsoft.com/en-us/azure/devops/test/overview)
* [AZ-400: Designing and Implementing Microsoft DevOps Solutions](https://learn.microsoft.com/en-us/certifications/exams/az-400/)