Atlas log-export replay destination changes and failure-state observations
Parent: Atlas External Log Sink to GCS · Published reference · snapshot 2026-11-02
↓ Facts as markdownall context files
Source-anchored research for Atlas log-export replay destination changes and failure-state observations. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Definitions
- `LOG_STREAMING_EXPORT_RECOVERED` means queued logs are ready to resume sending. The event reference marks it non-alertable, and the log-export overview lists recovery readiness as an informational Project Activity Feed event. (medium confidence) (verified as of 2026-11-02) [source 1] [source 2]
- `LOG_STREAMING_REPLAY_STARTED` means queued logs are now being sent. The event reference marks it non-alertable, and the log-export overview lists this sending state as an informational Project Activity Feed event. (medium confidence) (verified as of 2026-11-02) [source 1] [source 2]
- `LOG_STREAMING_REPLAY_COMPLETE` means all queued logs have been delivered to the sink. The event reference marks it non-alertable, and the log-export overview lists delivery completion as an informational Project Activity Feed event. (medium confidence) (verified as of 2026-11-02) [source 1] [source 2]
How it works
- The retries-exhausted alert triggers after delivery retries are exhausted; its message says logs are being queued and will be sent once the connection is restored. The event reference identifies it as alertable `LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED`. (medium confidence) (verified as of 2026-11-02) [source 1] [source 2]
Problems, failure modes and limitations
- The non-retryable failure alert triggers immediately for an error such as invalid credentials or a misconfigured sink. The event reference identifies this alertable condition as `LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE`. (medium confidence) (verified as of 2026-11-02) [source 1] [source 2]
- The replay-failure alert concerns automatic replay from the DLQ failing after an automatic retry attempt. The alert-conditions documentation tells users to contact MongoDB Support to request manual redelivery and warns that undelivered records will be permanently deleted when their retention window expires. (medium confidence) (verified as of 2026-11-02) [source 1] [source 2]
- For Activity Feed event export, the pinned Delivery Behavior section explicitly labels the initial release as having no automatic replay, backfill or failure alerts. It says persistent failures do not automatically replay events, historical events from before integration configuration are not backfilled, and users should contact MongoDB Support to request redelivery after a persistent failure. This scopes the system-log replay behavior separately from event export. (low confidence) (verified as of 2026-11-02) [source]
Comparisons and alternatives
- In the pinned Atlas system-log documentation, modifying the sink configuration while logs are queued in the DLQ makes replay use the new configuration. The documented example changes the destination between S3 buckets: queued logs go to the new bucket rather than the original destination. (low confidence) (verified as of 2026-11-02) [source]
Children
- No children recorded.