/

/

Datadog costs, allocated and explained

Datadog costs, allocated and explained

Observability

Datadog costs, allocated and explained

Datadog usage and billing estimates (+ metrics and CI Visibility)

How Costory connects to Datadog

Costory turns Datadog product usage into cost rows using a Datadog API key and application key with usage_read and billing_read. timeseries_query is optional, for querying Datadog metrics with the same integration.

The cost is an estimate built from Datadog usage and billing endpoints, shown in Explorer next to your cloud bills.

Step by step: Datadog setup in the Costory docs.

Questions you can ask

  • “Why did our Datadog bill move this month?”

  • “Correlate the cost spike with Datadog traffic metrics.”

  • “Show Datadog CI spend by pipeline.”

Good to know

Datadog billing is an estimate until invoiced; compare against usage.

Official tooling

Datadog also has its own tooling: Datadog MCP (cost toolset). Costory adds cross-provider allocation and event context on top. Compare options.

Use Datadog with your AI assistant

Setup guide: Datadog in the Costory docs.

In Costory

Datadog cost in the product

Screenshots from the Costory app with this integration connected.

Explorer filtered to Datadog, grouped by service name
Explorer filtered to Datadog, grouped by service name

Explorer filtered to Datadog, grouped by service name

Datadog metrics in Costory, including CI execution time
Datadog metrics in Costory, including CI execution time

Datadog metrics in Costory, including CI execution time

Datadog metric render.service.network.receive.bytes grouped by service name
Datadog metric render.service.network.receive.bytes grouped by service name

Datadog metric render.service.network.receive.bytes grouped by service name

Skills

Skills that use Datadog

What the Costory agent can watch, investigate and report on for you, with this in the loop.

All skills

Costory notices

Daily, as Datadog usage and the EKS bill refresh.

Dynamic cost reallocation for EKS using Datadog usage

Split shared EKS cluster costs across teams in proportion to what each team's workloads actually use, measured in Datadog.

See the skill

Costory notices

A service runs well below its capacity for 30 days.

Rightsizing recommendations grounded in real usage

The agent compares what you pay for compute with what services actually use in CloudWatch or Datadog, then recommends instance sizes to the owning team, with the deploy history attached.

See the skill

Costory notices

An anomaly is detected, any time of day.

Investigate anomalies in a Slack thread with Costory

When an alert fires in #finops or a team channel, reply in the thread and @Costory investigates: which team, which service, which deploy.

See the skill

Costory notices

A shared API or platform bill lands without an owner.

Split shared API costs across teams with usage data

Allocate untagged or shared API costs, like a single LLM key or a shared data platform account, to teams based on actual usage.

See the skill

Costory notices

Every week, across every connected provider.

One showback across AWS, Google Cloud, Azure, AI and data platforms

Teams see all their costs in one place, whatever the provider: cloud, Kubernetes, data platforms and LLM APIs.

See the skill

Costory notices

Idle capacity in a node pool stays above your threshold.

Find over-requested Kubernetes workloads and right-size requests

Measure the gap between requested and available CPU and memory, convert it to cost, and get request changes per deployment.

See the skill

Connect in under 30 minutes, get your first optimization recommendation the next day.

30-day free trial. Plans from €250/month, billed annually. We recommend Team (€600/month) once more than one team uses Costory.

First optimization recommendation

The next day

PRICE

From 250€/month, never a % of your bill

Setup

Under 30 minutes

Data residency

EU

Access

Read-only on your cloud

From 250€/month, never a % of your bill. 30 days free, no credit card.