belaustegui
By default, the Phoenix.Logger prints some useful information about each received request.
Turns out that (at least in development) the color and the log format is not very legible and difficult to find among other log entires.
I was wondering if there is a way to customize how this information is displayed, or if the Phoenix team would be open to a proposition to update it.
This is a screenshot I’ve took that shows what I mean.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #elixirconf-us
- #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.
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.
Master modern tools, write cleaner code, and tackle real-world challenges.
Enabling companies to succeed by building software people love.
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)
NobbZ
I can’t really read anything on the screenshot.
But what I can see is, that it seems that there are some pretty printed single value spanning many lines.
From the point of aggregating logs via ELK or similar, I really do not like spanning single log entries over more than a single line.
If though you really want that, you can provide a custom formatter that does this for you as you want it.
edit
The screenshot has been updated splitseconds after I submitted the post. Its now better readable, but doesn’t really change my thinking about the problem at hand.
hauleth
AFAIK it is not currently possible to change
Phoenix.Loggerformat in any way. Maybe in future, when structured logging in Elixir will became a thing it will change, but for now I am not aware of any way to help You.As this is local development output (as it outputs blue debug messages) it shouldn’t be a problem, as the production format can be completely different.
ferry331
You should be able to use Kernel.inspect/2 to pretty print conn:
Logger.debug inspect(conn)