-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Query Logging: Appsignal.Ecto.log/1 errors when using the preferred Ecto.Repo loggers format #27
Comments
Sorry, I can't seem to reproduce this. Are you using the latest version? It seems the LogEntry that's passed in is I also don't see how this variant could cause the error, they look pretty similar. Are you doing something special? e.g. when there is another logger that does not return the |
It only happens in prod for me. I'm passing in other loggers as well so it looks like this:
|
You should check whether your |
Ah, nice catch. Didn't realize each one affected subsequent calls. |
NP! I also just realised this by looking at Ecto's source. |
From the Ecto docs:
:loggers
- a list of{mod, fun, args}
tuples...https://hexdocs.pm/ecto/Ecto.Repo.html
In Ecto 2.0.2, when I add Appsignal to Repo loggers using the preferred format
loggers: [{Appsignal.Ecto, :log, []}]
it throws an error here:
https://github.com/appsignal/appsignal-elixir/blob/master/lib/appsignal/ecto.ex#L29
The text was updated successfully, but these errors were encountered: