Resolve double counting in all Redis service's request rates
For a number of Redis services, request rates from both primary_server
and rails_redis_client
are used to derive the service's request rate. This leads to double-counting as we sum both server and client side stats together. Taking 1 of the 2 is sufficient.
Partially resolved in gitlab-com/runbooks!5592 (merged). In gitlab-com/runbooks!5601 (merged), We take rails_redis_client
's rate into account instead since it has an apdex defined while primary_server
does not.