# Context https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10370 added pod log usage info to the usage ping on a per-project basis. However, a critical implementation step got missed (by me!), so the usage ping information wasn't actually showing up in https://version.gitlab.com (you can use your dev credentials to log in). This actually broke parts of version.gitlab.com, but https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/181 fixed it! However, https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/181 reports only the pod log usage total - not the per-project values we intended to include. # Problem We now need to decide how to move forward. Option 1 - Finish restricting to just totals. - If we want to just restrict ourselves to total hits to the endpoint per-customer, there's some bloat that should be cleaned up. There's already and MR opened for this change: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14049, so it wouldn't take much. Option 2 - Support per-project counts on version.gitlab.com - Unfortunately, version.gitlab.com doesn't actually have a UI for viewing per-project counts over time. To make the most effective use of this data, we'd need to add that functionality, which would take some time. Since the goal is to ultimately [move away from usage ping](https://gitlab.com/gitlab-org/telemetry/issues/14), this may or may not be worth it.