Measure before you commission another capacity pack
A polished utilisation chart on untagged change events only accelerates the wrong debate.
Teams under pressure often skip attribution fields and jump to a new capacity pack. Weeks later, platform and operations argue over different totals for the same release because every change still shares one opaque counter.
Prefer environment and service-family tags over widget names. Keep the reporting window out of the metric alias and in a property. Write allowed values the same day a new tool ships—or the surface becomes a free-form dump.
In an Infrastructure Reporting Baseline we spend early days on the inventory, not on chart cosmetics. Packs get sharper only after the measurement map stops arguing with itself.