AWS_XRAY_CONTEXT_MISSING configuration override INFO logs persist after removal

[balaravichandran097]

I am encountering an issue where the AWS_XRAY_CONTEXT_MISSING environment variable override INFO LOG is still reflected in the cloudwatch logs, even though it has been removed from the serverless.yml configuration. This behaviour occurs everytime when lambda coldstarts

Cloud watch logs:

INIT_START Runtime Version: java:21.v27 Runtime Version ARN:
| 2024-12-12T15:33:16.691+05:30 | Dec 12, 2024 10:03:16 AM com.amazonaws.xray.AWSXRayRecorder
INFO: Overriding contextMissingStrategy. Environment variable AWS_XRAY_CONTEXT_MISSING has value: "LOG_ERROR".
even after the environment AWS_XRAY_CONTEXT_MISSING is removed from serverless.yml not sure it was the default behaviour.

expected behaviour:
INFO logs should not be generated, as they are misleading since the AWS_XRAY_CONTEXT_MISSING configuration is not present in the serverless.yml file."

library version:

com.amazonaws
aws-xray-recorder-sdk-core
2.15.3


com.amazonaws
aws-xray-recorder-sdk-aws-sdk
2.15.3

[srprash]

Hello @balaravichandran097
Logging the context missing error is the default behavior. You can set the environment variable AWS_XRAY_CONTEXT_MISSING=IGNORE_ERROR to avoid logging it completely.
More info on this doc: https://docs.aws.amazon.com/xray/latest/devguide/xray-sdk-java-configuration.html#xray-sdk-java-configuration-envvars