Linking CloudZero as a source

Contents

Note: This source is in alpha. It's fully functional but has not yet been tested against a wide range of CloudZero accounts.

The CloudZero connector syncs your cloud cost intelligence data – costs and dimensions – into PostHog, so you can analyze cloud spend alongside your product data.

Prerequisites

You need a CloudZero account and an API key with the following scopes:

  • billing:read_costs
  • billing:read_dimensions

To create an API key, go to Settings > API Keys in your CloudZero dashboard.

Adding a data source

  1. In PostHog, go to the Sources tab of the data pipeline section.
  2. Click + New source and click Link next to this source.
  3. Enter your credentials (see Configuration below) and click Next.
  4. Select the tables you want to sync, choose a sync method and frequency, then click Import.

Once the syncs are complete, you can start querying this data in PostHog.

When linking CloudZero, you'll need:

  • API key – a CloudZero API key with the billing:read_costs and billing:read_dimensions scopes. Create one under Settings > API Keys in your CloudZero dashboard.
  • Granularity – how to bucket cost data. Options: hourly, daily (default), weekly, monthly, yearly.
  • Cost type – which cost metric to sync. Options: billed_cost, discounted_cost, amortized_cost, discounted_amortized_cost, real_cost (default), on_demand_cost, invoiced_amortized_cost, usage_amount.
  • Group costs by dimensions (optional) – a comma-separated list of CloudZero dimension IDs to break costs down by (e.g. service,account). When set, each unique combination of dimensions produces its own row. You can find available dimension IDs by syncing the Dimensions table.

Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

  • Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
  • Incremental – only new or updated rows are synced on each run, using a cursor field (such as an updated_at timestamp). Cheaper than a full refresh, but deletes aren't captured.
  • Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
  • Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See sync methods for a full explanation of how each mode works and how to choose between them.

The Costs table supports incremental sync using the usage_date field. A built-in 7-day lookback window automatically re-syncs recent data on each run to capture any cost restatements CloudZero applies after the fact.

The Dimensions table only supports full table refresh because the CloudZero API does not expose a reliable timestamp filter for dimensions.

Configuration

Supported tables

The tables available from this source are discovered from your account when you connect it, so the exact list depends on your data. Once connected, you can pick which tables to sync from the sources tab.

Troubleshooting

Sync failing with a 403 or "Unauthorized" error

Your API key is invalid or missing the required scopes. Verify the key in Settings > API Keys in your CloudZero dashboard and confirm it has the billing:read_costs and billing:read_dimensions scopes.

Sync failing with a 410 "Gone" error

CloudZero caches paginated query results for 24 hours. If a sync takes longer than that, the cache expires and you'll see a 410 error. Retry the sync to start a fresh query.

If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.

Was this page useful?