Details
-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
7.19.0.Final
-
None
-
NEW
-
NEW
Description
We've had multiple requests to add an ootb auditing/logging feature to Drools. The basic requirements is to allow users to audit which rules fired against which data and for what reason.
For example, when you want to determine a fraud transaction, and you insert transactions into an engine, you want to know why a transaction was marked as fraudulent. So you want to know which rules fired against which transaction.
Another requirement I've seen is the following:
[quote]
Furthermore, they want the dashboard to show all the rules that execute by task stage in summary and then have the ability to drill into that list to see the individual delinquent account and the rules fired against it.
[/quote]
I know that we can add listeners to the engine to record things like MatchFired, but it would be great if we would have an ootb feature for this. Maybe even an API that instead of returning the number of rules fired, would be able to return the entire execution context.