Kubecost (IBM / Apptio)

Connect Kubecost (IBM / Apptio) to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.

Connect your Kubecost deployment to pull Kubernetes cost allocation and infrastructure asset costs into the PostHog Data warehouse.

Enter the URL where your Kubecost cost-model API is reachable (e.g. https://kubecost.example.com — with or without the /model suffix). Self-hosted Kubecost ships with no built-in auth, so the API must be exposed to PostHog, typically behind an ingress or auth proxy. If your deployment or proxy requires a token (e.g. Kubecost Cloud), provide it as the API key and it is sent as a bearer token — this requires an https:// URL so the key is never sent in plaintext.

Configuration

Option	Type	Required
Kubecost API URL	text	Yes
API key (optional)	password	No

Linking Kubecost (IBM / Apptio) to PostHog

1. Go to the Data pipeline page in PostHog
2. Click New source and select Kubecost (IBM / Apptio)
3. Fill in the required configuration fields
4. Click Next, select the tables you want to sync, and then press Import

Supported tables

Table	Description	Sync method	Incremental field	Primary key
allocation_by_namespace	Kubernetes workload cost and usage from the Kubecost Allocation API, aggregated by namespace — one row per namespace per day.	Incremental, Full refresh	window_start	—
allocation_by_controller	Kubernetes workload cost and usage from the Kubecost Allocation API, aggregated by controller — one row per controller per day.	Incremental, Full refresh	window_start	—
allocation_by_pod	Kubernetes workload cost and usage from the Kubecost Allocation API, aggregated by pod — one row per pod per day.	Incremental, Full refresh	window_start	—
assets	Cluster infrastructure costs from the Kubecost Assets API — one row per asset (node, disk, network, load balancer, cluster management fee) per day.	Incremental, Full refresh	window_start	—