github
/
developer-roadmap
mirror of https://github.com/kamranahmedse/developer-roadmap.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Roadmap to becoming a developer in 2022
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
5206 Commits
212 Branches
4 Tags
447 MiB
 
 
 
 
 
Tag: Branch: Tree: 7cb4287925
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7cb4287925'
${ noResults }
developer-roadmap/src/data/question-groups/devops/content/health-monitor.md

1.3 KiB
Raw Blame History

Each DevOps team should define this list within the context of their own project, however, a good rule of thumb is to consider the following metrics:

  1. Build Success Rate: The percentage of successful builds versus failed builds. A low success rate indicates issues in code quality or pipeline configuration.
  2. Build Time: The time it takes to complete a build. Monitoring build time helps identify bottlenecks and optimize the pipeline for faster feedback.
  3. Deployment Frequency: How often deployments occur. Frequent deployments indicate a smooth pipeline, while long gaps may signal issues with your CI/CD or with the actual dev workflow.
  4. Lead Time for Changes: The time from code commit to production deployment. Shorter lead times are preferable, indicating an efficient pipeline.
  5. Mean Time to Recovery (MTTR): The average time it takes to recover from a failure. A lower MTTR indicates a resilient pipeline that can quickly address and fix issues.
  6. Test Coverage and Success Rate: The percentage of code covered by automated tests and the success rate of those tests. High coverage and success rates are good indicators of better quality and reliability.
  7. Change Failure Rate: The percentage of deployments that result in failures. A lower change failure rate indicates a stable and reliable deployment process.