jitsu
jitsu copied to clipboard
Proxy API events cache endpoint – separate caches for each event status
Problem
Limited number of last events is stored in the events cache. That makes the events cache very inconvenient for catching error events – high chance that cache will be overflown with success events most of the time.
Solution
- Introduce separate caches based on event status (success, error)
- Introduce new or modify current Proxy API endpoint
- Support filtering by date, time, destinations, status (when both status requested - lookup for 2 caches)