AWS RequestId in logger MDC

[gquintana]

From what I see in this commit and the associated issue #24192
6942710
I should have the AWS Request ID in the logs MDC, but sadly it's not the case.

{
    "timestamp": "2023-08-18T12:45:04.322Z",
    "sequence": 306,
    "loggerClassName": "org.slf4j.impl.Slf4jLogger",
    "loggerName": "com.mycompany.http.exception.MyApplicationExceptionMapper",
    "level": "WARN",
    "message": "Error occured, returning status 404 in request '27b4353a-0863-4b1f-bd17-32ccf86f5bd1'",
    "threadName": "vert.x-eventloop-thread-0",
    "threadId": 38,
    "mdc": {},
    "ndc": "",
    "hostName": "unknown-host.unknown-domain",
    "processId": 698,
    "stackTrace": "jakarta.ws.rs.NotFoundException: Unable to find matching target resource method..."
}

@Temdegon I am wondering where I am wrong.
I am using quarkus-amazon-lambda-rest and quarkus-logging-json 3.2.4 and running as a natively compiled Amazon Lambda.

[gquintana]

Looking at the headers I receive in the JAXRS ContainerRequestContext:

	Accept: */*
	Accept-Encoding: gzip, deflate, br
	Content-Type: application/json
	Host: xxx.execute-api.eu-west-1.amazonaws.com
	transfer-encoding: chunked
	User-Agent: PostmanRuntime/7.32.3
	X-Amz-Content-Sha256: ...
	X-Amz-Date: 20230731T163009Z
	X-Amz-Security-Token: ...
	x-amzn-cipher-suite: ECDHE-RSA-AES128-GCM-SHA256
	x-amzn-tls-version: TLSv1.2
	x-amzn-vpc-id: ...
	x-amzn-vpce-config: 1
	x-amzn-vpce-id: ...
	X-Forwarded-For: ...

I don't have any Lambda-Runtime-Aws-Request-Id header