Directories Structure
Jitsu keeps all events data in a single directory.
Directory is configurable via log.path in eventnative.yaml. Default value is: ./logs/events or /home/eventnative/data/logs/events for docker images.
Here's the layout of sub-directories. File naming convention. Files usually named as ${file_type}.${var1}=${val1}|${var2}=${val2}.${extention}. The structure is very similar to the URL query string, but instead of `?` parameters are delimited by `|` and `.` is used instead of `?` (dots can't be a part of ${file_type})
| Sub-dir | Purpose | Data format | Filename pattern |
|---|---|---|---|
events/incoming | Incoming events (batch mode only) | Original JSON after ContextEnrichment step |
where |
(status files) | Status of each batch: to which destinations and tables data has been sent successfully | DestinationStatus JSON | incoming.tok=${tok}.log.status |
events/archive | Events that have been already processed | Original JSON after ContextEnrichment step |
or
or
depend on events from batch destination or stream destination or replaying failed events. Where ${tok} is used API token id |
events/failed | Events that haven't been saved to a destination due to error | Collection of EventError: original JSON (after ContextEnrichment step) wrapped with EventError structure | failed.dst=${destination_id}.log |
events/queue.dst=${dest_id} | Stream mode only: persistence for event queue | Binary |
|