Difference of behavior between JVM and Native builds

[KaranAhlawat]

Hello, I'm trying to log CloudWatch metrics to stdout.
I setup the relevant code, and when testing in dev, the logs are as expected.

Here is the relevant code -

public class MetricsService {
    MetricsLogger metricsLogger;

    public MetricsService() {
        var namespace = ConfigProvider.getConfig()
                .getOptionalValue("aws.emf.namespace", String.class)
                .orElse("OceanAnalytics");
        this.metricsLogger = new MetricsLogger().setNamespace(namespace);
    }
}

I then proceed to build the images, one for JVM and one for Native. The amazon-lambda extension is being used. And I'm using the following commands
For jvm -

./mvnw clean package

For native

./mvnw clean package -Dnative=true

When I run the app using the provide SAM template, the JVM one produces the expected logs.
However, the Native one always logs an empty object as {}.

Any ideas what may be going wrong? I really can't figure it out and it hurts observability a lot

[KaranAhlawat]

Interesting to note, if you use the jar produced by the second command for running the local SAM app, it also logs {} only.

I tried adding my MetricsService class to --initialize-at-run-time in the native image build additional args, but to no avail.