From a business perspective; how many mortgage applications are we rejecting because of reason XYZ, should we change those (are the rules too tight, too loose ...) >> eg can we increase risk to get more business? or do we need to offer a new banking product?

Add auditing functionality to record/log which rules fired during a specific run -------------------------------------------------------------------------------- Key: DROOLS-3774 URL: https://issues.jboss.org/browse/DROOLS-3774 Project: Drools Issue Type: Feature Request Components: core engine Affects Versions: 7.19.0.Final Reporter: Duncan Doyle Assignee: Mario Fusco Priority: Major 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.