Kishore: I would start with the OpenTelemetry Agent (https://opentelemetry.io/docs/zero-code/java/agent/). That comes with a fair number of instrumentations that get automatically enabled (e.g. many inbound/outbound HTTP requests, JDBC drivers, etc). There are additional auto-instrumentation packages that you can add if you need to cover additional libraries/APIs. You can also add manual instrumentation to complement the auto-instrumentation. But I’d start with auto-instrumentation and see how far that gets you. Using the Agent is nice because it requires no code modifications (to get started, anyway…you may eventually want to add some manual instrumentation) and it can be configured (enabled/disabled, pointed to whatever OpenTelemetry Collector you want to send tracing data/metrics to) via environment variable and/or Java property. Zipkin these days, I believe, supports OpenTelemetry (https://github.com/open-telemetry/opentelemetry-java/tree/main/exporters/zipkin). So if you’re hoping to have traces sent to Zipkin, you can use OpenTelemetry to send data there as well as any other OpenTelemetry-enabled service (most of my experience is from my prior job, where we sent all of our telemetry to Honeycomb.io). Ryan Sent from my iPad On Aug 5, 2025, at 9:59 AM, Kishore keshu <1989kish...@gmail.com> wrote: -- You received this message because you are subscribed to the Google Groups "dropwizard-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to dropwizard-dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/dropwizard-dev/187E8D7A-440E-44A0-B99A-A5C20423FE04%40gmail.com. |
- Zipkin for Dropwizard 4 Kishore keshu
- Re: Zipkin for Dropwizard 4 Ryan Kennedy
- Re: Zipkin for Dropwizard 4 Kishore keshu
