belaustegui

belaustegui

Pretty printing Phoenix request parameters

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.

First 3 of 3 Posts Switch mode

NobbZ

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

hauleth

AFAIK it is not currently possible to change Phoenix.Logger format 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

ferry331

You should be able to use Kernel.inspect/2 to pretty print conn:
Logger.debug inspect(conn)

— All posts loaded —

Where Next?

Trending in Questions Top

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
jonnycharles
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
spammy
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
silverdr
Using Phoenix.LiveView.TagEngine as an EEx.Engine is deprecated! To compile HEEx, use Phoenix.LiveView.TagEngine.compile/2 instead. Sta...
New
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
bottlenecked
Hi all, I wanted to ask how the community is dealing with post-release steps. Today we have Ecto migrations, which make sure that the db...
New
michallepicki
I am using Oban and occasionally, shortly after a deployment, a handful of jobs can fail because of dependency on other parts of the syst...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve. They are GUI (Emerge) and State management (S...
New
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
type1fool
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New
akoutmos
@hugobarauna and I (Alex Koutmos) have been hard at work on writing a book on Nerves that takes you from simply blinking LEDs to building...
New

We're in Beta

About us Mission Statement