arjun289
I have an umbrella app(having one core Elixir and two Phoenix apps) running on prod in a docker container. In the dev environment if there is an error a stack trace is shown which can help us debug the issue.
In prod, all the debug messages are being shown, however, the exception isn’t. Is there a setting to be done for the logger to show all the information.
From the logger documentation here Logger — Logger v1.20.2, if we keep it to debug then we should see everything but all I get is a 500 error response without any trace. Any help is appreciated.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
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
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #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.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
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 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
hauleth
Check out this Cowboy handlers proably exit, not being logged or reported anywhere. It may be the source of your problem. The exception should be shown, maybe there is something other capturing that message?
Additionally you can try Sentry to handle errors logging in more developer friendly way.
arjun289
Thanks @hauleth will check this out, could probably be the reason. I had added sentry, but for sentry to work the error log should come, for some reason the error log itself doesn’t come.