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 in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app?
Looking for hints regarding:
Addi...
New
Kia ora,
We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
Hi all, I wanted to ask how the community is dealing with post-release steps.
Today we have Ecto migrations, which make sure that the db...
New
Hello,
I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance o...
New
Other Trending Topics
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
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
There are three potential reasons for members of this forum to have a look at https://vutuv.de
You are tired or annoyed of LinkedIn.
Yo...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










First 10 of 14 Posts
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).