Home
Welcome to the metrik wiki!
Four key metrics was firstly introduced in State of DevOps report in 2014 and marked as ADOPT by ThoughtWorks Tech Radar` in 2019. These metrics could be used to measure the software delivery performance, which are:
- Deployment frequency: The number of successful deployments to target environment under the given date range.
- Lead time for changes: The average amount of time it takes to go from code commit to code running in target environment under the given date range.
- Change failure rate: The percentage of deployment failures in target environment under the given date range.
- Meantime to restore service: The average amount of time it takes to restore from deployment failures in target environment under the given date range.
Metrik is an automation tool that pulls data out of CD pipelines and analysis the four key metrics trends for delivery teams.
Features that differentiate Metrik from other similar tools in the market:
- Metrik hides the complex algorithms underneath the simple UI. A user only needs to spend less than 10 minutes to install the tool and view their data on the chart dashboard.
- Metrik provides multi-pipeline supports natively. A consistent, universally acknowledged algorithm is applied regardless of the types of CD tools. This is particularly useful for organizations where various tools are used across teams. E.g. ThoughtWorks.
- The tool is designed and implemented in an extensible manner, where the effort of extending the product to other CD tools is minimized. Up to now, Metrik supports Jenkins and Bamboo , and more is coming soon.
By using Metrik, one could easily measure their delivery performance, hence get some insights in terms of how well they perform, and direction for improvement.