Atlas External Log Sink to GCS
Parent: MongoDB Atlas on GCP · Published reference · snapshot 2026-10-29
↓ Facts as markdownall context files
Source-anchored research for Atlas External Log Sink to GCS. 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
- Destination retention is an implementation responsibility. Google documents bucket retention policies that block premature deletion or replacement, and irreversible policy locking. These GCS controls are not evidence that enabling Atlas export automatically configures immutable retention. (low confidence) (verified as of 2026-10-26) [source]
Problems, failure modes and limitations
- GCS export failure notifications are informational: Atlas emails Project Owners and records them in the Project Activity Feed; they do not appear in the Open or Closed Alerts tabs. (low confidence) (verified as of 2026-10-14) [source]
- Project Activity Feed events can export to GCS, and event-only export does not require M10+. The event documentation separately states no automatic replay, historical backfill, or failure alerts in the initial release; system-log recovery must not be assumed for events. (low confidence) (verified as of 2026-10-14) [source]
Facts and statements
- Atlas documents one-minute GCS export of mongod, mongos, mongod-audit, and mongos-audit logs; the feature is broader than audit-only export. (low confidence) (verified as of 2026-10-14) [source]
- The GCS procedure requires an M10+ cluster running MongoDB 7.0 or later and Atlas Project Owner or Organization Owner access. (low confidence) (verified as of 2026-10-14) [source]
- GCS setup selects a Google Cloud service account, a bucket name, prefix path, and log types, then assigns an IAM access policy and validates the configuration. (low confidence) (verified as of 2026-10-14) [source]
- The GCS integration supports up to ten export paths, including simultaneous export to multiple GCS buckets. (low confidence) (verified as of 2026-10-14) [source]
- Pulumi documents GCS_LOG_EXPORT with bucketName, prefixPath, roleId and logTypes, and shows GCP cloud-provider access setup and authorization. This is an automation example, not a delivery test. (low confidence) (verified as of 2026-10-27) [source]
- Atlas warns that network issues or retries can produce duplicate exported log entries. Consumers should not assume exactly-once delivery. (low confidence) (verified as of 2026-10-14) [source]
- The general system-log exporter documents retries, a per-sink circuit breaker, seven-day dead-letter retention and automatic replay after recovery; queued logs older than seven days are deleted. The employee announcement corroborates recovery only broadly, without a GCS-specific test. (low confidence) (verified as of 2026-10-14) [source]
- MongoDB documents external-log egress through the Atlas control plane in AWS us-east-1, regardless of cluster cloud or region. GCP placement therefore does not establish an entirely GCP-local log path; cross-cloud transfer charges can apply. (low confidence) (verified as of 2026-10-14) [source]
Children
- No children recorded.