quatermain

quatermain

Hello,
I have this in prod.exs:

config :logger,
      level: :info,
      backends: [:console],
      compile_time_purge_level: :info,
      metadata: [:request_id],
      format: "$time $metadata[$level] $metadata[$request_id] $message\n"

and I still get this like logger output:

13:55:01.183 [info]  GET /sessions/new
13:55:01.185 [info]  Sent 200 in 1ms

I use this:

Hex:    0.18.2
Elixir: 1.7.4
OTP:    21.1.1
distillery: 1.5.5
phoenix: 1.4.0

Any idea where can be problem?

Showing Posts 1 to 4

mudasobwa

mudasobwa

Creator of Cure

You should rebuild phoenix for this to take effect (mix deps.clean.)

voughtdq

voughtdq

This happens to me so often and I always forget. Basically, the format is specific to the backend, so you have to add this to your config:

config :logger, :console,
      metadata: [:request_id],
      format: "$time $metadata[$level] $metadata[$request_id] $message\n"

Edit: and IIRC $metadata is just a list of the metadata variables. So you can’t “access” it. So you’re format probably should be: format: "$time $metadata[$level] $message\n" or you’ll just repeat $metadata twice (and I don’t think $request_id will expand to anything at all)

quatermain

quatermain OP

Prod still doesn’t work.
I got this in log:

10:02:56.476 [info]  Sent 200 in 11ms
10:03:17.514 [info]  POST /api/v1/

and I have this in config:

config :logger,
  level: :info,
  backends: [:console],
  compile_time_purge_level: :info,
  metadata: [:request_id],
  format: "$time $metadata[$level] $metadata[$request_id] $message\n"
gmile

gmile

These lines are coming from Plug.Logger, see this. To remove them, add log: debug to the plug init in your endpoint.ex like this:

plug Plug.Logger, log: :debug

Those log lines will now only appear in development.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
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
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
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

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews