1. Proposed title of this feature request process to change logrotate retention time 3. What is the nature and description of the request? Customer needs to be able to retain logs collected in their dedicated cluster for a longer period of time. We need a process by which the customer can request a logrorate retention period. As this may require considerations on storage, this may also need attention from the perspective of the account, in addition to just the technical. 4. Why does the customer need this? (List the business requirements here) Needs longer period of logs for troubleshooting, debugging, auditing, or other processes
Hi, I have a customer that is waiting for a response on this case since it was opened. Do we have any expectation on when we are going to have a resolution for this? I really want to avoid a customer escalation. case: 01956962 Thanks, Guilherme Camposo TAM - Middleware
Hi, I apologize for this request getting lost and the delay in response. The logging stack provided with OpenShift Dedicated is designed for short term retention to help troubleshoot application issues. We have seen longer retention times lead to performance and log data availability problems. Our recommendation for long-term log storage is to forward logs to a dedicated log aggregation product from you application using a sidecar container (https://kubernetes.io/docs/concepts/cluster-administration/logging/#using-a-sidecar-container-with-the-logging-agent). We are planning to include an integrated log forwarding component in a future release, but do not have a time frame for that today. Please work with your account team or TAM to stay updated on our roadmap. Sincerely, Patrick Strick Product Manager, OpenShift Dedicated