notes

Author: gingerwizard

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

@@ -19,7 +19,7 @@ The following configuration options are available for each component of ClickSta
 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.
 
 ```bash
-docker run  -e HYPERDX_LOG_LEVEL='debug' -p 8080:8080 -p 8123:8123 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one:2-nightly
+docker run  -e HYPERDX_LOG_LEVEL='debug' -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one:2-nightly
 ```
 
 ### Docker compose {#docker-compose}

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

@@ -32,10 +32,10 @@ This option includes authentication, enabling the persistence of dashboards, ale
 
 ### Deploy with Docker {#deploy-with-docker}
 
-The following will run an OpenTelemetry collector (on port 4317 and 4318), ClickHouse (on port 8123), and the HyperDX UI (on port 8080).
+The following will run an OpenTelemetry collector (on port 4317 and 4318) and the HyperDX UI (on port 8080).
 
 ```bash
-docker run -p 8080:8080 -p 8123:8123 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one:2-nightly
+docker run -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one:2-nightly
 ```
 
 ### Navigate to the HyperDX UI {#navigate-to-hyperdx-ui}
@@ -66,7 +66,6 @@ mkdir -p .volumes/db .volumes/ch_data .volumes/ch_logs
 # modify command to mount paths
 docker run \
   -p 8080:8080 \
-  -p 8123:8123 \
   -p 4317:4317 \
   -p 4318:4318 \
   -v "$(pwd)/.volumes/db:/data/db" \
@@ -89,7 +88,7 @@ If you need to customize the application (8080) or API (8000) ports that HyperDX
 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.
 
 ```bash
-docker run -p 8080:8080 -p 8123:8123 -p 4317:4317 -p 4999:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one:2-nightly
+docker run -p 8080:8080 -p 4317:4317 -p 4999:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one:2-nightly
 ```
 
 ## Using ClickHouse Cloud {#using-clickhouse-cloud}

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

@@ -49,7 +49,7 @@ receivers:
       - /var/log/syslog
       - /var/log/messages
       - /private/var/log/*.log       # macOS
-    start_at: beginning
+    start_at: beginning # modify to collect new files only
 
   hostmetrics:
     collection_interval: 1s
@@ -105,6 +105,14 @@ service:
 
 This configuration collects system logs and metric for OSX and Linux systems, sending the results to ClickStack via the OTLP endpoint on port 4317.
 
+:::note Ingestion timestamps
+This configuration adjusts timestamps at ingest, assigning an updated time value to each event. Users should ideally [preprocess or parse timestamps](/use-cases/observability/clickstack/ingesting-data/otel-collector#processing-filtering-transforming-enriching) using OTel processors or operators in their log files to ensure accurate event time is retained.
+
+With this example setup, if the receiver or file processor is configured to start at the beginning of the file, all existing log entries will be assigned the same adjusted timestamp - the time of processing rather than the original event time. Any new events appended to the file will receive timestamps approximating their actual generation time.
+
+To avoid this behavior, you can set the start position to `end` in the receiver configuration. This ensures only new entries are ingested and timestamped near their true arrival time.
+:::
+
 For more details on the OpenTelemetry (OTel) configuration structure, we recommend [the official guide](https://opentelemetry.io/docs/collector/configuration/).
 
 ## Start the collector {#start-the-collector}

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

@@ -38,10 +38,10 @@ This all-in-one image allows you to launch the full stack with a single command,
 
 ### Deploy stack with docker {#deploy-stack-with-docker}
 
-The following will run an OpenTelemetry collector (on port 4317 and 4318), ClickHouse (on port 8123), and the HyperDX UI (on port 8080).
+The following will run an OpenTelemetry collector (on port 4317 and 4318) and the HyperDX UI (on port 8080).
 
 ```bash
-docker run -p 8080:8080 -p 8123:8123 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one:2-nightly
+docker run -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one:2-nightly
 ```
 
 :::note Persisting data and settings
@@ -53,7 +53,6 @@ mkdir -p .volumes/db .volumes/ch_data .volumes/ch_logs
 # modify command to mount paths
 docker run \
   -p 8080:8080 \
-  -p 8123:8123 \
   -p 4317:4317 \
   -p 4318:4318 \
   -v "$(pwd)/.volumes/db:/data/db" \