Skip to Main Content
Status Future consideration
Workspace * IBM Cloud Ideas
Created by Guest
Created on Jun 2, 2025

FP2027 Support log agent/network outages that exceed 24h without any data loss due to ICL dropping "outdated log entries"

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
  • Guest
    Jun 2, 2025

    Really important feature for our production-critical applications here in DACH