Hybr CCDF - Usage Data Format

This document describes the structure of the Common Cost Data Format (CCDF). This format is used to push usage to the Hybr platform from any external source such as GCP, OpenAI, or other service providers.

Overview

Each record in the CCDF represents a usage entry over a specified aggregation period. The format is designed to be extensible and vendor-agnostic, enabling integration with various providers.

Data Fields

Field Name
Description
Example

SourceSubscriptionAccountProjectId

Unique identifier such as subscription ID, project ID, or account ID from the source system.

gcp-project-123

SourceSubscriptionAccountProjectName

Human-readable name of the subscription, project, or account from the source system.

GCP Project Alpha

SourceUsageProvider

Name of the usage data provider.

OpenAI, GCP

SourceUsageService

Category of the service being used.

Virtual Machine, Storage

SourceUsageMeterName

A unique identifier for the usage meter. Usually a combination of model/service name and usage metric.

gpt-3.5-turbo_InputAudioTokens

SourceUsageQuantity

The quantity of usage recorded.

3560

SourceUnitOfMeasure

Unit in which the usage is measured.

tokens, GB, hours

AggGranularity

Aggregation level of the usage record.

Daily, Monthly

AggStartDate

Start datetime of the usage aggregation window. ISO 8601 format recommended.

2025-04-01T00:00:00Z

AggEndDate

End datetime of the usage aggregation window. ISO 8601 format recommended.

2025-04-01T23:59:59Z

SourceAdditionalInfo

Additional info about the usage (must be json string)

"{"SampleAdditionalData":"JsonString"}"

SourceResourceFilterProperties

Properties used to filter a meter

"{"VMName":"Basic_A0"}"

Format Guidelines

  • All datetime fields should follow ISO 8601 format (YYYY-MM-DDTHH:MM:SSZ).

  • Ensure all string fields are UTF-8 encoded.

  • Quantity values should be numeric and non-negative.

Sample Data

Here’s a preview of a sample usage record in CSV:

Last updated