Increasing Visibility with Cloud Costs
summary
Relativity instruments Kubernetes spend with Harness, beta testing and shaping features like perspectives, recommendations, budgets and anomaly detection so costs map to teams and labels. Budgets trigger alerts and cut variance — a reported 20% reduction in month one and 45% reduction after three months — while recommendations use percentile histograms to suggest resource-rightsizing and anomalies surface unexpected spikes for postmortem notes and action.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:08Cloud journey and costs
- 3:15Product managers and costs
- 4:37On-prem vs cloud costs
- 5:40Stakeholders in cost management
- 6:23Harness Cost dashboard
- 7:29Team-specific cost views
- 9:35Budgets for predictability
- 12:21Cost optimization in Harness
- 14:49Anomaly detection and trends
- 17:16Key takeaways
related talks
20mCloud Cost Management Updates
40mCloud Costs Panel "Lots of Reward Points"
19mBuilding Cost Visibility For Your Kubernetes Clusters
35mWhy Kubernetes Can't Get Around FinOps – Cost Management Best Pra...
26mBuilding Cost Visibility For Your Kubernetes Clusters
34mOptimizing Cloud Efficiency with Prompt Engineering
12mHow Unit Costs will change the way you think about your cloud bill
46mCloud cost chaos? Get clarity with FinOps cloud cost management
