This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-17
Channels
- # announcements (2)
- # babashka (52)
- # beginners (10)
- # calva (9)
- # cider (2)
- # clj-kondo (7)
- # clojure (63)
- # clojure-europe (26)
- # clojuredesign-podcast (5)
- # clojurescript (13)
- # datalog (2)
- # datomic (6)
- # defnpodcast (1)
- # fulcro (46)
- # incanter (4)
- # integrant (5)
- # jobs-discuss (12)
- # kaocha (1)
- # lsp (31)
- # malli (10)
- # meander (1)
- # off-topic (6)
- # podcasts-discuss (1)
- # polylith (20)
- # rewrite-clj (6)
- # shadow-cljs (23)
- # tools-deps (9)
- # xtdb (13)
- # yada (10)
@borkdude I'm using the datadog apm which integrates with netty and handles all of this :D
@borkdude we use elastic apm with yada, by yada.walk/update-routes and update each response by wrapping it in an anonymous function that starts the apm transaction and then invokes/returns the response within the transaction scope
We (I work with @borkdude) tried to use interceptors for managing APM transactions and spans, but as the active spans are tied to a specific thread this wasn't very straightforward