fix: audit logger stream-based queryLogs #96
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR prevents memory exhaustion (OOM) when querying large audit logs.
1. Stream-based File Reading
queryLogsmethod was usingfs.readFileto load the entire log file content into memory at once. For large log files (100MB+), this allocated massive strings on the heap, causing OOM crashes or severe GC pauses.fs.readFilewithfs.createReadStreamandreadline.createInterface. This processes the file line-by-line, maintaining a constant O(1) memory footprint regardless of file size.Result: Scalable log querying that is safe for production use with large log rotation policies.