aws / aws/aws-lambda-java-libs
Support log4j Custom ContextDataProvider?
- Dominant language
- Java
- Stars
- 548
- Forks
- 241
- Avg merge
- 2d 5m
- Merged PRs (30d)
- 11
Description
I tried a get a custom log4j `ContextDataProvider` (see [log4j doc](https://logging.apache.org/log4j/2.x/manual/extending.html#ContextDataProvider) to work but to no avail.
From the log4j doc, this mechanism relies on `java.util.ServiceLoader` to locate and load `ContextDataProvider` instances.
Is this a restriction of the Corretto VM in AWS Lambda for Java?
I tested this with https://github.com/dynatrace-oss/log4j-metadata-provider.
Contributor guide
Research direction
Start with the Log4j ContextDataProvider documentation and the dynatrace-oss/log4j-metadata-provider example named in the issue, then inspect how java.util.ServiceLoader behaves in an AWS Lambda Java runtime. Done means determining whether custom providers are supported and, if not, defining the required change or documenting the limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100