Metrics and traces answer different questions—Micrometer’s rich registry ecosystem handles “how much/how often,” while OpenTelemetry owns end-to-end causality.
Micrometer’s Observation API gives us a single façade: one hook in HttpClient, pluggable handlers fan out to Prometheus stats and OTLP spans. Arturo On Sun, 3 Aug 2025 at 4:43 PM, Gary Gregory <[email protected]> wrote: > Why both? Or is there an Java API facade that covers both like JDBC, JPA, > JMS, Logging and so on? > > Gary > > On Sun, Aug 3, 2025, 10:35 Arturo Bernal <[email protected]> wrote: > > > Hi all, > > I’m exploring adding optional OpenTelemetry & Micrometer support to > > HttpClient > > It’ll be fully configurable via the user’s ObservationRegistry and OTel > > settings. > > Details are TBD, but the goal is zero-boilerplate tracing & metrics. > > > > Would love quick feedback on module placement and overall approach. > > > > Thanks! > > Arturo > > >
