Exclude redis-cache memory from capacity planning

Sean McGivernrequested to merge
exclude-redis-cache-from-capacity-planning into master

This resource should not saturate completely: we have maxmemory and an LRU policy set, and the cache is constantly full. If this saturates, then either:

  1. Something has gone terribly wrong with Redis.
  2. We have misconfigured something.

Both of those will happen much quicker than a week, but we only run the capacity planning report once a week. We will still keep the redis-memory component in the catalog, so saturation is visible on the regular dashboards.

Like !4732 (merged) but for redis-cache. For gitlab-com/gl-infra/scalability#1746.

Merge request reports