fourkeys VS reliza-cli

Four Keys is an open source alternative by Google employees that has been halted earlier this year (but forks-friendly).

DORA metrics

We began tracking Dora metrics by saving all events from our SCM and CI/CD systems into postres DB. Guidance: https://github.com/GoogleCloudPlatform/fourkeys

For starters, there a number of tools such as Sleuth (disclaimer: am co-founder) that will measure the metrics for you. There are also open source options like Four Keys and many vendors like Gitlab also provide some or all metrics as well, though make sure they are measuring things as you expect.

I looked a lot for a tool that could help my team track these metrics. I knew that Jira, Gitlab, and some other tools implement these features but I was looking for something with a high level of customization, and not so coupled to a specific product (we use different systems for deployment, change, and incident) and one day I incidentally discovered FourKeys.

GoogleCloudPlatform/fourkeys is a software tool built by Google to generate insights from data based on the four core metrics mentioned above.

One solution we would recommend is the Four Keys project by Google.

Yep, in the process of productising Google’s Four Keys pattern. Pretty quick to stand up if you’re already on GCP.

We currently provide accurate lead time and deployment frequency calculation capability via Reliza Hub - https://relizahub.com (operating in public preview). Since we track when each piece of code gets deployed to each environment and each instance. Other metrics are on our roadmap.

You then either leverage getlatestrelease functionality of reliza-cli - https://github.com/relizaio/reliza-cli#6-use-case-request-latest-release-per-project-or-product to request approved image or you can use replacetags functionality over your Dockerfile which would replace base image with the one approved - https://github.com/relizaio/reliza-cli#74-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-environment

Note, we have recently released a new replacetags functionality (https://github.com/relizaio/reliza-cli#74-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-environment - going to add tutorial soon) so that you don't need to use templating language inside your helm charts or manifests and instead it would just parse raw base yamls into correct images per each environment.

We're building Reliza Hub for this purpose - https://relizahub.com

Note, it's somewhat outdated and we're working on a new one based on new replacetags functionality - https://github.com/relizaio/reliza-cli#72-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-instance-and-revision