Unfortunately only for libraries directly supported by/integrated into Quarkus. And combining it with the OpenTelemetry Java Agent for covering the other 3rd party libraries or standard library classes isn’t possible. 😔 - ThreadSky

About ThreadSky

joschi.xyz • 13 days ago

Unfortunately only for libraries directly supported by/integrated into Quarkus.

And combining it with the OpenTelemetry Java Agent for covering the other 3rd party libraries or standard library classes isn’t possible. 😔

Comments

joschi.xyz•13 days ago

Re: https://github.com/quarkusio/quarkus/discussions/47238

maxandersen.xam.dk•13 days ago

well you can add the agent and just not use Quarkus OpenTelemetry - we can't both support fast startup and high throughput AND use of the runtime based agent...

I really do want to see opentelemetry adopting more buildtime instrumentation - making it work in jvm and native images AND in other fwks

allemas.bsky.social•13 days ago

Funny ! that reminds me of the time I experimented with an agent in quarkus to instrument and add oteltraces to all http requests.

I ended up giving up because we had a class loader that loaded after the instrumentation was finished or something like that, I ended up doing my demo with vertx :D

brunobat.bsky.social•13 days ago

Which libraries do you miss instrumentation in Quarkus?

joschi.xyz•12 days ago

In my specific case it was about instrumenting `java.net.URLConnection` in the JDK (used by a third-party library I don't control).

allemas.bsky.social•12 days ago

I maybe missed something, how your agent is loaded to the project?

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply