silviurosu
I encountered a problem recently trying to listen for Phoenix.Logger events in Phoenix Dasbboard.
Since I have multiple phoenix applications running into my all as separate umbrella applications I appended specific event prefix to Plug.Telemetry like this:
plug(Plug.Telemetry, event_prefix: [:payments_api, :phoenix, :endpoint])
Telemetry plug is taking in consideration the event prefix correctly. Phoenix.Logger instead does not. Handlers are hardcoded and the event names can not be configured as you can see here: phoenix/lib/phoenix/logger.ex at d106fbef5366761669c7dbc34931996fc5a30c30 · phoenixframework/phoenix · GitHub.
Should we not be able to configure the logger prefix also? I want your opinion before spamming phoenix repo with pull requests.
Where Next?
Trending in Discussions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
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
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
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.
**Building the future of software with AI, trust, and human connection.**
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)
josevalim
Yes, the Phoenix logger only handles its own prefix. If you are using another one, we assume it is because you don’t want Phoenix to hook into it. I am not sure this is something we would change. You can always plug in your own logging too!
silviurosu
Having multiple Phoenix applications in the same VM is a common scenario and collecting separate metrics for each it’s required in this case. Being able to append a prefix like Plug.Telemetry does seems like a nice way to do it in my opinion instead of duplicating code for entire Phoenix.Logger.