Bug 1505544

Summary:	[dedicated][RFE] process to change logrotate retention time
Product:	OpenShift Online	Reporter:	Steven Walter <stwalter>
Component:	RFE	Assignee:	Abhishek Gupta <abhgupta>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.x	CC:	abhgupta, acavalla, guilherme.camposo, mirollin, mruzicka, mtaru, pportant, pstrick
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-23 17:39:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Steven Walter 2017-10-23 20:22:35 UTC

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

Comment 4 guilherme.camposo 2018-06-19 21:36:06 UTC

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

Comment 8 Patrick Strick 2019-09-23 17:39:24 UTC

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