johnhamelink
Hey there,
I have an endpoint that’s used to check to see if an instance is up and available (for use with a node balancer). The node balancer will hit this endpoint once a second or so. Obviously that produces a lot of unnecessary log chatter, so I’m trying to figure out how to disable the request logging for this endpoint only.
I noticed that in Phoenix.Controller there’s an option under Plug Pipeline called “log” - but I’m not sure if it’s relevant and how to use it if it is.
Anyone else figured this out before?
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
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
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
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
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
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
- #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










Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
johnhamelink
I figured it out
thanks to @benwilson512 and others!
The answer is to use pipelines:
Plug.Loggerline from theendpoint.exfile.plug Plug.Loggerto all other pipelinespipe_through <pipeline which doesn't include logger>to the scope you don’t want to log.gzrain
Hi
I know this post has been a while but I have the same situation like this now.
I have a
health_checkcontroller which receivespingevery xx secs, and would be ideal the logger to be turned off for it.But the current phoenix version does not have
Plug.Loggerinendpoint.exany more so I don’t where to disable it and then apply it in router.ex via different pipeline.Anyone has idea?
elixir: 1.9.1
phoenix: 1.4.9
Kind regards
Rain
jola
or
gzrain
thank you for you reply, however I cannot get it work as the documentation
and then I open
router.ex, tried bothand
still I can see the logs
Regards
Phillipp
Confirmed. The option on the scope does not work.
And I don’t like the pipeline workaround.
cnck1387
I use this plug:
And then
endpoint.exuses it like thisplug(HelloWeb.Plug.HealthCheck)as the first thing that gets defined. This way it does the least amount of work possible. No controller or route needed and your normal pipeline gets ignored.Pretty sure I grabbed that snippet and slightly modified it from one of @jola’s blog posts.
gzrain
it works like charm!! Thanks mate ~
jonator
It may be best to mark yours as the best solution as not to confuse others.
SZJX
This StackOverflow post also provides two alternatives approaches:
Pre-Telemetry (by Wile E. Coyote):
Define a custom plug to replace
Plug.Loggerinendpoint.ex:Post-Telemetry (by Ilja Everilä):
Define a custom Telemetry Plug and replace the plug in
endpoint.ex:dvic
I just ran into this. I believe the scope option is not about those
GET /andSent 200 in 286µslogs, it’s about these debug logs you see:You will notice that the
log: falseoption onscopedoes disable these log entries.The other request logs are disabled by adding
log: falseto thePlug.Telemetryplug (in endpoint.ex), but this then applies to all routes. I am not aware of an approach to disable these on a per request basis (without resorting to your own logging).