Map traffic before you commission another API dashboard
A polished percentile chart on untagged routes only accelerates the wrong debate.
Teams under pressure often skip route and consumer tags and jump to a new traffic board. Weeks later, product and platform argue over different totals for the same gateway because every call still shares one opaque identity.
Prefer consumer and release tags over UI widget names. Keep environment out of the route alias and in a property. Write allowed values the same day a new endpoint ships—or the path becomes a free-form dump.
In an API Traffic Baseline Audit we spend early days on the inventory, not on chart cosmetics. Dashboards get sharper only after the traffic map stops arguing with itself.