ABP Audit Logging Skill

To configure ABP audit logging for entity history, you enable auditing options and use selectors or attributes to target specific entities in EF Core. This captures create, update, and delete operations with property-level changes for reliable compliance tracking.

Yes, ABP audit trails support sensitive-property exclusions and ASP.NET Core URL filtering. This allows you to ignore noise like health-check GET requests while maintaining a reliable audit log for critical application service invocations.

ABP audit logging works with both EF Core and MongoDB to capture application service calls and entity changes. It supports multi-tenancy by logging the tenant context, ensuring compliant change tracking across different database providers.

You customize ABP audit log storage by implementing the IAuditingStore interface for persistence. To add custom contextual data, you use AuditLogContributor classes, enriching the audit trail with specific application or request metadata.

The best way to capture before and after property values is configuring ABP entity history with explicit selectors for audited entities. This records detailed property-level changes for sensitive workflows while excluding unnecessary properties.

ABP application service calls may not appear if auditing is disabled in options or filtered by ASP.NET Core URL rules. Ensure auditing is enabled, ApplicationName is set, and URL filtering excludes your target endpoints.