For our productive system we have the requirement to survive any downtime of up to 72h, so that on a failure that starts at Friday afternoon it can be solved on Monday morning without loosing data. This also includes log data. However, IBM Cloud Logs (ICL) backend rejects any log entries that are older than 24h (relative to current time). When the log agents e.g. stop running over the weekend or cannot connect to ICL due to network outages, likely all log data is still present in the CRI-O files or in the agent caches, however ICL will not accept any of the log entries that are older than 24h. This reduces the time window of outages without data loss to just 24h.
We request that ICL respective the OCP log agents support successfully delivering and storing delayed log entries for at least 72 hours.
| Idea priority | Urgent |
| Needed By | Month |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Really important feature for our production-critical applications here in DACH