Bifurcation of Logs into different collections using a Configuration

Hi,

Thank you for a great library supporting audit feature. While the feature is comprehensive, is there a way I can configure where my logs should go and sit.

To quote a few examples, I may want to:

1. Have my logs go into separate tables/collections based on the Source Application. Meaning thereby, let's say I have multiple applications but would like to have all my audit data in a single database, but seggregated into separate tables/collections. Is this a possibility?
2. Have my logs move into a dynamically created table/collection by date. Meaning thereby, let's say, I configure my logging/auditing such that every month or so, a new table/collection gets created and the audit logs go into this table/collection.

Please let me know your thoughts on the above two.

Warm Regards
Siva

No files, tests, or entry points are named in the issue. Start by locating the audit-log configuration and persistence entry points, then clarify the desired scope for source-application separation and date-based table or collection creation; done requires an agreed configuration design and implementation criteria for the supported databases.