Extending counting of unique secondary users beyond issues, projects and users
In 14.6 we introduced unique userid count for Geo proxied requests to service ping. This appears to only count users visiting specific pages/routes such issue, project and user pages. It does not increment the count when a user logs in or when they pull/push data to the secondary. @nwestbury performed an investigation into this here
I am not sure of the historical reasons for limiting the tracking of counts to specific pages. In general it is useful to know how many users are being accelerated by Geo secondaries. It is therefore important to track pull/push requests since these will likely be the most common interaction flows for users accelerated by secondary sites. Additionally it would be useful to as login requests if possible.
We have started using this count as one of the performance indicator metric for Geo replication.
@geo-team I'd like to get everyone's thoughts on how we might be able to extend the current functionality to capture the major workflows users would perform via secondary sites. I'd like to understand any technical challenges.