Skip to content

ATLAS-4797: Implement audit filters in Atlas - #347

Open
sheetalshah1007 wants to merge 6 commits into
apache:masterfrom
sheetalshah1007:ATLAS-4797_
Open

sheetalshah1007 wants to merge 6 commits into
apache:masterfrom
sheetalshah1007:ATLAS-4797_

Conversation

@sheetalshah1007

Copy link
Copy Markdown
Contributor

What changes were proposed in this pull request?

Currently, Atlas has to persist all audit events without any constraints which can make audit data grow exponentially after some time. This feature is specifically to reduce Atlas audit storage where generation of audit events can be controlled based on the user's use-case/criteria
Note: Audit data mentioned here is exclusive of Admin Audit Data which persists in atlas_janus table. Filtering will be applicable to the entity audit data which persists in ATLAS_ENTITY_AUDIT_EVENTS table.

How was this patch tested?

Manual testing
Integration Testing
Pre-commit : https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1876/

@sheetalshah1007 sheetalshah1007 changed the title ATLAS-4797: Implement custom audit filters in Atlas ATLAS-4797: Implement audit filters in Atlas Oct 21, 2026
Filter discarded entity audit events in EntityAuditListenerV2 before
persistence so all audit backends behave consistently.

Do not fail entity mutations when audit rules cannot be loaded or
evaluated; fall back to the configured default filter action.
Fix AtlasEntityAuditFilterService logger and add unit tests.
Expose remaining entity audit filter rule admin APIs to match AdminResource.
Add feature documentation, configuration section, and site menu entry
for entity audit filter rules and admin APIs.
Update the test-tools core template query fields to match the current
index schema used by integration tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant