Linking Komodor as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Contents
Connect your Komodor account to sync Kubernetes services, jobs, clusters, and monitors into the PostHog data warehouse.
Adding a data source
- Go to the sources tab of the data pipeline section in PostHog.
- Click + New source and then click Link next to Komodor.
- In Komodor, go to User settings > API Keys and create a new API key. Grant read access for the tables you want to sync.
- Back in PostHog, select your region (US or EU), enter your API key, then click Next.
- Select the tables you want to sync, set the sync frequency, then click Import.
Once the syncs are complete, you can start using Komodor data in PostHog.
Available tables
| Table | Description | Sync method |
|---|---|---|
services | Kubernetes services with their health status, latest deployment, and latest issue | Full refresh |
jobs | Kubernetes jobs and cron jobs with their status and issue details | Full refresh |
clusters | Kubernetes clusters connected to Komodor | Full refresh |
monitors | Monitor configurations used to detect failures in Kubernetes infrastructure | Full refresh |
All tables use full refresh, meaning all data is reloaded on each sync.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
services | Kubernetes services with their health status, latest deployment, and latest issue. | Full refresh | — | — |
jobs | Kubernetes jobs and cron jobs with their status and issue details. | Full refresh | — | — |
clusters | Kubernetes clusters connected to Komodor. | Full refresh | — | — |
monitors | Monitor configurations used to detect failures in Kubernetes infrastructure. | Full refresh | — | — |
cluster_issues | Issues Komodor detected in each cluster over its 7-day retention window, such as availability problems and failed deploys. | Incremental, Full refresh | startTime | — |
k8s_events | Kubernetes deploy and node events in each cluster over Komodor's 7-day retention window. | Incremental, Full refresh | startTime | — |
cost_allocation | Kubernetes cost per service over the past 30 days, refreshed on each sync. | Full refresh | — | — |