Summary
On August 14, 2025, we had intermittent issues with delayed log ingestion. During these periods of delayed log ingestion, customers may not have seen their logs from the past 1 to 2 hours on logs.fr.cloud.gov. We believe we have now identified and fixed the cause of delayed log ingestion, so we do not expect the problem to recur.
Timeline
Impact
Intermittently, customers may not have seen their logs appearing on logs.fr.cloud.gov in real time. Logs may have been delayed from appearing for 1 to 2 hours. While there were delays in logs appearing on logs.fr.cloud.gov, there was no loss of logs.
Root Cause
While investigating the second case of delayed log ingestion, we discovered that the log ingestion was being over-allocated to a specific data node, which overwhelmed that node’s CPU resources and caused the delays in log ingestion. To fix this issue, we updated a setting in OpenSearch that controls how many shards can be allocated to a single node for each index, which allowed data ingestion to be distributed more evenly across all of the data nodes.
Since making the change to shard allocation, log ingestion rates have remained stable and logs have been ingested in near real-time.
Next Steps
Thank you for your patience. If you have any questions, please contact us at support@cloud.gov.