This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-10-09
Channels
- # announcements (2)
- # babashka (11)
- # beginners (9)
- # biff (7)
- # calva (20)
- # catalyst (1)
- # cider (8)
- # clerk (46)
- # clj-kondo (18)
- # clj-otel (2)
- # clojure-brasil (22)
- # clojure-europe (18)
- # clojure-gamedev (23)
- # clojure-italy (5)
- # clojure-nl (2)
- # clojure-norway (14)
- # clojure-uk (6)
- # clr (1)
- # datomic (13)
- # emacs (1)
- # hoplon (13)
- # hyperfiddle (53)
- # introduce-yourself (1)
- # java (23)
- # malli (7)
- # obb (35)
- # off-topic (31)
- # polylith (2)
- # portal (9)
- # rdf (15)
- # reitit (12)
- # releases (3)
- # ring (4)
- # shadow-cljs (6)
- # solo-full-stack (3)
why shouldn't we use this? i assume this applies to all agents, like signalfx-otel-javaagent
The OpenTelemetry instrumentation agent and presumably any other agent derived from it populates HTTP Metrics defined by the semantic conventions for supported HTTP servers. The agent generally supplies metrics with greater accuracy and coverage than those supplied by clj-otel
, as the agent has much tighter integration with the supported libraries. However, sometimes the http.route
attribute is unknown by the agent. In these cases you could use the middleware/interceptor to export the metrics, but be warned there will be overlap with metrics produced by the agent which could be confusing.