ClickHouse integration: connect ClickHouse Cloud services to Polylane
Connect ClickHouse Cloud services to Polylane with a Developer API key. Link database endpoints to applications and inspect current service health.
Get started for freeHow to set up ClickHouse
- In ClickHouse Cloud, open your organization’s API Keys and create a Developer (read-only) key.
- Copy the key ID and the secret, which is shown once. Enter both in the ClickHouse Cloud connection form.
- Connect after validation. Each key belongs to one organization and each organization connects to the workspace once.
Permissions and access
Use the Developer role for read-only control-plane access. No SQL user or database password is requested. The connection reads ClickHouse Cloud services and current metrics, not application tables. A dedicated API key avoids sharing ClickHouse’s ten-requests-per-ten-seconds key budget with unrelated tooling.
Discovery, refresh and the connected view
Services refresh every 15 minutes with state, tier, region, cloud provider, version, replica sizing and endpoints. Hostnames link applications to database services through their environment configuration. The control plane returns current metric snapshots without history, so service pages do not have time-series metric charts.
Example workflow
Investigate an application that starts timing out after its ClickHouse service changes state. Follow its endpoint link to the database service, read current metrics and distinguish degraded, failed, stopped or partially running from normal idle/waking behavior. This checks the managed service before assuming a query or table is the cause.
Disconnect and revoke access
Disconnect the organization in Polylane and delete or disable its ClickHouse Cloud API key. If an expiring key stops working, replace it in the connection rather than changing SQL credentials.
Provider credentials and Polylane’s access mode are separate. Where write-capable tools exist, the connected account’s Settings page offers a Read-only switch. Turning it off permits writes subject to review and confirmation, but cannot add permissions to the provider credential. Agent-connected Kubernetes clusters stay read-only.
In the graph.
Every ClickHouse resource Polylane picks up sits in the graph with its connections, config and history.
Service Tools for the investigation.
What Polylane can do with ClickHouse while it investigates. Every call is recorded in the transcript.
clickhouseApi Call any ClickHouse Cloud API endpoint that lacks a dedicated tool
clickhouseListServices List ClickHouse Cloud services with state, sizing, version, and endpoints
clickhouseGetMetrics Read live ClickHouse Cloud service metrics (CPU, memory, connections, queries) from the Prometheus endpoint
Common questions.
Does this integration query my ClickHouse tables?
No. This connection uses the ClickHouse Cloud control plane, with service inventory and current metrics. It does not request SQL credentials or read application tables.
Why are there no historical ClickHouse metric charts?
The Cloud control plane provides a live metrics snapshot without historical time series. Agents read current values on demand instead.