This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-09
Channels
- # aws (3)
- # babashka (48)
- # babashka-sci-dev (1)
- # beginners (143)
- # calva (62)
- # clj-kondo (6)
- # clj-otel (3)
- # cljs-dev (59)
- # cljsrn (4)
- # clojure (39)
- # clojure-austin (5)
- # clojure-europe (60)
- # clojure-losangeles (1)
- # clojure-nl (2)
- # clojure-romania (4)
- # clojure-spec (3)
- # clojure-uk (2)
- # clojurescript (32)
- # datomic (17)
- # events (3)
- # figwheel-main (4)
- # graphql (3)
- # gratitude (2)
- # holy-lambda (52)
- # introduce-yourself (3)
- # jobs (1)
- # juxt (5)
- # kaocha (2)
- # lsp (33)
- # nyc (3)
- # off-topic (9)
- # other-languages (4)
- # overtone (1)
- # portal (21)
- # reitit (2)
- # remote-jobs (5)
- # shadow-cljs (65)
- # tools-deps (2)
- # xtdb (8)
Has anyone had any experiences with the instrumentation agent increasing startup times significantly? It doesn't seem to make a difference on my laptop, but application startup time in AWS fargate has increased significantly.
I've worked around this for now by setting OTEL_INSTRUMENTATION_COMMON_DEFAULT_ENABLED=false
and then opting into each of the instrumentation types individually, which seems to help. It still takes longer to start up than without the agent, but it's something.
For questions on OpenTelemetry not specific to clj-otel
, you'll be more likely to get help in one of the OpenTelemetry channels in the CNCF Slack. I suggest #otel-java-instrumentation or #otel-java. See details about the Slack here : https://opentelemetry.io/community/

Hi @U06M4ST0F, we're experiencing the same issue with increased start-up times after adding the auto-instrumentation agent to our Clojure apps. Disabling defaults and enabling only what is needed (as you suggested above), did help to reduce the start-up times back to sane levels. Another option is to ditch the auto-agent and manually instrument, though that comes with obvious other trade-offs.