kvssg123 commented on issue #3408: URL: https://github.com/apache/logging-log4j2/issues/3408#issuecomment-2613788390
Thank you for your response. We are currently using Log4j version 2.17.2. The issue occurs exclusively in our production clusters running on AWS EKS. We attempted to reproduce the problem in a controlled environment by generating dummy logs in a multi-threaded setup using the same Log4j2 configuration and version but were unable to replicate the behavior. Since this issue manifests only in production, it has been challenging to investigate without log redaction enabled. Additionally, these logs are exported to our ELK stack for further analysis. Is there an alternative way to debug this issue without directly experimenting in the production environment? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
