Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
[https://www.devops-research.com/research.html DevOps Research and Assessment (DORA)] team identified four key metrics for software delivery and operational performance. | [https://www.devops-research.com/research.html DevOps Research and Assessment (DORA)] team identified four key metrics for software delivery and operational performance. | ||
==Delivery Lead Time== | |||
Delivery lead time is the elapsed time it takes to implement, test and deliver changes to the production system. | |||
==Deployment Frequency== | |||
Deployment frequency measures how often you deploy changes to a production system. | |||
==Change Fail Percentage== | |||
What percentage of changes either cause an impaired service or needs immediate correction, such as a rollback or emergency fix. | |||
==Meam Time to Restore (MTTR)== | |||
How long it takes to restore service when there is an unplanned outage or impairment. | |||
Revision as of 23:00, 29 December 2021
Internal
Logs
Monitoring
Deployment
Make it fast to roll back configuration changes if necessary.
Roll out new code gradually, so that any unexpected bugs affect only a small subset of users.
Operational Performance Metrics
DevOps Research and Assessment (DORA) team identified four key metrics for software delivery and operational performance.
Delivery Lead Time
Delivery lead time is the elapsed time it takes to implement, test and deliver changes to the production system.
Deployment Frequency
Deployment frequency measures how often you deploy changes to a production system.
Change Fail Percentage
What percentage of changes either cause an impaired service or needs immediate correction, such as a rollback or emergency fix.
Meam Time to Restore (MTTR)
How long it takes to restore service when there is an unplanned outage or impairment.