Prometheus labels should read like filenames: short, intentional, and unlikely to duplicate across teams. We run critique sessions where learners defend their label choices to peers who pretend to be sleepy on-call engineers.
The exercise sounds cute until someone proposes customer_id as a label on a high-cardinality counter. Then the room tightens up, which is exactly the muscle we want trained early.
We also show how to admit uncertainty in dashboards. A panel titled “maybe saturation” is more honest than a panel that implies certainty with a slick gradient.
We do not integrate billing consoles in this material. Cloud cost ops vocabulary shows up where it helps you ask better questions of owners who hold the invoices.