hubertlepicki
I am trying to configure logging in Oban in the following way:
- I don’t want to be overwhelmed by internal Oban logs. When I set
config :oban, log: :warningthis happens, but would like to see errors and warnings logged if this happens in Oban internally. - I do want to see logs emitted from the
process/1function in all of my workers.
I can’t seem to be able to configure it this way, in fact all log messages emitted from my workers seem to be swallowed/disappear, if I set the logging level to :warning on Oban config, and it outputs a bunch of debugging log statements like Ecto queries done with status: warning instead.
What is the correct configuration in that case? I want to see important internal events from Oban and my logs I emit from worker.
The logs I emit from worker manually are properly logged out when I don’t specify log: :warning to Oban config.
Where Next?
Trending in Questions
Other Trending Topics
Latest Oban Threads
Latest on Elixir Forum
Sponsor Spotlight
Practical resources that improve the lives of professional developers.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
D4no0
You need to use telemetry handlers to catch logs from workers. Here is the documentation for this: Oban.Telemetry — Oban v2.23.0
This always seemed strange to me, especially since older releases didn’t even include documentation on this behavior.
sorentwo
The
logoption is purely for ecto logging, for historic reasons. To get job, plugin, and other important logging you need to attach the telemetry logger manually:The goal for Oban v3.0 is to attach a logger by default, and control the levels/options with the
logoption, and set the ecto/repo log level separately.There has always been documentation on the
Oban.Telemetrymodule about the logger, since it was introduced in Oban v0.4. However, you’re right that it wasn’t included as part of the installation/getting started guides until fairly recently.hubertlepicki
oh that would be perfect! I’m glad it’s on the to-do list. I’ll stick to attach_default_logger for now and ignore the log option.