Observability metrics
Tsuga metrics next to your cloud costs
Tsuga metrics
What Costory does with Tsuga
Tsuga adds the usage side: metrics, log aggregates such as error rate and trace aggregates such as p99 latency. The agent puts those series next to cost to compute unit costs, split shared spend by real usage and explain why a service got more expensive, in Slack or from Claude through the Costory MCP.
Setup in short
Create a read-only Operation API key in Tsuga (it starts with tsuga_, ingestion keys are not used) and connect your workspace from the Tsuga tile in Costory. Data is queryable as soon as it validates, with history matching your Tsuga retention.
How it is used
Add a Tsuga metric in Advanced Explorer, group by attributes or narrow it with a Tsuga filter (per service or environment for example), and use it as the driver when splitting a shared cost.
Questions you can ask
“Plot our cost next to Tsuga request volume.”
“Which service's cost grew faster than its traffic?”
“Compute cost per 1,000 requests by service.”
Full setup guide: Tsuga in the Costory docs.
Skills
Skills that use Tsuga
What the Costory agent can watch, investigate and report on for you, with this in the loop.
All skills
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
Spend on a team, service or account deviates from its baseline.
Investigate a cost spike and find the deploy behind it
When spend moves, the agent finds the deploy, team and service behind it, checks incidents and provider events from the same window, and posts the likely cause.
See the skill
Costory notices
A team's forecast crosses a budget threshold.
Team budgets with forecast-based alerts
Monthly budgets per team, with Slack or email alerts when actual spend or the end-of-month forecast crosses a threshold.
See the skill
Costory notices
Every Monday.
A weekly optimization shortlist posted to each team's channel
Every Monday, each team gets three optimization candidates for its own services, with evidence, in its Slack channel.
See the skill
Costory notices
A shared service's cost grows, or a new team starts using it.
Split shared infrastructure costs by actual usage
Allocate shared databases, networking and platform services to the teams that use them, based on real usage metrics.
See the skill
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

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.
