Sébastien Crocquesel

I mean like https://github.com/envoyproxy/envoy/blob/main/source/extensions/filters/common/ext_authz/ext_authz_grpc_impl.cc

From what I understand, tracing span for streaming grpc call was not implemented during https://github.com/envoyproxy/envoy/pull/1885.

Yes, span should begin with the start of the stream and should end at the end of it. And a child span can be created in the filter to align...

I tried to set the `initial_metadata` with `%REQ(x-b3-traceid)%` but if the downstream request do not have those headers, envoy generate a new trace and I don't get those values at...

I close it as you were faster than me aligning with the 2.15

> @MarcelMichau Unfortunately, I wasn't able to try this out yet. Thank you for the write-up, I wish I could have saved you some of the effort that it must...

When available it could be interesting to test if we can actually use a FIC with MSI assertion in a daemon app. Ifo so, should we use SourceType or AcquireTokenOptions...

> @scrocquesel It seems you are using Quarkus native with the [AWS SDK](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation/aws-sdk/aws-sdk-2.2/library/README.md)? > > cc @brunobat Actually, I'm a maintainer of https://github.com/quarkiverse/quarkus-amazon-services. I come up with these substitutions https://github.com/quarkiverse/quarkus-amazon-services/pull/1242/files#diff-1315d92c76bc1b2c96ba5966b4dca0e048aa0c6b92c4f6d7531b15542a9d52c7...

We rewrote the quickstart to use DevServices for AWS eliminating many manual setup tasks. @gsmet, this can be closed thanks to #1356.

@gsmet could be closed