AEM as a Cloud Service: Delay in log stream availability after midnight UTC
This article explains the temporary unavailability of Adobe log streams after daily UTC log rotation in AEM as a Cloud Service, which causes AIO tail:logs connection failures and a gap in real-time log visibility.
Description description
Environment
Adobe Experience Manager as a Cloud Service (all versions)
Issue/Symptoms
- After the daily log rotation at 00:00 UTC, Adobe log streams are unavailable for 15–40 minutes.
- During this window, attempts to connect with AIO
tail:logsfail, and real-time logs for the start of the day are not accessible. - Connection attempts between 00:06 and 00:30 UTC typically fail, with successful connections resuming around 00:35 UTC.
- All log entries are eventually available for retrieval once the stream is restored.
- No specific error message is returned by AIO
tail:logs; the connection simply fails until the stream becomes available.
Cause
The delay occurs because the log-serving endpoint waits for the previous day’s archive file to be created before assigning the new day’s live stream, resulting in a temporary gap in real-time log stream availability after midnight UTC.
Resolution resolution
Follow the steps below to resolve the issue:
- Be aware that Adobe log streams rotate at 00:00 UTC daily, but the new day’s live stream may not be immediately available.
- Schedule your AIO
tail:logsscripts to reconnect after 00:30–00:35 UTC to ensure the new day’s log stream is available. - Avoid attempting to connect immediately after midnight, as this may result in being pointed to the previous day’s stream.
- Monitor log stream availability and adjust your script timing as needed.
Note: All log entries during the delay window are captured and can be retrieved once the new day’s stream is available. The issue is limited to real-time streaming and does not result in data loss.
recommendation-more-help
experience-cloud-kcs-help-kbarticles