Geo Secondary Proxying usage ping
In #273134 (closed), we've introduced tracking the number of OAuth grants in the usage ping as the number of users accessing a Geo secondary.
With Geo secondary proxying, there won't be an OAuth flow anymore (except in a few cases where the requests aren't proxied, like the admin/geo page), so this won't work as intended and will likely decrease with customers switching to secondary proxying.
We need to find a different way to measure usage when secondary proxying is used.
Proposal: Maybe we can add a header or some annotation when proxying requests, then the primary can store that in the events table, and we would use that count for the usage ping?