v1
latestOpenAPI 3.1.0BSD-32026-07-2471176175.5 KBPost telemetry records
Allocation telemetry provides additional information that the CloudZero system can use to split your cloud cost data through custom allocation dimensions. In this way, you can gain further insights into the costs of your multi-tenant systems, shared infrastructure, and more.
The telemetry_stream_name sent to this API can be used in the Streams parameter of an AllocateByStreams custom dimension (see https://docs.cloudzero.com/docs/allocation-short-form-rules#allocatebystreams-short-form-rule)
Note: This endpoint is the legacy version of /unit-cost/v1/telemetry/allocation/{telemetry_stream_name}/sum. It is functionally identical, but predates the operational path parameter concept.
Path parameters
A unique name to identify this telemetry stream. Best practice is for this to reflect the metric being used to measure utilization and its units. Only alphanumeric characters are allowed along with "_", ".", and "-".
- i.e. gigabyte-seconds-for-x-feature, count_of_records_in_x_database, bytes-consumed-in-x-feature
Headers
Your CloudZero API Key. Note: This is not a bearer token, and should appear in the header as Authorization: <cloudzero-api-key>
Request body
Example request
{
"records": [
{
"value": 16.4,
"timestamp": "2020-03-03T15:32:44+00:00",
"element_name": "Adidas"
}
]
}Response
Telemetry accepted