In IBM Cloud Pak for Integration (CP4I) v2021.2, OpenShift Logging utilizes Elasticsearch as its log storage backend. The default configuration of the OpenShift Logging stack is optimized for short-term storage and is designed to retain logs for approximately 7 days before they are automatically purged.
Performance Optimization: The OpenShift Logging Elasticsearch instance is designed for short-term log retention to balance storage efficiency and performance.
Default Curator Configuration: OpenShift Logging uses Elasticsearch Curator to manage the log retention policy, and by default, it is set to delete logs older than 7 days.
Designed for Operational Logs: The default OpenShift Logging stack is intended for short-term troubleshooting and monitoring, not long-term log archival.
Why is the retention period 7 days?If longer retention is required, organizations can:
Configure a different retention period by modifying the Elasticsearch Curator settings.
Forward logs to an external log storage system like Splunk, IBM Cloud Object Storage, or another long-term logging solution.
A. 1 day – Too short; OpenShift Logging does not delete logs on a daily basis by default.
B. 30 days – The default retention period is 7 days, not 30. A 30-day retention period would require manual configuration changes.
D. 6 months – OpenShift Logging is not optimized for such long-term storage. Long-term log retention should be managed using external storage solutions.
Why Other Options Are Incorrect:IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References:
IBM Cloud Pak for Integration Logging and Monitoring
Red Hat OpenShift Logging Documentation
Configuring OpenShift Logging Retention Policy
Submit