Source boundary
Datadog
Confirm source eligibility in your workspace before creating access.
- Financial source
- Estimated current-period and settled historical cost or usage reports
- Reviewed
- 2026-09-17
- Cost bases
- net, billed, credits
- Useful dimensions
- organization, sub-organization, product, pricing category, cost status
Known limits
- Current-period estimates are provisional.
- Settled historical cost supersedes earlier estimates when available.
Prepare the connection
Eligibility
A parent or root organization with the reporting entitlement and a supported Datadog site is required for organization cost reporting.
Authorize usage and billing read access for the selected Datadog site, or provide scoped API and application keys.
Authentication choices
- Datadog authorization — recommendedPruneFox stores the credential encrypted in the isolated credential broker and never returns it to the browser.
- API and application keysPruneFox stores the credential encrypted in the isolated credential broker and never returns it to the browser.
Connection details
| Field | Why it is needed | Example format |
|---|---|---|
| Datadog site | Choose the exact site that hosts the organization. | Choose a Datadog site |
Permission boundary
| Resource | Read or bounded staging permissions | Purpose |
|---|---|---|
| Selected Datadog organization | usage_read, billing_read when required | Read usage and cost reporting without monitors, dashboards, integrations, users, or organization mutation. |
Connection sequence
- Identify the exact Datadog site and parent/root organization.
- Confirm historical-cost eligibility and required scopes.
- Create dedicated scoped keys.
- Enter the site and keys, then validate organization identity and each cost capability separately.
Validation and first sync
Validation rejects a site mismatch, unsupported custom host, child organization without required parent access, missing scope, or unavailable historical-cost capability.
Historical finalized cost anchors closed periods; estimated and projected current-period values are stored as non-authoritative coverage and never overwrite finalized totals.
Freshness: Estimated cost can be delayed by up to the provider-documented window and is never labelled finalized.
Remove access
Revoke the PruneFox connection, then revoke the application key/API key or delegated grant.
Troubleshooting
Check site, parent organization, reporting entitlement, scopes, period type, and whether the value is estimated, projected, or finalized.
Verify the first completed period
Compare one bounded completed period with the provider billing source. Match currency and cost basis, inspect credits and adjustments, and confirm that missing dimensions remain unavailable rather than zero.
Troubleshoot safely
Use the visible connection state, provider name, affected date range, and expected outcome. Never send credentials, raw billing exports, payment data, or customer records through support.