ClickStack setup on clickhouse cloud

[abhikp10]

During our ClickStack setup, we’re encountering some challenges and would appreciate your guidance.

We’re currently ingesting logs into ClickHouse using the Otel Collector DaemonSet as described in the ClickStack Kubernetes Ingestion Guide
However, the documentation refers to an Otel Collector endpoint and a HyperDX API key, which we couldn’t locate in our HyperDX Cloud setup.

Current Setup

HyperDX Helm chart is deployed with the Otel Collector configured to point to ClickHouse Cloud.

The Otel DaemonSet is configured to send data to this Otel Collector.
Questions / Clarifications

Based on the documentation, is it correct that the Otel Collector should be managed on the ClickHouse side, while we only deploy the DaemonSet for log shipping?

Could you clarify where to obtain the Otel Collector endpoint and HyperDX API key? Are there any additional setup steps in ClickHouse Cloud or HyperDX required for this integration?

Are there any best practices or configuration recommendations for this deployment scenario?
Case ID: 00036816 clickhouse cloud support

[DerekChia]

cc @wrn14897

[wrn14897]

Hey @abhikp10, great question!

Currently, there isn’t a managed OpenTelemetry Collector available on ClickHouse Cloud. You’ll need to host your own collector.
The HyperDX API key and authentication are managed by the API and OpAMP server, which means you’ll still need to initialize a HyperDX account when deploying the HyperDX Helm chart.
If you don’t need ingestion authentication and there aren’t any receivers in your pipeline (for example, if you’re only scraping local Kubernetes logs), you can simply use a default OTel Collector with the clickhouseexporter. Point it to your ClickHouse Cloud account by deploying it via the OTel Collector Operator Helm chart
Let me know if this makes sense to you :)