Showback design
Decide how to slice cost back to teams, split what is shared between them fairly, and put a cost-per-unit figure on the chart.
7 lessons. 1 quiz.
Read in order, or jump to what you need.
Organisation, Teams, Tags: pick the dimension
By the end of this lesson, you will be able to pick the right showback dimension based on the audience question, describe the underlying data source for each, and handle a question that needs more than one dimension.
Team attribution and shared resources
By the end of this lesson, you will be able to distribute shared-resource costs equitably across consuming teams, identify when equal split is wrong and what to change when it is, and drive the Unattributed bucket toward zero.
Tag attribution
By the end of this lesson, you will be able to attribute cost across any tag dimension (cost-center, environment, project, campaign), distinguish cloud-native tags from ZopNight's auto-tags, and know where tag attribution stops and team attribution starts.
Tag coverage card
By the end of this lesson, you will be able to read the Tag Coverage card, track it over time yourself, and execute a coverage-improvement plan that moves untagged resources from 30%+ down to under 5%.
Unit economics: cost per X
By the end of this lesson, you will be able to configure a unit metric in ZopNight, trace cost-per-X over time, and avoid the most common denominator and source-pipeline pitfalls.
Push, pull, CSV ingest
By the end of this lesson, you will be able to choose the right ingest path for unit-metric data, configure each path correctly, and reason about the SSRF guard on Pull API.
Unattributed spend and invoice reconciliation
By the end of this lesson, you will be able to explain why org totals include a residual that showback views do not, locate unattributed spend, and reason about CUR 2.0 and credit handling.
Module quiz.
Take it once the lessons are done.