Tyler Benson
Tyler Benson
I just submitted a PR that validates the Vertx resource name is being set properly, even with path parameters #2284. Given your initial description mentioned Quarkus, I don't think that...
Upon further review of the description above, I think I misunderstood what was going on. I didn't fully understand how Quarkus and Vertx were related. When writing the test I...
@Kausik-A looks like the linked issue is resolved. Feel free to revisit this.
Please try the latest collector layer release with the `decouple` processor automatically added. This sounds like exactly the problem that processor was designed to resolve.
@mat-rumian do you still want to take care of this? Feel free.
@lpsinger do you want to revisit this? If so, please rebase and fill in the description.
For reference, see the latest spec change here: https://github.com/open-telemetry/semantic-conventions/pull/354
Do you have "Active Tracing" enabled for your lambda?
I'm not sure where the data is being reported to, but the delay might be caused by the synchronous flush. Please try the new `decouple` processor included in the latest...
You still need to add the javaagent or [use the wrapper](https://github.com/open-telemetry/opentelemetry-lambda/blob/main/java/layer-javaagent/scripts/otel-handler). Try adding the following environment variable. ``` AWS_LAMBDA_EXEC_WRAPPER=/opt/otel-handler ```