Transformer - Enhance Transformer Logging Root Cause Detection
Current Transformer Logs like "GET COUNT EXCEPTION" or "CACHE NOT INITIALIZED" point generally to areas of the code but could be improved with more specific references to aid in troubleshooting.
Additionally, log4j.yml does not make use of environment variables to set log level (info, trace, etc.), but this would be a valuable enhancement for Kubernetes deployments since modifying the file directly is an anti-pattern.
Finally, please note in documentation the location of Transformer app.log in Kubernetes environment to be in the Transformer pod's logs/app.log
directory.
Acceptance Criteria:
- Exception messages should include stack trace