This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-04
Channels
- # announcements (1)
- # architecture (18)
- # aws (7)
- # babashka (63)
- # beginners (38)
- # bristol-clojurians (1)
- # circleci (1)
- # clj-kondo (10)
- # clojars (4)
- # clojure (159)
- # clojure-berlin (3)
- # clojure-europe (4)
- # clojure-italy (7)
- # clojure-losangeles (6)
- # clojure-nl (7)
- # clojure-spec (3)
- # clojure-uk (109)
- # clojurescript (54)
- # css (1)
- # cursive (38)
- # data-science (2)
- # datascript (3)
- # datomic (14)
- # docker (2)
- # duct (11)
- # fulcro (47)
- # jobs (8)
- # jobs-discuss (3)
- # kaocha (4)
- # malli (3)
- # nyc (2)
- # off-topic (30)
- # overtone (3)
- # re-frame (17)
- # reagent (33)
- # shadow-cljs (29)
- # spacemacs (3)
- # specter (4)
- # tools-deps (13)
- # xtdb (13)
Hi everyone! We still have room for presenters at our next meetup. The topic is logging. We’d love to hear from you! Drop ideas here in the channel, or you can dm @dorab or @ticean if you’re more comfortable doing that.
Selfishly, I use timbre
but have been battling with slf4j
this week. We have untamed, chatty Java libs logging at all levels. I’d like to log all of it as structured (json) logs. ♥️💖 if someone presents a good solution for that. 😂 😂 😂
We use Cambium ( https://cambium-clojure.github.io/ ) for structured logging, but unfortunately I’m not able to make it. I also dug into trying to use LogBack in a more raw way a while back, but hit a lot of dead ends getting structured logging to work.
Thanks for the link @defndaines! I haven’t tried Cambium and will give it a look!