- All Implemented Interfaces:
- org.apache.logging.log4j.layout.template.json.resolver.EventResolver, org.apache.logging.log4j.layout.template.json.resolver.TemplateResolver<org.apache.logging.log4j.core.LogEvent>
public class LambdaTimestampResolver
extends java.lang.Object
implements org.apache.logging.log4j.layout.template.json.resolver.EventResolver
Default timestamp used by log4j is not RFC3339, which is used by Lambda internally to filter logs.
When `AWS_LAMBDA_LOG_FORMAT` is set to JSON (i.e. using Lambda logging configuration), we should use the appropriate pattern,
otherwise logs with invalid date format are considered as INFO.
Inspired from org.apache.logging.log4j.layout.template.json.resolver.TimestampResolver
TODO: remove in v2 an replace with the good pattern in LambdaJsonLayout.json