This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-02-21
Channels
- # announcements (9)
- # babashka (45)
- # beginners (45)
- # calva (1)
- # clojure (40)
- # clojure-austin (16)
- # clojure-europe (16)
- # clojure-nl (1)
- # clojure-norway (35)
- # clojure-uk (4)
- # clojurescript (11)
- # conjure (3)
- # cursive (4)
- # datalevin (14)
- # datavis (1)
- # datomic (8)
- # emacs (6)
- # hyperfiddle (7)
- # introduce-yourself (3)
- # joyride (17)
- # missionary (16)
- # off-topic (2)
- # pedestal (9)
- # polylith (27)
- # re-frame (7)
- # reitit (1)
- # releases (1)
- # shadow-cljs (17)
- # sql (17)
- # tools-build (19)
- # tools-deps (15)
- # xtdb (15)
What am I looking at? This is the output from the Jaeger UI for a trace inside Pedestal, when using the Open Telemetry Java agent.
The agent provides the outer-most Span; Pedestal's request-tracing interceptor adds the inner Span; this means we get much better information about the time spent outside of Pedestal.
For example, when streaming a long response, Pedestal will have closed its Span while the response is still sent back down but Jetty is still working on it and I believe that time will be reflected in the outer span, at the end.
Nice!! Looks much better than the default jetty 8 spans I’m getting. Those are all under GET /**
for some reason.
This is with Jetty 11. The agent seems to provide a span named after the method, and the interceptor creates a span named with the method and route path.
First phase is ready for review: https://github.com/pedestal/pedestal/pull/804