Deno

Use Deno’s built-in OpenTelemetry support to send logs, metrics, and traces to ClickHouse Observability. You do not need the ClickStack Node.js SDK or the legacy Deno logging package.

Set up OpenTelemetry

Follow the official Deno OpenTelemetry setup instructions to instrument your application. Configure the destination below, then enable Deno’s built-in integration when starting your application:

OTEL_DENO=true OTEL_SERVICE_NAME='my-deno-app' deno run app.ts

Add the permissions your application needs. Replace any example destinations or console-exporter settings from upstream instructions, including signal-specific endpoint overrides.

Configure your destination

Fully managed
Self-managed

Open Team Settings → Data → Managed Telemetry in your service and copy the OTLP HTTP endpoint and API key. Use the complete HTTPS endpoint, including its port:

export OTEL_EXPORTER_OTLP_ENDPOINT='https://YOUR_OTEL_ENDPOINT:4318'
export OTEL_EXPORTER_OTLP_HEADERS='authorization=Bearer%20YOUR_INGESTION_API_KEY'
export OTEL_EXPORTER_OTLP_PROTOCOL='http/protobuf'

Use your collector’s OTLP HTTP endpoint and ingestion key. Use http:// instead of https:// if your collector does not have TLS configured. For collector setup, see Ingesting with OpenTelemetry.

export OTEL_EXPORTER_OTLP_ENDPOINT='https://YOUR_COLLECTOR_HOST:4318'
export OTEL_EXPORTER_OTLP_HEADERS='authorization=YOUR_INGESTION_API_KEY'
export OTEL_EXPORTER_OTLP_PROTOCOL='http/protobuf'

Verify ingestion

Start your application and generate activity. In ClickHouse Observability, select a recent time range and find your application’s service name in Logs or Traces. Check Metrics after allowing time for export.

Introduction

Features

Administration

Guides

Integration partners

Self-managed

Set up OpenTelemetry

Configure your destination

Verify ingestion

​Set up OpenTelemetry

​Configure your destination

​Verify ingestion

Set up OpenTelemetry

Configure your destination

Verify ingestion