This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-07
Channels
- # aleph (15)
- # beginners (18)
- # boot (18)
- # business (1)
- # cider (11)
- # cljs-dev (13)
- # cljsrn (19)
- # clojure (14)
- # clojure-austin (8)
- # clojure-dusseldorf (1)
- # clojure-finland (1)
- # clojure-greece (118)
- # clojure-poland (3)
- # clojure-russia (46)
- # clojure-spec (65)
- # clojure-uk (18)
- # clojurebridge (3)
- # clojurescript (16)
- # cloverage (7)
- # core-async (8)
- # cursive (74)
- # datomic (28)
- # editors (3)
- # emacs (3)
- # ethereum (5)
- # hoplon (19)
- # jobs-rus (18)
- # lein-figwheel (1)
- # off-topic (2)
- # om (107)
- # om-next (4)
- # onyx (23)
- # pedestal (23)
- # proton (3)
- # protorepl (1)
- # re-frame (108)
- # reagent (10)
- # ring-swagger (15)
- # spacemacs (2)
- # specter (11)
- # testing (7)
- # untangled (79)
- # vim (4)
- # yada (53)
would love to have something like that that integrates with existing dashboard tools (like Kibana)
My plan is to make something that is extensible (via subscribing to streams), so i think that should be possible. I already found that the hystrix metrics granularity is not good enough for us so I’m thinking of other visualizations too. But the hystrix dashboard is a start 🙂
One thing I would really like is to have a visualisation of latent requests. This visualisation should be able to tell what caused a timeout for instance. This visualisation could be a timeline of calls to nested services
not sure
i don’t think so
I think they did the same at Fitbit by having an explicit state machine (passport) passed through the code
sounds interesting
is it on youtube already?
cool, i’ll have a look
Had a quick glance through it. It has definitely overlap 🙂
@jeroenvandijk: I think we're doing something similar. basically all http requests are tagged, recursively, which we can then use for debugging