From e6bebd216e93cdba054d185b0dd68fbb017238d7 Mon Sep 17 00:00:00 2001 From: Shaun Struwig <41984034+Blargian@users.noreply.github.com> Date: Tue, 2 Sep 2025 11:35:51 +0200 Subject: [PATCH] prefer "you" over "users" --- .../observability/clickstack/ingesting-data/sdks/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/use-cases/observability/clickstack/ingesting-data/sdks/index.md b/docs/use-cases/observability/clickstack/ingesting-data/sdks/index.md index 9dc65b41ae2..0bb78e93527 100644 --- a/docs/use-cases/observability/clickstack/ingesting-data/sdks/index.md +++ b/docs/use-cases/observability/clickstack/ingesting-data/sdks/index.md @@ -6,7 +6,7 @@ description: 'Language SDKs for ClickStack - The ClickHouse Observability Stack' title: 'Language SDKs' --- -Users typically send data to ClickStack via the **OpenTelemetry (OTel) collector**, either directly from language SDKs or through intermediate OpenTelemetry collector acting as agents e.g. collecting infrastructure metrics and logs. +Data is typically sent to ClickStack via the **OpenTelemetry (OTel) collector**, either directly from language SDKs or through intermediate OpenTelemetry collector acting as agents e.g. collecting infrastructure metrics and logs. Language SDKs are responsible for collecting telemetry from within your application - most notably **traces** and **logs** - and exporting this data to the OpenTelemetry collector, via the OTLP endpoint, which handles ingestion into ClickHouse. @@ -21,7 +21,7 @@ In browser-based environments, SDKs may also be responsible for collecting **ses ## Supported languages {#supported-languages} :::note OpenTelemetry compatibility -While ClickStack offers its own language SDKs with enhanced telemetry and features, users can also use their existing OpenTelemetry SDKs seamlessly. +While ClickStack offers its own language SDKs with enhanced telemetry and features, you can also use their existing OpenTelemetry SDKs seamlessly. :::
@@ -51,7 +51,7 @@ OTEL_EXPORTER_OTLP_HEADERS='authorization=' This API key is generated by the HyperDX application, and is available via the app in `Team Settings → API Keys`. -For most [language SDKs](/use-cases/observability/clickstack/sdks) and telemetry libraries that support OpenTelemetry, users can simply set `OTEL_EXPORTER_OTLP_ENDPOINT` environment variable in your application or specify it during initialization of the SDK: +For most [language SDKs](/use-cases/observability/clickstack/sdks) and telemetry libraries that support OpenTelemetry, you can simply set `OTEL_EXPORTER_OTLP_ENDPOINT` environment variable in your application or specify it during initialization of the SDK: ```shell export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318