cost-observability

id	SKL-cost-COSTOBSERVABILITY
name	Cost Observability
description	Cost Observability is practice of extending traditional system observability (logs, metrics, traces) to include **Financial** data. It allows engineering teams to answer not just "Is the system health
version	1.0.0
status	active
owner	@cerebra-team
last_updated	2026-02-22
category	Backend
tags	["api","backend","server","database"]
stack	["Python","Node.js","REST API","GraphQL"]
difficulty	Intermediate

Cost Observability

Skill Profile

(Select at least one profile to enable specific modules)

• DevOps
• Backend
• Frontend
• AI-RAG
• Security Critical

Overview

Cost Observability is practice of extending traditional system observability (logs, metrics, traces) to include Financial data. It allows engineering teams to answer not just "Is the system healthy?" but "Is the system cost-effective?"

Core Principle: "Total spend is a vanity metric; cost per unit of work is a performance metric."

Why This Matters

• Cost Visibility: Understand where money is being spent
• Attribution: Assign costs to teams and projects
• Anomaly Detection: Identify unusual spending patterns
• Optimization: Identify areas for cost reduction

---

Core Concepts & Rules

1. Core Principles

• Follow established patterns and conventions
• Maintain consistency across codebase
• Document decisions and trade-offs

2. Implementation Guidelines

• Start with the simplest viable solution
• Iterate based on feedback and requirements
• Test thoroughly before deployment

Inputs / Outputs / Contracts

• Inputs:
  • Cloud billing data
  • Resource tags and metadata
  • Application metrics and traces
  • Business unit mappings
• Entry Conditions:
  • Cost tracking enabled
  • Tagging strategy implemented
  • Monitoring configured
• Outputs:
  • Cost dashboards and reports
  • Anomaly alerts
  • Attribution reports
  • Chargeback/showback data
• Artifacts Required (Deliverables):
  • Cost dashboards