使用 Entity Framework Core 进行审计跟踪

我有一个 ASP.NET 核心 2.0，在 SQL Server 数据库上使用实体框架核心.

我必须跟踪和审计用户对数据所做的所有事情.我的目标是拥有一个自动机制来记录所有正在发生的事情.

例如，如果我有表 Animals，我想要一个并行表Audit_animals"，您可以在其中找到有关数据、操作类型(添加、删除、编辑)和创建此操作的用户的所有信息.

这一次我已经在Django + MySQL中做了，但现在环境不同了.我发现了

解决方案

阅读 文档:

<块引用>

事件输出

要配置输出持久化机制，请参阅配置和数据提供者部分.

然后，在关于配置的文档中:

<块引用>

如果您没有指定数据提供者，默认的 FileDataProvider 将用于将 事件作为 .json 文件 写入到当前工作目录.(强调我的)

总而言之，请按照文档配置您要使用的数据提供程序.

I have an ASP.NET core 2.0 using Entity Framework core on a SQL Server db.

I have to trace and audit all the stuff made by the users on the data. My goal is to have an automatic mechanism writing all what is happening.

For example, if I have the table Animals, I want a parallele table "Audit_animals" where you can find all the info about the data, the operation type (add, delete, edit) and the user who made this.

I already made this time ago in Django + MySQL, but now the environment is different. I found this and it seems interesting, but I'd like to know if there are better ways and which is the best approach to do this in EF Core.

UPDATE

I'm trying this and something happens, but I have some problems.

I added this:

1. services.AddMvc().AddJsonOptions(options => {
   
               options.SerializerSettings.ReferenceLoopHandling = ReferenceLoopHandling.Ignore;
           }); 
   

2. public Mydb_Context(DbContextOptions<isMultiPayOnLine_Context> options) : base(options)
   {
       Audit.EntityFramework.Configuration.Setup()
           .ForContext<Mydb_Context>(config => config
               .IncludeEntityObjects()
               .AuditEventType("Mydb_Context:Mydb"))
           .UseOptOut()
   }
   

3. public MyRepository(Mydb_Context context)
   {
       _context = context;
       _context.AddAuditCustomField("UserName", "pippo");
   
   }
   

I also created a table to insert the audits (only one to test this tool), but the only thing I got is what you see in the image. A list of json files with the data I created.... why??

解决方案

Read the documentation:

Event Output

To configure the output persistence mechanism please see Configuration and Data Providers sections.

Then, in the documentation on Configuration:

If you don't specify a Data Provider, a default FileDataProvider will be used to write the events as .json files into the current working directory. (emphasis mine)

Long and short, follow the documentation to configure the data provider you'd like to use.