You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you able to provide some additional explanation with regard to the following Extension Methods of the IAuditLoggingBuilder. Many of the Methods are self explanatory
I'm happy to contribute to the project in any way I can.
Not Sure what this does - omitting this from the builder event seemingly had no effect. Nor did setting UseDefaultAction to false as per below. The "Action" property of the AuditEvent was always populated with the same data.
No discernible difference when added or omitted. Also setting options.UseDefaultSubject = false; has not effect.
AddEventData<TEventSubject, TEventAction>(this IAuditLoggingBuilder builder)
where TEventSubject : class, IAuditSubject
where TEventAction : class, IAuditAction;
No Idea
FYI This project looks perfect for my requirements. I've been able to deploy a custom sink which publishes to a MessageQueue (RabbitMQ) and then in another Microservice I subscribe to the message queue and persist them to a SQL Database.
The text was updated successfully, but these errors were encountered:
Hi @skoruba
Are you able to provide some additional explanation with regard to the following Extension Methods of the IAuditLoggingBuilder. Many of the Methods are self explanatory
I'm happy to contribute to the project in any way I can.
Not Sure what this does - omitting this from the builder event seemingly had no effect. Nor did setting UseDefaultAction to false as per below. The "Action" property of the AuditEvent was always populated with the same data.
No discernible difference when added or omitted
No discernible difference when added or omitted. Also setting
options.UseDefaultSubject = false;
has not effect.No Idea
FYI This project looks perfect for my requirements. I've been able to deploy a custom sink which publishes to a MessageQueue (RabbitMQ) and then in another Microservice I subscribe to the message queue and persist them to a SQL Database.
The text was updated successfully, but these errors were encountered: