Datadog spend by product and team
Import Datadog usage and billing estimates, then allocate observability spend to the teams generating it.
Runs in
Claude · Slack
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Playbook
What the agent does
From what Costory notices to what you decide. Costory suggests the next step in conversation, and you decide whether to go ahead.
Costory notices
A Datadog product line grows faster than usual.
Context used
Remembered
Costory investigates
01
Connect Datadog
Usage and billing estimates, from the same integration as Datadog metrics.
02
Put in context
Datadog standard metrics per service, from the same integration, show which services drive each product line before it is allocated.
03
Break down
By Datadog product: logs, APM, infrastructure, custom metrics.
04
Allocate
Rules or usage-based splits to teams.
05
Watch
Alerts on sudden usage growth.
Where you see it
Claude
You decide
Teams decide on log levels, retention or sampling.
Why it matters
Observability bills grow with every new service and log line. Without allocation, they land in the platform budget.
Who it’s for
Platform teams, SREs, FinOps leads
Where it runs
Claude · Slack
What you get
What lands in front of your team
Observability, owned
Teams see their share.
Product-level detail
Logs vs APM vs infrastructure.
Early warning
Alerts on usage spikes.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
FAQ
Questions about this playbook
Which platforms are supported?
Snowflake, BigQuery, Datadog, Confluent, Aiven, Elastic Cloud, ClickHouse, Cloudflare and more, plus any FOCUS-formatted billing data in BigQuery.
How long does this playbook take to set up?
Connecting your billing data and the Costory MCP takes under 30 minutes with Terraform or CloudFormation. The playbook itself takes minutes: pick the scope, the trigger and the Slack channel. The first billing data lands the next day, and the agent starts from there.
Can we adjust what the agent does?
Yes. You choose the trigger, the scope (team, service, environment), the channel and the format, and you can pause or change it at any time.
Does Costory change anything in our cloud accounts?
No. Costory reads billing exports and the metrics you connect, and has no write access to your cloud. Actions it takes create Costory objects only: alerts, reports, dashboards and events. Your team stays in control of every change.
Step-by-step guide in the Costory docs
Related playbooks
Run these alongside it
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 playbook
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 playbook
Put this playbook on call
Included in every plan, from €250/month. 30-day free trial: connect in under 30 minutes, get your first optimization recommendation the next day.
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Setup
About 30 minutes
Data residency
EU
Access
Read-only on your cloud