From 9c6b21d6d31bb3b5d3090d0aebbfa49ad324c200 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Mon, 15 Jun 2026 17:17:43 +0000
Subject: [PATCH] docs: fix ClickStack collector env var CLICKHOUSE_USERNAME ->
 CLICKHOUSE_USER

---
 clickstack/ingesting-data/collector.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/clickstack/ingesting-data/collector.mdx b/clickstack/ingesting-data/collector.mdx
index 2e9d9bb88..09f4b08ae 100644
--- a/clickstack/ingesting-data/collector.mdx
+++ b/clickstack/ingesting-data/collector.mdx
@@ -106,7 +106,7 @@ ClickStack images are now published as `clickhouse/clickstack-*` (previously `do
 
 </Tabs>
 
-The target ClickHouse instance is configured via the environment variables `CLICKHOUSE_ENDPOINT`, `CLICKHOUSE_USERNAME`, and `CLICKHOUSE_PASSWORD`. The `CLICKHOUSE_ENDPOINT` should be the full ClickHouse Cloud HTTP endpoint, including the protocol and port—for example, `https://99rr6dm6v3.us-central1.gcp.clickhouse.cloud:8443`.
+The target ClickHouse instance is configured via the environment variables `CLICKHOUSE_ENDPOINT`, `CLICKHOUSE_USER`, and `CLICKHOUSE_PASSWORD`. The `CLICKHOUSE_ENDPOINT` should be the full ClickHouse Cloud HTTP endpoint, including the protocol and port—for example, `https://99rr6dm6v3.us-central1.gcp.clickhouse.cloud:8443`.
 
 For details on retrieving your Managed ClickStack credentials, see [here](/products/cloud/guides/sql-console/connection-details).
 
@@ -120,7 +120,7 @@ You should use a user with the [appropriate credentials](/clickstack/ingesting-d
 
 #### Configuring Managed ClickStack instance {#configuring-managed-clickstack}
 
-The OpenTelemetry collector can be configured to use a Managed ClickStack instance via the environment variables `CLICKHOUSE_ENDPOINT`, `CLICKHOUSE_USERNAME` and `CLICKHOUSE_PASSWORD`. How these are set depends on your deployment method:
+The OpenTelemetry collector can be configured to use a Managed ClickStack instance via the environment variables `CLICKHOUSE_ENDPOINT`, `CLICKHOUSE_USER` and `CLICKHOUSE_PASSWORD`. How these are set depends on your deployment method:
 
 <Tabs>
 
@@ -276,7 +276,7 @@ For the collector to connect to the OpAMP port it must be exposed by the HyperDX
 
 </Tabs>
 
-The target ClickHouse instance is configured via the environment variables `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`.
+The target ClickHouse instance is configured via the environment variables `CLICKHOUSE_ENDPOINT`, `CLICKHOUSE_USER`, and `CLICKHOUSE_PASSWORD`. The `CLICKHOUSE_ENDPOINT` should be the full ClickHouse HTTP endpoint, including the protocol and port—for example, `http://localhost:8123`.
 
 **These environment variables can be used with any of the docker distributions which include the connector.**
 
@@ -290,7 +290,7 @@ You should use a user with the [appropriate credentials](/clickstack/ingesting-d
 
 #### Configuring ClickHouse instance {#configuring-clickhouse-instance}
 
-The OpenTelemetry collector can be configured to use a ClickHouse instance via the environment variables `OPAMP_SERVER_URL`, `CLICKHOUSE_ENDPOINT`, `CLICKHOUSE_USERNAME` and `CLICKHOUSE_PASSWORD`. How these are set depends on your deployment method:
+The OpenTelemetry collector can be configured to use a ClickHouse instance via the environment variables `OPAMP_SERVER_URL`, `CLICKHOUSE_ENDPOINT`, `CLICKHOUSE_USER` and `CLICKHOUSE_PASSWORD`. How these are set depends on your deployment method:
 
 <Tabs>