cblavier
I’m writing a mix task that needs part of my app to be started.
But when I use Mix.Task.run("app.start") or Application.ensure_all_started(:my_app), I have tons of info logs like this:
16:02:55.606 [info] Application lager started on node nonode@nohost
16:02:55.624 [info] Application gpb started on node nonode@nohost
16:02:55.624 [info] Application exprotobuf started on node nonode@nohost
16:02:55.640 [info] Application eex started on node nonode@nohost
16:02:55.661 [info] Application mime started on node nonode@nohost
16:02:55.664 [info] Application plug_crypto started on node nonode@nohost
16:02:55.678 [info] Application telemetry started on node nonode@nohost
16:02:55.680 [info] Application plug started on node nonode@nohost
Any way to silent this?
Already tried an experimental cocktail with multiple combinations of following commands. Not working … 
Mix.shell(Mix.Shell.Quiet)
Logger.disable(self())
Logger.remove_backend(:console)
Mix.Task.run("app.start")
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
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
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #ai
- #elixirconf-us
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
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.
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
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 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
fuelen
Can’t believe
Logger.remove_backend(:console)doesn’t help. I guess Logger is successfully disabled and these logs were written bylager.cblavier
Maybe?
What do you think I should do?
I’m a bit confused between logger and lager, it reminds me of the dark ages of Java (log4j, common-logging
)
LostKobrakai
:lager- popular third party logger in erlang:logger- erlangs new logger api (newer than:lager)Logger- elixir’s logger api (in recent versions of elixir mostly backed by erlangs:logger)cblavier
It was indeed Lager, thank you @fuelen!
I was able to get rid of most logs with :
and then
Logger.remove_backend(:console)removed the few extra logs remaining!