Skip to content

Commit 0b38aa9

Browse files
committed
updating docker images
1 parent 4698586 commit 0b38aa9

File tree

14 files changed

+47
-35
lines changed

14 files changed

+47
-35
lines changed

docs/use-cases/observability/clickstack/config.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ The following configuration options are available for each component of ClickSta
2121
If using the [All in One](/use-cases/observability/clickstack/deployment/all-in-one), [HyperDX Only](/use-cases/observability/clickstack/deployment/hyperdx-only) or [Local Mode](/use-cases/observability/clickstack/deployment/local-mode-only) simply pass the desired setting via an environment variable e.g.
2222

2323
```shell
24-
docker run -e HYPERDX_LOG_LEVEL='debug' -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one
24+
docker run -e HYPERDX_LOG_LEVEL='debug' -p 8080:8080 -p 4317:4317 -p 4318:4318 clickhouse/clickstack-all-in-one:latest
2525
```
2626

2727
### Docker Compose {#docker-compose}

docs/use-cases/observability/clickstack/deployment/all-in-one.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,13 @@ This option includes authentication, enabling the persistence of dashboards, ale
3838
The following will run an OpenTelemetry collector (on port 4317 and 4318) and the HyperDX UI (on port 8080).
3939

4040
```shell
41-
docker run -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one
41+
docker run -p 8080:8080 -p 4317:4317 -p 4318:4318 clickhouse/clickstack-all-in-one:latest
4242
```
4343

44+
:::note Image Name Update
45+
ClickStack images are now published as `clickhouse/clickstack-*` (previously `docker.hyperdx.io/hyperdx/*`).
46+
:::
47+
4448
### Navigate to the HyperDX UI {#navigate-to-hyperdx-ui}
4549

4650
Visit [http://localhost:8080](http://localhost:8080) to access the HyperDX UI.
@@ -74,7 +78,7 @@ docker run \
7478
-v "$(pwd)/.volumes/db:/data/db" \
7579
-v "$(pwd)/.volumes/ch_data:/var/lib/clickhouse" \
7680
-v "$(pwd)/.volumes/ch_logs:/var/log/clickhouse-server" \
77-
docker.hyperdx.io/hyperdx/hyperdx-all-in-one
81+
clickhouse/clickstack-all-in-one:latest
7882
```
7983

8084
## Deploying to production {#deploying-to-production}
@@ -91,7 +95,7 @@ If you need to customize the application (8080) or API (8000) ports that HyperDX
9195
Customizing the OpenTelemetry ports can simply be changed by modifying the port forwarding flags. For example, replacing `-p 4318:4318` with `-p 4999:4318` to change the OpenTelemetry HTTP port to 4999.
9296

9397
```shell
94-
docker run -p 8080:8080 -p 4317:4317 -p 4999:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one
98+
docker run -p 8080:8080 -p 4317:4317 -p 4999:4318 clickhouse/clickstack-all-in-one:latest
9599
```
96100

97101
## Using ClickHouse Cloud {#using-clickhouse-cloud}
@@ -105,7 +109,7 @@ export CLICKHOUSE_ENDPOINT=<HTTPS ENDPOINT>
105109
export CLICKHOUSE_USER=<CLICKHOUSE_USER>
106110
export CLICKHOUSE_PASSWORD=<CLICKHOUSE_PASSWORD>
107111

108-
docker run -e CLICKHOUSE_ENDPOINT=${CLICKHOUSE_ENDPOINT} -e CLICKHOUSE_USER=default -e CLICKHOUSE_PASSWORD=${CLICKHOUSE_PASSWORD} -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one
112+
docker run -e CLICKHOUSE_ENDPOINT=${CLICKHOUSE_ENDPOINT} -e CLICKHOUSE_USER=default -e CLICKHOUSE_PASSWORD=${CLICKHOUSE_PASSWORD} -p 8080:8080 -p 4317:4317 -p 4318:4318 clickhouse/clickstack-all-in-one:latest
109113
```
110114

111115
The `CLICKHOUSE_ENDPOINT` should be the ClickHouse Cloud HTTPS endpoint, including the port `8443` e.g. `https://mxl4k3ul6a.us-east-2.aws.clickhouse.com:8443`
@@ -121,5 +125,5 @@ The OTel collector configuration can be modified if required - see ["Modifying c
121125
For example:
122126

123127
```shell
124-
docker run -e OTEL_AGENT_FEATURE_GATE_ARG='--feature-gates=clickhouse.json' -e BETA_CH_OTEL_JSON_SCHEMA_ENABLED=true -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one
128+
docker run -e OTEL_AGENT_FEATURE_GATE_ARG='--feature-gates=clickhouse.json' -e BETA_CH_OTEL_JSON_SCHEMA_ENABLED=true -p 8080:8080 -p 4317:4317 -p 4318:4318 clickhouse/clickstack-all-in-one:latest
125129
```

docs/use-cases/observability/clickstack/deployment/local-mode-only.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Similar to the [all-in-one image](/use-cases/observability/clickstack/deployment
3939
Local mode deploys the HyperDX UI on port 8080.
4040

4141
```shell
42-
docker run -p 8080:8080 docker.hyperdx.io/hyperdx/hyperdx-local
42+
docker run -p 8080:8080 clickhouse/clickstack-local:latest
4343
```
4444

4545
### Navigate to the HyperDX UI {#navigate-to-hyperdx-ui}
@@ -63,5 +63,5 @@ Create a source, retain all default values, and complete the `Table` field with
6363
For the local mode only image, users only need to set the `BETA_CH_OTEL_JSON_SCHEMA_ENABLED=true` parameter e.g.
6464

6565
```shell
66-
docker run -e BETA_CH_OTEL_JSON_SCHEMA_ENABLED=true -p 8080:8080 docker.hyperdx.io/hyperdx/hyperdx-local
66+
docker run -e BETA_CH_OTEL_JSON_SCHEMA_ENABLED=true -p 8080:8080 clickhouse/clickstack-local:latest
6767
```

docs/use-cases/observability/clickstack/example-datasets/local-data.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ docker run -d --name clickstack \
117117
-v "$(pwd)/custom-local-config.yaml:/etc/otelcol-contrib/custom.config.yaml:ro" \
118118
-v /var/log:/host/var/log:ro \
119119
-v /private/var/log:/host/private/var/log:ro \
120-
docker.hyperdx.io/hyperdx/hyperdx-all-in-one:latest
120+
clickhouse/clickstack-all-in-one:latest
121121
```
122122

123123
:::note Root user
@@ -140,7 +140,7 @@ docker run -d \
140140
-v "$(pwd)/custom-local-config.yaml:/etc/otelcol-contrib/custom.config.yaml:ro" \
141141
-v /var/log:/host/var/log:ro \
142142
-v /private/var/log:/host/private/var/log:ro \
143-
docker.hyperdx.io/hyperdx/hyperdx-otel-collector
143+
clickhouse/clickstack-otel-collector:latest
144144
```
145145

146146
The collector will immediately begin collecting local system logs and metrics.

docs/use-cases/observability/clickstack/getting-started.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -42,10 +42,14 @@ This all-in-one image allows you to launch the full stack with a single command,
4242
The following will run an OpenTelemetry collector (on port 4317 and 4318) and the HyperDX UI (on port 8080).
4343

4444
```shell
45-
docker run -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one
45+
docker run -p 8080:8080 -p 4317:4317 -p 4318:4318 clickhouse/clickstack-all-in-one:latest
4646
```
4747

48-
:::note Persisting data and settings
48+
:::note Image Name Update
49+
ClickStack images are now published as `clickhouse/clickstack-*` (previously `docker.hyperdx.io/hyperdx/*`).
50+
:::
51+
52+
:::tip Persisting data and settings
4953
To persist data and settings across restarts of the container, users can modify the above docker command to mount the paths `/data/db`, `/var/lib/clickhouse` and `/var/log/clickhouse-server`.
5054

5155
For example:
@@ -59,7 +63,7 @@ docker run \
5963
-v "$(pwd)/.volumes/db:/data/db" \
6064
-v "$(pwd)/.volumes/ch_data:/var/lib/clickhouse" \
6165
-v "$(pwd)/.volumes/ch_logs:/var/log/clickhouse-server" \
62-
docker.hyperdx.io/hyperdx/hyperdx-all-in-one
66+
clickhouse/clickstack-all-in-one:latest
6367
```
6468
:::
6569

@@ -124,7 +128,7 @@ export CLICKHOUSE_PASSWORD=<YOUR_PASSWORD>
124128
Run the following docker command:
125129

126130
```shell
127-
docker run -e CLICKHOUSE_ENDPOINT=${CLICKHOUSE_ENDPOINT} -e CLICKHOUSE_USER=default -e CLICKHOUSE_PASSWORD=${CLICKHOUSE_PASSWORD} -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one
131+
docker run -e CLICKHOUSE_ENDPOINT=${CLICKHOUSE_ENDPOINT} -e CLICKHOUSE_USER=default -e CLICKHOUSE_PASSWORD=${CLICKHOUSE_PASSWORD} -p 8080:8080 -p 4317:4317 -p 4318:4318 clickhouse/clickstack-all-in-one:latest
128132
```
129133

130134
This will expose an OpenTelemetry collector (on port 4317 and 4318), and the HyperDX UI (on port 8080).
@@ -177,7 +181,7 @@ You can use a hosted version of HyperDX in local mode available at [play.hyperdx
177181
The self-hosted local mode image comes with an OpenTelemetry collector and a ClickHouse server pre-configured as well. This makes it easy to consume telemetry data from your applications and visualize it in HyperDX with minimal external setup. To get started with the self-hosted version, simply run the Docker container with the appropriate ports forwarded:
178182

179183
```shell
180-
docker run -p 8080:8080 docker.hyperdx.io/hyperdx/hyperdx-local
184+
docker run -p 8080:8080 clickhouse/clickstack-local:latest
181185
```
182186

183187
You will not be promoted to create a user as local mode does not include authentication.

docs/use-cases/observability/clickstack/host-logs/generic-host-logs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -245,7 +245,7 @@ docker run --name clickstack \
245245
-e CUSTOM_OTELCOL_CONFIG_FILE=/etc/otelcol-contrib/custom.config.yaml \
246246
-v "$(pwd)/host-logs-monitoring.yaml:/etc/otelcol-contrib/custom.config.yaml:ro" \
247247
-v /var/log:/var/log:ro \
248-
docker.hyperdx.io/hyperdx/hyperdx-all-in-one:latest
248+
clickhouse/clickstack-all-in-one:latest
249249
```
250250

251251
:::note
@@ -341,7 +341,7 @@ docker run --name clickstack-demo \
341341
-e CUSTOM_OTELCOL_CONFIG_FILE=/etc/otelcol-contrib/custom.config.yaml \
342342
-v "$(pwd)/host-logs-demo.yaml:/etc/otelcol-contrib/custom.config.yaml:ro" \
343343
-v "$(pwd)/journal.log:/tmp/host-demo/journal.log:ro" \
344-
docker.hyperdx.io/hyperdx/hyperdx-all-in-one:latest
344+
clickhouse/clickstack-all-in-one:latest
345345
```
346346

347347
:::note

docs/use-cases/observability/clickstack/ingesting-data/collector.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ If you are managing your own OpenTelemetry collector in a standalone deployment
4040
To deploy the ClickStack distribution of the OTel connector in a standalone mode, run the following docker command:
4141

4242
```shell
43-
docker run -e OPAMP_SERVER_URL=${OPAMP_SERVER_URL} -e CLICKHOUSE_ENDPOINT=${CLICKHOUSE_ENDPOINT} -e CLICKHOUSE_USER=default -e CLICKHOUSE_PASSWORD=${CLICKHOUSE_PASSWORD} -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-otel-collector
43+
docker run -e OPAMP_SERVER_URL=${OPAMP_SERVER_URL} -e CLICKHOUSE_ENDPOINT=${CLICKHOUSE_ENDPOINT} -e CLICKHOUSE_USER=default -e CLICKHOUSE_PASSWORD=${CLICKHOUSE_PASSWORD} -p 8080:8080 -p 4317:4317 -p 4318:4318 clickhouse/clickstack-otel-collector:latest
4444
```
4545

4646
Note that we can overwrite the target ClickHouse instance with environment variables for `CLICKHOUSE_ENDPOINT`, `CLICKHOUSE_USERNAME`, and `CLICKHOUSE_PASSWORD`. The `CLICKHOUSE_ENDPOINT` should be the full ClickHouse HTTP endpoint, including the protocol and port—for example, `http://localhost:8123`.
@@ -71,9 +71,13 @@ export CLICKHOUSE_PASSWORD=<CLICKHOUSE_PASSWORD>
7171
```
7272

7373
```shell
74-
docker run -e OPAMP_SERVER_URL=${OPAMP_SERVER_URL} -e CLICKHOUSE_ENDPOINT=${CLICKHOUSE_ENDPOINT} -e CLICKHOUSE_USER=default -e CLICKHOUSE_PASSWORD=${CLICKHOUSE_PASSWORD} -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one
74+
docker run -e OPAMP_SERVER_URL=${OPAMP_SERVER_URL} -e CLICKHOUSE_ENDPOINT=${CLICKHOUSE_ENDPOINT} -e CLICKHOUSE_USER=default -e CLICKHOUSE_PASSWORD=${CLICKHOUSE_PASSWORD} -p 8080:8080 -p 4317:4317 -p 4318:4318 clickhouse/clickstack-all-in-one:latest
7575
```
7676

77+
:::note Image Name Update
78+
ClickStack images are now published as `clickhouse/clickstack-*` (previously `docker.hyperdx.io/hyperdx/*`).
79+
:::
80+
7781
#### Docker Compose {#docker-compose-otel}
7882

7983
With Docker Compose, modify the collector configuration using the same environment variables as above:
@@ -169,7 +173,7 @@ docker run -d --name clickstack \
169173
-p 8080:8080 -p 4317:4317 -p 4318:4318 \
170174
-e CUSTOM_OTELCOL_CONFIG_FILE=/etc/otelcol-contrib/custom.config.yaml \
171175
-v "$(pwd)/custom-config.yaml:/etc/otelcol-contrib/custom.config.yaml:ro" \
172-
docker.hyperdx.io/hyperdx/hyperdx-all-in-one:latest
176+
clickhouse/clickstack-all-in-one:latest
173177
```
174178

175179
**Deploy with the standalone collector:**
@@ -182,7 +186,7 @@ docker run -d \
182186
-e CLICKHOUSE_PASSWORD=${CLICKHOUSE_PASSWORD} \
183187
-v "$(pwd)/custom-config.yaml:/etc/otelcol-contrib/custom.config.yaml:ro" \
184188
-p 4317:4317 -p 4318:4318 \
185-
docker.hyperdx.io/hyperdx/hyperdx-otel-collector
189+
clickhouse/clickstack-otel-collector:latest
186190
```
187191

188192
:::note
@@ -412,7 +416,7 @@ In order to query the JSON type, support must also be enabled in the HyperDX app
412416
For example:
413417

414418
```shell
415-
docker run -e OTEL_AGENT_FEATURE_GATE_ARG='--feature-gates=clickhouse.json' -e OPAMP_SERVER_URL=${OPAMP_SERVER_URL} -e CLICKHOUSE_ENDPOINT=${CLICKHOUSE_ENDPOINT} -e CLICKHOUSE_USER=default -e CLICKHOUSE_PASSWORD=${CLICKHOUSE_PASSWORD} -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-otel-collector
419+
docker run -e OTEL_AGENT_FEATURE_GATE_ARG='--feature-gates=clickhouse.json' -e OPAMP_SERVER_URL=${OPAMP_SERVER_URL} -e CLICKHOUSE_ENDPOINT=${CLICKHOUSE_ENDPOINT} -e CLICKHOUSE_USER=default -e CLICKHOUSE_PASSWORD=${CLICKHOUSE_PASSWORD} -p 8080:8080 -p 4317:4317 -p 4318:4318 clickhouse/clickstack-otel-collector:latest
416420
```
417421

418422
### Migrating from map-based schemas to the JSON type {#migrating-from-map-based-schemas-to-json}

docs/use-cases/observability/clickstack/integration-examples/kafka-metrics.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ This example shows a complete setup with Kafka, the JMX Metric Gatherer, and Cli
101101
```yaml
102102
services:
103103
clickstack:
104-
image: docker.hyperdx.io/hyperdx/hyperdx-all-in-one:latest
104+
image: clickhouse/clickstack-all-in-one:latest
105105
ports:
106106
- "8080:8080"
107107
- "4317:4317"
@@ -234,7 +234,7 @@ Start a ClickStack instance:
234234
```bash
235235
docker run -d --name clickstack-demo \
236236
-p 8080:8080 -p 4317:4317 -p 4318:4318 \
237-
docker.hyperdx.io/hyperdx/hyperdx-all-in-one:latest
237+
clickhouse/clickstack-all-in-one:latest
238238
```
239239

240240
#### Load metrics into ClickStack {#load-metrics}

docs/use-cases/observability/clickstack/integration-examples/nginx-logs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,7 @@ docker run --name clickstack \
160160
-e CUSTOM_OTELCOL_CONFIG_FILE=/etc/otelcol-contrib/custom.config.yaml \
161161
-v "$(pwd)/nginx-monitoring.yaml:/etc/otelcol-contrib/custom.config.yaml:ro" \
162162
-v /var/log/nginx:/var/log/nginx:ro \
163-
docker.hyperdx.io/hyperdx/hyperdx-all-in-one:latest
163+
clickhouse/clickstack-all-in-one:latest
164164
```
165165

166166
:::note
@@ -245,7 +245,7 @@ docker run --name clickstack-demo \
245245
-e CUSTOM_OTELCOL_CONFIG_FILE=/etc/otelcol-contrib/custom.config.yaml \
246246
-v "$(pwd)/nginx-demo.yaml:/etc/otelcol-contrib/custom.config.yaml:ro" \
247247
-v "$(pwd)/access.log:/tmp/nginx-demo/access.log:ro" \
248-
docker.hyperdx.io/hyperdx/hyperdx-all-in-one:latest
248+
clickhouse/clickstack-all-in-one:latest
249249
```
250250

251251
#### Verify logs in HyperDX {#verify-demo-logs}

docs/use-cases/observability/clickstack/integration-examples/nginx-traces.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -183,7 +183,7 @@ If you don't have ClickStack running yet, start it with:
183183
```bash
184184
docker run --name clickstack-demo \
185185
-p 8080:8080 -p 4317:4317 -p 4318:4318 \
186-
docker.hyperdx.io/hyperdx/hyperdx-all-in-one:latest
186+
clickhouse/clickstack-all-in-one:latest
187187
```
188188

189189
Wait about 30 seconds for ClickStack to fully initialize before proceeding.

0 commit comments

Comments
 (0)