chore(audit): disable config-change log filtering in 4.0#183
Merged
Conversation
The config-change entries require a data__contains filter, which becomes a full-table LIKE '%...%' scan over every Log row. On installations with hundreds of millions of rows this is prohibitively slow. Comment out the new logic and keep the old REST-only filter active; kept commented for reference.
dkmstr
approved these changes
Jul 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 pull request temporarily disables the inclusion of configuration change log entries from the "LOGS" source in the audit report generation, due to performance concerns with large datasets in version 4.0. Only REST-based log entries are now processed for audit reports, avoiding expensive full-table scans.
Performance and Filtering Changes:
Qobjects and thedata__containsfilter for including config-change entries from the "LOGS" source in the audit report, as this would require a full-table LIKE scan and is not scalable for large installations. Only entries from the "REST" source are now considered. [1] [2]Code and Logic Adjustments:
CONFIG_MARKERconstant and the code that parsed and yielded these entries, to align with the new filtering approach for version 4.0. [1] [2]