Sum 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 functionally identical to the legacy /unit-cost/v1/telemetry/allocation/{telemetry_stream_name} endpoint.

Path Params
string
required

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
Body Params
records
array of objects
required

A batch of telemetry records to submit to CloudZero.

records*
Headers
string
required

Your CloudZero API Key. Note: This is not a bearer token, and should appear in the header as Authorization: <cloudzero-api-key>

Responses
200

Telemetry accepted

400

Invalid request, specific responses for:

  • Invalid JSON
  • Invalid Schema: Unrecognized filter keys
  • Invalid Schema: Missing required fields
  • Timestamp too far into the future
  • All records in a stream must contain the same filter keys
  • All records in a stream must contain the same granularity as the stream's granularity
403

Not authorized, make sure you're using a valid API key in the header Authorization

429

Rate limit exceeded. The API enforces rate limiting on incoming requests. Retry after a short delay.

503

Service temporarily unavailable due to downstream capacity constraints. Retry after a short delay with exponential backoff.

Language
Response
Click Try It! to start a request and see the response here!