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
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m aware of 2 such projects, are there others?
git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
Hi everyone.
My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
Hello folks!
So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
How Can I Optimise Compile Time Dependencies
I have been building an elixir application for about 2 years now. Many modules and files ha...
New
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
Other Trending Topics
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with.
But I don’t use it anymore.
Serverless was the promis...
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
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #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).