The IguanaX Logging and Queuing system is architected for resiliency, performance, and scale. To understand the benefits, you should understand how it works. To take a look at the structure of the log directory - see Log Directory Structure.
The Logging and Queuing system is made up of:
...
...
All
...
data is first committed to
...
a single journal file before being saved into the component
...
log files. Once the
...
data is successfully saved in the
...
log files,
...
it can be removed from the journal file.
Fast Performance: Performance is optimized by writing logs to the queue in batches, based on frequency and file size. This batch approach reduces the number of I/O operations, resulting in faster overall system performance.
Reliability and Recovery: If IguanaX becomes unavailable, all data in the .log files remains intact. The journal file keeps track of queue positions and, upon restart, IguanaX reads the journal to quickly recover and resume operations. If the journal file is lost, IguanaX will reconstruct it using the available .log files.
2. Queue Files:
...
Log Files: Data is written from the journal file and stored in
...
individual log files per component.
...
Long-Term Storage & Flexible Purging: Logs can be stored for longer periods with distinct purge rules per component, offering flexibility in managing data storage without interrupting ongoing operations. Even if a queue is blocked, log purging will continue as scheduled, ensuring uninterrupted management of storage space.
...
All component log files are stored in a single Log Directory - see Log Directory Structure for how IguanaX stores its logs and enables fast searching.