removing sections that don't make sense

Author: dhtclk

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

@@ -10,41 +10,21 @@ keywords: ['clickstack', 'example data', 'sample dataset', 'logs', 'observabilit
 ---
 
 import Image from '@theme/IdealImage';
-import hyperdx from '@site/static/images/use-cases/observability/hyperdx-1.png';
 import hyperdx_20 from '@site/static/images/use-cases/observability/hyperdx-20.png';
-import hyperdx_3 from '@site/static/images/use-cases/observability/hyperdx-3.png';
-import hyperdx_4 from '@site/static/images/use-cases/observability/hyperdx-4.png';
 import hyperdx_21 from '@site/static/images/use-cases/observability/hyperdx-21.png';
 import hyperdx_22 from '@site/static/images/use-cases/observability/hyperdx-22.png';
 import hyperdx_23 from '@site/static/images/use-cases/observability/hyperdx-23.png';
-import copy_api_key from '@site/static/images/use-cases/observability/copy_api_key.png';
 
-This getting started guide allows you collect local logs and metrics from your system, sending them to ClickStack for visualization and analysis.
+This getting started guide allows you to collect local logs and metrics from your system, sending them to ClickStack for visualization and analysis.
 
 **This example works on OSX and Linux systems only**
 
-The following example assumes you have started ClickStack using the [instructions for the all-in-one image](/use-cases/observability/clickstack/getting-started) and connected to the [local ClickHouse instance](/use-cases/observability/clickstack/getting-started#complete-connection-credentials) or a [ClickHouse Cloud instance](/use-cases/observability/clickstack/getting-started#create-a-cloud-connection).
-
 :::note HyperDX in ClickHouse Cloud
-This sample dataset can also be used with HyperDX in ClickHouse Cloud, with only minor adjustments to the flow as noted. If using HyperDX in ClickHouse Cloud, users will require an Open Telemetry collector to be running locally as described in the [getting started guide for this deployment model](/use-cases/observability/clickstack/deployment/hyperdx-clickhouse-cloud).
+This sample dataset can also be used with HyperDX in ClickHouse Cloud, with only minor adjustments to the flow as noted. If using HyperDX in ClickHouse Cloud, users will require an OpenTelemetry collector to be running locally as described in the [getting started guide for this deployment model](/use-cases/observability/clickstack/deployment/hyperdx-clickhouse-cloud).
 :::
 
 <VerticalStepper>
 
-## Navigate to the HyperDX UI {#navigate-to-the-hyperdx-ui}
-
-Visit [http://localhost:8080](http://localhost:8080) to access the HyperDX UI if deploying locally. If using HyperDX in ClickHouse Cloud, select your service and `HyperDX` from the left menu.
-
-## Copy ingestion API key {#copy-ingestion-api-key}
-
-:::note HyperDX in ClickHouse Cloud
-This step is not required if using HyperDX in ClickHouse Cloud.
-:::
-
-Navigate to [`Team Settings`](http://localhost:8080/team) and copy the `Ingestion API Key` from the `API Keys` section. This API key ensures data ingestion through the OpenTelemetry collector is secure.
-
-<Image img={copy_api_key} alt="Copy API key" size="lg"/>
-
 ## Create a custom OpenTelemetry configuration {#create-otel-configuration}
 
 Create a `custom-local-config.yaml` file with the following content:
@@ -57,8 +37,9 @@ receivers:
       - /host/var/log/syslog
       - /host/var/log/messages
       - /host/private/var/log/*.log   # macOS logs from host
-      - /tmp/all_events.log           # macOS - see below
-    start_at: beginning # modify to collect new files only
+    start_at: beginning
+    resource:
+      service.name: "system-logs"
 
   hostmetrics:
     collection_interval: 1s
@@ -124,11 +105,7 @@ To avoid this behavior, you can set the start position to `end` in the receiver
 
 For more details on the OpenTelemetry (OTel) configuration structure, we recommend [the official guide](https://opentelemetry.io/docs/collector/configuration/).
 
-:::note Detailed logs for OSX
-Users wanting more detailed logs on OSX can run the command `log stream --debug --style ndjson >> /tmp/all_events.log` before starting the collector below. This will capture detailed operating system logs to the file `/tmp/all_events.log`, already included in the above configuration.
-:::
-
-## Start the collector {#start-the-collector}
+## Start ClickStack with custom configuration {#start-clickstack}
 
 Run the following docker command to start the all-in-one container with your custom configuration:
 
@@ -149,7 +126,6 @@ We run the collector as the root user to access all system logs—this is necess
 Note that we mount the host's `/var/log` to `/host/var/log` inside the container to avoid conflicts with the container's own log files.
 :::
 
-:::note HyperDX in ClickHouse Cloud
 If using HyperDX in ClickHouse Cloud with a standalone collector, use this command instead:
 
 ```shell
@@ -166,13 +142,16 @@ docker run -d \
   -v /private/var/log:/host/private/var/log:ro \
   docker.hyperdx.io/hyperdx/hyperdx-otel-collector
 ```
-:::
 
 The collector will immediately begin collecting local system logs and metrics.
 
+## Navigate to the HyperDX UI {#navigate-to-the-hyperdx-ui}
+
+Visit [http://localhost:8080](http://localhost:8080) to access the HyperDX UI if deploying locally. If using HyperDX in ClickHouse Cloud, select your service and `HyperDX` from the left menu.
+
 ## Explore system logs {#explore-system-logs}
 
-Navigate to the HyperDX UI. The search UI should be populated with local system logs. Expand the filters to select the `system.log`:
+The search UI should be populated with local system logs. Expand the filters to select the `system.log`:
 
 <Image img={hyperdx_20} alt="HyperDX Local logs" size="lg"/>