Connector docs — Datadog
Exactly what CostMon asks for to read Datadog
CostMon calls Datadog's Usage Metering API: estimated_cost for the current and previous month, historical_cost for anything older the sync window reaches.
What CostMon calls
The literal API surface, nothing more
- GET /api/v2/usage/estimated_cost
- Freshest source, used for the current and previous month.
- GET /api/v2/usage/historical_cost
- Used for any month older than that, viewed sub-org.
What you supply
Credential and config fields
api_keyAPI keysecretrequired
app_keyApplication keysecretrequired
siteDatadog site (e.g. datadoghq.com)required
Minimum permission
Copy this, not a broader role
Scope of access
What Datadog access can't reach
- Metrics, logs, traces, or any monitored data
- Dashboards, monitors, or any Datadog configuration
Troubleshooting
Setup errors and what they mean
- api_key and app_key are both required
- Datadog's Usage Metering API needs both keys together. Neither works alone.
FAQ
Common questions about the Datadog connector
Can CostMon see the metrics or logs I'm sending to Datadog?
No. Both endpoints CostMon calls are Usage Metering cost reports, not data-access APIs. Your actual telemetry is never in scope.
Why do I need an Application key, not just an API key?
Datadog's Usage Metering endpoints require both together. This is a Datadog platform requirement, not a CostMon design choice.
A rate you looked up will change again.
Provider pricing pages change without notice. CostMon tracks the bill that pays for it.