William Armiros

Hi @kullu-ashish, Unfortunately there is no equivalent to the OpenTelemetry Event in the X-Ray data model so events are dropped when sending OTel spans to the X-ray backend. We will...

Docs have been updated here: https://aws-otel.github.io/docs/getting-started/x-ray#configuring-the-aws-x-ray-exporter We are working with the X-Ray backend team to update our data model to support span Events as first-class citizens. Will leave this open...

Hi @dimitardanailov - can you clarify what your questions for X-Ray in particular are per the title of this issue? It seems your questions relate to using ADOT for metrics...

@Aneurysm9 I'm not sure which milestone to include this under to ensure it doesn't become stale - what do you think?

Thanks - we will take a look at the renaming in `awsxrayexporter`

The issue of `service.name` not being respected is covered here too: https://github.com/aws-observability/aws-otel-java-instrumentation/issues/158 I think we should leave this open since the change is on the collector and it's a WIP.

Fixed by #341, to close at next release.

Hi @a-h, Thanks for raising this. We are tracking the cold-start issues and considering modifying the wording on our documentation, stay tuned! Are all of the durations in your screenshot...

Hi everyone, There are currently no plans to support GORM in the X-Ray SDK. OpenTelemetry Go supports instrumenting GORM with a 3rd party instrumentation package: https://github.com/uptrace/opentelemetry-go-extra/tree/main/otelgorm You can see OpenTelemetry-approved...

Hi @joanlopez - thanks for the feedback! We'd be happy to take a look at a PR for a new client instrumentation, however at this time we will not be...