Skip to content

FY21-Q3 Infra KR: Work with Package Team to implement service-level spend metrics => 100%

I have broken this OKR out from https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/9926 as there are several items that will not be able to be done in Q2.

End Goal:

[revised]

  • 3 base cost metrics defined in group cost PI dashboard

https://app.periscopedata.com/app/gitlab/744908/Group-GCP-Cost-PI's

OKR Retrospective

This retrospective is meant to be an impartial summary of of what went well as well as areas where we could improve so that we can keep improving for next time.

Thanks @trizzi for your collaboration on this OKR, feel free to comment your thought on this issue as well.

What Went Well

We had good meetings related to this OKR and a shared understanding of the importance of this work now and in the future.

We were able to create some general cost metrics that are useful for seeing growth in registry storage and download costs.

What didn't go well

We ended up changing the end goal to be focused solely on providing general cost visibility when there are other things we still would like to do, because those things don't fit well into a single quarter OKR format.

What should we try to do in the future?

Work with Tim to continue to iterate on Registry cost metrics for what is most useful to them.

Once migration is done, create more granular metrics around registry usage to understand the usage and storage growth of the product.

Track Ongoing Registry Migration cost.

Discuss other ways to track work such as this outside of OKR process, because it is important to track, but may need to be tracked over multiple quarters, which does not fit in the current OKR format.

Edited by Davis Townsend