Commit 20d35e50 authored by Alina Mihaila's avatar Alina Mihaila Committed by Evan Read

Proposal for Redis slots name for events tracked using Redis HLL

parent c4aae485
...@@ -635,11 +635,12 @@ Implemented using Redis methods [PFADD](https://redis.io/commands/pfadd) and [PF ...@@ -635,11 +635,12 @@ Implemented using Redis methods [PFADD](https://redis.io/commands/pfadd) and [PF
- `category`: event category. Used for getting total counts for events in a category, for easier - `category`: event category. Used for getting total counts for events in a category, for easier
access to a group of events. access to a group of events.
- `redis_slot`: optional Redis slot; default value: event name. Used if needed to calculate totals - `redis_slot`: optional Redis slot. Default value: event name. Only event data that is stored in the same slot
for a group of metrics. Ensure keys are in the same slot. For example: can be aggregated. Ensure keys are in the same slot. For example:
`users_creating_epics` with `redis_slot: 'users'` builds Redis key `users_creating_epics` with `redis_slot: 'users'` builds Redis key
`{users}_creating_epics-2020-34`. If `redis_slot` is not defined the Redis key will `{users}_creating_epics-2020-34`. If `redis_slot` is not defined the Redis key will
be `{users_creating_epics}-2020-34`. be `{users_creating_epics}-2020-34`.
Recommended slots to use are: `users`, `projects`. This is the value we count.
- `expiry`: expiry time in days. Default: 29 days for daily aggregation and 6 weeks for weekly - `expiry`: expiry time in days. Default: 29 days for daily aggregation and 6 weeks for weekly
aggregation. aggregation.
- `aggregation`: may be set to a `:daily` or `:weekly` key. Defines how counting data is stored in Redis. - `aggregation`: may be set to a `:daily` or `:weekly` key. Defines how counting data is stored in Redis.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment