Skip to main content
Skip to main content
Edit this page

Local mode only

Similar to the all-in-one image, this comprehensive Docker image bundles all ClickStack components:

  • ClickHouse
  • HyperDX
  • OpenTelemetry (OTel) collector (exposing OTLP on ports 4317 and 4318)
  • MongoDB (for persistent application state)

However, user authentication is disabled for this distribution of HyperDX

Suitable for​

  • Demos
  • Debugging
  • Development where HyperDX is used

Deployment steps​


Deploy with Docker​

Local mode deploys the HyperDX UI on port 8080.

docker run -p 8080:8080 clickhouse/clickstack-local:latest

Visit http://localhost:8080 to access the HyperDX UI.

You won't be prompted to create a user, as authentication isn't enabled in this deployment mode.

Connect to your own external ClickHouse cluster e.g. ClickHouse Cloud.

Create a source, retain all default values, and complete the Table field with the value otel_logs. All other settings should be auto-detected, allowing you to click Save New Source.

Schema choice: Map vs JSON​

ClickStack stores attributes as Map(LowCardinality(String), String) columns by default. This is the recommended schema for observability workloads. Combined with bucketed map serialization and text indexes on map keys and values, it provides selective lookups without the per-key ingest overhead of dynamic JSON subcolumns.

A JSON-typed schema is available in beta for evaluation on workloads with a small, stable attribute key-set. It is not recommended as the default. See Map vs JSON type for the full comparison and the env vars required to enable JSON support.