Observability integration

Datadog

Ingest Datadog usage and cost so observability spend is governed with the same budgets, anomaly detection, and FinOps Agent workflows.

Available on request. We're prioritizing AWS, Azure, GCP, and Oracle Cloud billing first. Datadog usage ingestion is available for design partners on request — talk to us to prioritize your account.

Connection

Datadog Usage API (read)

Access model

Read-only

Time to value

Usually within an hour of API key validation

How OptCloud connects with Datadog

Datadog bills on product usage (hosts, custom metrics, logs indexed, APM spans, etc.). OptCloud uses the Usage and Cost Attribution APIs with an API key that can read usage — not modify monitors or dashboards — then surfaces trends, spikes, and budget alerts alongside cloud infrastructure cost.

Required permissions

API key with usage_read (or equivalent usage/billing scopes)
Application key if required by your Datadog org for usage endpoints
No dashboard, monitor write, or log content read scopes

OptCloud reads aggregated usage and cost attribution, not your raw log payloads.

Create a connection

1
Create an API key for OptCloud
In Datadog Organization Settings, create an API key dedicated to OptCloud. Restrict scopes to usage/billing read where your plan allows.
2
Create an application key if required
Some usage endpoints need an application key tied to a service account user with billing read.
3
Connect in OptCloud
Add account → Datadog. Enter site (US1, EU, etc.), API key, and application key.
4
Map Datadog orgs to FinOps dimensions
If you run multiple orgs or child orgs, assign them to the right OptCloud workspace.
5
Validate product breakdown
Confirm hosts, custom metrics, logs, and APM appear as separate cost lines matching Datadog’s usage UI.