Organization-scoped alert configuration API
Parent: Admin API alert configurations for billing events · Published reference · snapshot 2026-10-24 · skill mongodb-cohort-32c3803915b5
↓ Facts as markdownall context files
Source-anchored research for Organization-scoped alert configuration API. 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.
Problems, failure modes and limitations
- In a February 8, 2024 report against Terraform provider v1.15.1, DAILY_BILL_OVER_THRESHOLD configuration failed with "metric_name" required, and importing a UI-created resource panicked in NewTFThresholdConfigModel. This historical provider report does not prove a current server-side limitation or organization-scoped API support. (low confidence) [source]
Comparisons and alternatives
- The reviewed project-create schema includes a Billing Threshold Alert Configuration variant with PENDING_INVOICE_OVER_THRESHOLD, DAILY_BILL_OVER_THRESHOLD, and daily, weekly, and monthly billing-change event types. It uses threshold with GREATER_THAN and RAW rather than requiring a host metric name. (low confidence) (verified as of 2026-10-21) [source]
Facts and statements
- Atlas documents organization billing alerts through the Organization Alerts UI; organization alerts and project alerts have separate scope and access requirements. (medium confidence) (verified as of 2026-10-23) [source]
- The reviewed Admin API create operation is POST /api/atlas/v2/groups/{groupId}/alertConfigs and identifies groupId as a project ID. Compyl independently documents collecting alert configurations using the corresponding project-scoped GET route. (high confidence) (verified as of 2026-10-23) [source]
- An ORG notification target identifies organization recipients; its presence inside the project create schema does not establish an organization-scoped configuration endpoint. Resource scope and recipient scope must be checked separately. (medium confidence) (verified as of 2026-10-23) [source]
- The organization-alert UI documentation requires Organization Owner for all organization alerts and grants Organization Billing Admin limited authority over billing alerts. This does not by itself specify authorization for an unverified organization alert API. (low confidence) (verified as of 2026-10-23) [source]
- Cloudaware documents its own Atlas billing integration as organization-scoped invoice and billing-report ingestion. That integration supplies evidence for billing-data access, not for creating organization alert configurations. (low confidence) (verified as of 2026-10-23) [source]
- Compyl documents Project Read Only as sufficient for its MongoDBAtlasAlertConfigs collector. That read-only project collector is distinct from organization billing-alert administration. (medium confidence) (verified as of 2026-10-23) [source]
Children
- Alert configuration resource scope versus notification recipient scope (frontier)
- Organization billing-alert API authorization (frontier)
- Billing threshold schema and Terraform provider compatibility (frontier)
Frontier under this node: Alert configuration resource scope versus notification recipient scope, Billing threshold schema and Terraform provider compatibility, Organization billing-alert API authorization