Currently, audit filters reject data provided by audit data producers (Inbound Audit Values) as described in the attached article.
This capability is insufficient for any Alfresco applications that makes more than just casual use of Auditing. In a scenario where multiple Audit Applications consume the data from the same data producer (alfresco-api or alfresco-access), filtering inbound data is no longer practical as the filter necessary for one application may suppress data relevant to the second application. On the other hand, having no filter at all can lead to excessive data collected by Audit Applications and introduce significant scalability issues.
Customers are requesting that the following enhancement(s) or sensible sub-sets thereof be considered for future product development:
1) Support of inbound filters specific to an Audit Application (after path mapping has occurred)
2) Support of outbound filters specific to an Audit Application (i.e. reject audit entries based on calculated / extracted data)
3) Support of registrable, custom filter implementations (in addition to sole the simple property-based filter currently in place)
4) Support of aggregation-capable data extractors (audit data extractor with access to multiple inbound values)
These should help customers / developers to improve audit-based solutions to keep unnecessary data from being committed to the database while removing the potential for side-effects by only filtering on inbound values from data producers.