Drools Audit Trail

[doran.george]

Drools use in Chorus does not provide an audit trail on which rule used. 

One solution would be a baseline audit trail similar to Design Studios Automation Services (Service Tab on 'view history' on a transaction). 

[Karen_Hunter]

Current initiative underway to review and manage the service history event logging and retention.  When using a conditional set value, for example, the service history identifies which rule was selected.  Because drools rule sets vary widely by client, what information from the selected rule do you envision being included in the audit history if we were to include additional information in the history event?

Would you agree that the drools service history requirement to record the "selected rule" is similar to a requirement to record the "selected outcome" for a a "conditional set value" or "decision" element?

[doran.george]

Some useful audit trail information:

1.  The rule file name, deployed date, rule file modified date. 
2. The rule name or id that failed.
3. The rule name or id that was successful.
4. gold plating - the action taken on successful rule.

Log date/time for each event above. 

Something similar to automation services.

If Drools rule set has <5 rules, this isn't much of an issue.  If you have > 20 or more, it becomes cumbersome to decode which rule was hit.