Trace/span id's not logged with an OpenTelemetry instrumented AWS lambda

[einarjohnson]

Hello everyone,
I am builing a lambda with the quarkus-amazon-lambda extension alongside the quarkus-opentelemetry extension using the latest Quarkus version 2.16.1.Final. I have noticed that the traceId and spanId is always logged out empty in the console logger

I have the following in my application.properties
quarkus.application.name=shipment-logger-service
quarkus.opentelemetry.enabled=true
quarkus.opentelemetry.tracer.exporter.otlp.endpoint=http://localhost:4317
quarkus.log.console.format=%d{HH:mm:ss} %X %-5p traceId=%X{traceId}, parentId=%X{parentId}, spanId=%X{spanId}, sampled=%X{sampled} [%c{2.}] (%t) %s%e%n

However, the traces are being exported successfully to my Jaeger instance running on localhost so the issue here is just that the traceId and spanId is missing from the actual console log/json log. I have also tried deploying my lambda into AWS and the same problem persists there. I have been following the official documentation here https://quarkus.io/guides/opentelemetry but I seem to be unable to get this working with the logging framework. Is there any documentation anywhere I can look into to make this work?