trentjones21
I’m trying to silence the phoenix liveview logs, or at least change them from :info to :debug so they don’t appear in production. The logs I’m referring to are:
19:58:49.505 [info] CONNECTED TO Phoenix.LiveView.Socket in 161µs
Nov 22 12:58:49 web.1 | Transport: :websocket
Nov 22 12:58:49 web.1 | Serializer: Phoenix.Socket.V2.JSONSerializer
Nov 22 12:58:49 web.1 | Connect Info: %{}
Nov 22 12:58:49 web.1 | Parameters: %{"vsn" => "2.0.0"}
Is there an easy way to do this? I don’t see anything regarding logs in the live view documentation.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
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
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
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.
Bringing learning, work and compliance together since 1987.
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)
OvermindDL1
Info is very verbose, generally not good to have the logs set to that in production (except for short testing sessions). I don’t know if their level can be changed though. They might belong better in
:debugthough actually, or at least some of those lines…trentjones21
Thanks for the response. I’ll up my productions logs to
:warnfor now