Adrian Cole

thanks for the context. I think the best next step is to choose the webflux example or similar with the exact versions of micrometer you are using because I know...

FWIW, what I am concerned with is that it has something to do with this https://github.com/spring-projects/spring-boot/blob/1a907bf47e1dbcc3b5c8e41b47b9b40bbc42740b/spring-boot-project/spring-boot-actuator-autoconfigure/src/main/java/org/springframework/boot/actuate/autoconfigure/tracing/CompositePropagationFactory.java#L78 Spring have paid employees, rather than rely on volunteer time we should get together...

fyi for your own experiments, here's how we have measured this in the past * [B3PropagationBenchmarks](https://github.com/openzipkin/brave/blob/master/instrumentation/benchmarks/src/test/java/brave/propagation/B3PropagationBenchmarks.java): our optimized B3 propagation. * I believe spring boot uses this, but may also...

also added this so you can see how changes might affect others. There may be a way to improve this without affecting others, and as always a change is welcome...

I think this is also not relevant when all handlers read, but don't mutate, the span.

instrumentation is only added once folks ask for it, and someone has time to implement it. Sometimes, not everything ends up here.. For example, it could be that thrift ends...

ps I took a peek at the GHA workflows and not sure which is actually running the tests marked !nodocker, as I only see a go test for nodocker.

TL;DR; this was implicitly rolled back into a second/review session of the existing time slot, then canceled. There's some interest in a 3 timezone proposal. We want UTC+8 to be...

here's the community roll-up issue I was asked to create by @svrnm https://github.com/open-telemetry/community/issues/2176

works for me. I think it may help with attendance to do a couple things, but up to you. * date the slots based on the 9am, not normalize to...