This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-14
Channels
- # announcements (1)
- # asami (3)
- # aws (1)
- # babashka (22)
- # beginners (39)
- # calva (21)
- # clj-kondo (10)
- # cljdoc (22)
- # cljs-dev (17)
- # clojure (93)
- # clojure-australia (3)
- # clojure-europe (39)
- # clojure-italy (3)
- # clojure-losangeles (17)
- # clojure-nl (14)
- # clojure-russia (2)
- # clojure-uk (5)
- # clojurescript (35)
- # community-development (7)
- # conjure (2)
- # cursive (13)
- # data-science (1)
- # datomic (25)
- # emacs (5)
- # events (4)
- # figwheel-main (2)
- # fulcro (12)
- # graphql (7)
- # gratitude (2)
- # inf-clojure (6)
- # leiningen (6)
- # lsp (49)
- # malli (13)
- # membrane (30)
- # minecraft (1)
- # pathom (3)
- # pedestal (26)
- # polylith (13)
- # portal (2)
- # quil (3)
- # random (1)
- # re-frame (13)
- # reagent (43)
- # reitit (6)
- # releases (1)
- # reveal (2)
- # ring (3)
- # shadow-cljs (30)
- # specter (5)
- # sql (8)
- # tools-build (1)
- # tools-deps (13)
- # videos (1)
Hello all, Is there any way to disable lacinia or lacinia pedestal debug messages from timbre?
Lacinia doesn't do any logging, so I'm confused what debug messages you are talking about? Does timbre do something (I don't use it).
Is it maybe pedestal or jetty debug logging?
Logging on the JVM is a bit... advanced 😬. There's a couple of log-frameworks like timbre or logback. You can set them up not to report debug messages from certain namespaces.
I discovered how to work with timbre and lacinia/lacinia-pedestal, and I´ll share with you:
deps.edn
dependencies
com.taoensso/timbre {:mvn/version "5.1.2"}
com.fzakaria/slf4j-timbre {:mvn/version "0.3.21"}
org.slf4j/slf4j-api {:mvn/version "1.7.32"}
(timbre/merge-config!
{:ns-filter {:allow #{"*"} :deny #{"org.eclipse.jetty.*" "io.pedestal.*" "com.walmartlabs.lacinia.*"}}})
to disable all external logging stuffs !!!👍 1