Why this matters
Telemetry streams carry the unit metrics behind every cost-per-unit number you report. Now each one can say in plain language what it measures.
You can call a stream whatever you want to: “MCP tool calls” or “Checkout transactions” or “Documents processed.” Spaces, capitals, and punctuation all work, and you can change the name whenever the metric’s purpose gets clearer. The identifier the pipeline uses stays exactly where it is.
That readability starts to pay as soon as you build a unit cost view. You pick a stream from a list to get cost per unit, and a name written for people tells you immediately which one you want. The number you produce is right because the input was obvious.
A product lead reviewing the cost of a feature by daily active users, or a CFO reading AI cost per completed task, sees “Cost per Support Request” and knows what they are looking at.
Editable names also let your streams keep up with your naming conventions. When a team renames a service, or your metric catalog standardizes on a phrasing, you update the display name in CloudZero. Collection keeps running, history stays intact, and everyone downstream sees the new name.
What we built
Telemetry streams now carry a display name along with an identifier. The API and the ingestion pipeline use the identifier, and it stays stable.
The display name is optional free text and it appears throughout the UI. Write it the way you would say it. Edit it any time. Changing it leaves the identifier, the ingestion, and historical data points untouched.
How it works
Go to Settings, then Telemetry Streams. Create a stream or open an existing one and set the display name. It appears everywhere the stream is shown.
