[MNT-10070] Provide audit filter capabilities for audit applications Created: 29-Nov-13 Updated: 27-May-15 Resolved: 24-Sep-14
|Project:||Service Packs and Hot Fixes|
|Type:||Service Pack Request|
|Reporter:||Marco Mancuso [X] (Inactive)||Assignee:||Closed Bugs|
|Remaining Estimate:||0 minutes|
|Time Spent:||3 days, 6 hours, 30 minutes|
|Original Estimate:||Not Specified|
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)
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.
|Comment by Derek Hulley [X] (Inactive) [ 28-Mar-14 ]|
I think that we have a bug here. The audit applications should not veto data that might be required by other applications.
|Comment by Derek Hulley [X] (Inactive) [ 08-Sep-14 ]|
Indeed, I would have expected to get the same inbound data for each of the applications app1, app2 and app3. This can be neatly demonstrated using a test rather than manually. Please set up the test as you describe and ensure that each application gets to audit the same data.