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?
Trending in Questions
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
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
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
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
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
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
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
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
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
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
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
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
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
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex











Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
mudasobwa
You should rebuild phoenix for this to take effect (
mix deps.clean.)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:
Edit: and IIRC
$metadatais 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$metadatatwice (and I don’t think$request_idwill expand to anything at all)quatermain
Prod still doesn’t work.
I got this in log:
and I have this in config:
gmile
These lines are coming from
Plug.Logger, seethis. To remove them, addlog: debugto the plug init in yourendpoint.exlike this:Those log lines will now only appear in development.