Increased logging after switching to using ExAudit.Repo

[joelevering]

In a Phoenix app I maintain when I switch our sole Repo from using Ecto.Repo to ExAudit.Repo, I see innumerable log lines after booting up the app locally:

2020-05-29T16:05:28.559Z [DEBUG] QUERY OK db=0.1ms
begin []
2020-05-29T16:05:28.559Z [DEBUG] QUERY OK db=0.1ms
begin []
2020-05-29T16:05:28.559Z [DEBUG] QUERY OK db=0.2ms
begin []
2020-05-29T16:05:28.559Z [DEBUG] QUERY OK db=0.2ms
begin []
2020-05-29T16:05:28.559Z [DEBUG] QUERY OK db=0.2ms
begin []
2020-05-29T16:05:28.560Z [DEBUG] QUERY OK db=0.5ms
commit []
2020-05-29T16:05:28.560Z [DEBUG] QUERY OK db=0.7ms
commit []
2020-05-29T16:05:28.560Z [DEBUG] QUERY OK db=0.5ms
commit []
2020-05-29T16:05:28.560Z [DEBUG] QUERY OK db=0.6ms
commit []
2020-05-29T16:05:28.560Z [DEBUG] QUERY OK db=0.8ms
commit []

My config is set up with an empty list for tracked_schemas and besides that just a version_schema set.

Is this happening to anyone else and/or expected?

[narrowtux]

What is the application doing with the Repo when these logs appear? begin/commit logs are expected in a way, because ex_audit will use transactions to insert the tracked versions.

There should be one begin and one commit per insert/update/delete call. That would be normal.

[narrowtux]

@joelevering can you provide more details to this issue?

[joelevering]

The app is a Phoenix app that's idling, but it's using oban which may be a cause. I've de-prioritized figuring this out for the moment... was mostly interested if this is an obvious problem to anyone and it seems like the answer is "no". Feel free to close if you'd like, otherwise I can update after doing more investigation