Event Cache

Luden supports caching last events in storage (currently only Redis is supported). All income events will be stored in meta storage as well as processed events with DB data types and errors if occurred. Default cache size is 100 events per destination. It is configured in server.cache.events.size.

This feature requires meta.storage configuration.

server:
  cache:
    # true by default. If false Jitsu doesn't cache any events
    enabled: true
    events:
      # default value. Amount of events which are saved per token or destination.
      # If there are more events, old ones will be replaced with new ones.
      size: 100
      # by default Luden applies rate limiting for not saving all events into the cache.
      # Luden saves in cache ${size} events per ${time_window_sec}. Other events are skipped.
      time_window_sec: 60
      # Every ${trim_interval_ms} value Jitsu will delete events from cache
      # if size of the cache collection by token or destination is greater than ${size}
      trim_interval_ms: 500
      # When Luden receives malformed event JSON, event will be cut to ${max_malformed_event_size_bytes} bytes (10KB) and saved to cache
      max_malformed_event_size_bytes: 10000
    pool:
      #number of goroutines which are process events cache
      size: 10


destinations:
...

meta:
  storage:
    redis:
      host: redis_host
      port: 6379
      password: secret_password