This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-27
Channels
- # announcements (10)
- # aws (11)
- # beginners (158)
- # calva (8)
- # cider (14)
- # clj-kondo (1)
- # cljsrn (1)
- # clojure (83)
- # clojure-europe (5)
- # clojure-italy (25)
- # clojure-nl (3)
- # clojure-spec (12)
- # clojure-uk (20)
- # clojurescript (72)
- # community-development (18)
- # core-async (4)
- # core-logic (19)
- # cursive (11)
- # datomic (21)
- # duct (6)
- # events (1)
- # figwheel-main (3)
- # fulcro (15)
- # ghostwheel (1)
- # jobs (1)
- # leiningen (16)
- # off-topic (45)
- # onyx (3)
- # pathom (7)
- # perun (1)
- # ring (3)
- # shadow-cljs (48)
- # spacemacs (10)
- # specter (1)
- # sql (24)
- # tools-deps (7)
- # vscode (7)
- # xtdb (14)
måning!
morning morning
Morning.
At the risk of being accused of spamming the channel, we are still looking for applicants for this role... :uk: / London-Based / Perm - Ethical / B-Corp Startup -> https://cervest.earth/jobs-platform-engineer/
(one day, in the not too distant future, I hope, we will start to open the books on remote working, but for now this is a London, office-based role)
I'll ask here - does anyone have recommends for tracing ring request/responses - perhaps to a zipkin server (or out via a prometheus scrape?)
have you looked at the stuff in iapetos https://github.com/clj-commons/iapetos#ring
that gets you basic latency, success and error metrics out of the box