1. Architecture #
OpenTelemetry and ClickHouse.
Components #
| Component | Role |
|---|---|
| SigNoz OTel Collector | Receives OTLP (and other formats), writes to ClickHouse, computes metrics from spans |
| ClickHouse | Stores logs, traces and metrics |
| SigNoz (main service) | Query API, alerts, web interface |
| ZooKeeper / ClickHouse Keeper | Coordinates ClickHouse replication |
2. Installing #
Docker Compose or Helm.
Docker Compose #
git clone -b main https://github.com/SigNoz/signoz.git
cd signoz/deploy/docker
docker compose up -d --remove-orphans
# Interface : http://localhost:8080 OTLP : 4317 (gRPC) et 4318 (HTTP)Good to know: The installation procedure and the interface port have changed between versions: follow the README of the deploy folder of the version you install.Kubernetes #
helm repo add signoz https://charts.signoz.io && helm repo update
helm install signoz signoz/signoz -n platform --create-namespace -f values.yaml
# Collecte de l'infrastructure (métriques des nœuds et pods, logs des conteneurs, événements)
helm install k8s-infra signoz/k8s-infra -n platform \
--set otelCollectorEndpoint=signoz-otel-collector.platform.svc:4317Good practice: Size ClickHouse first (fast disks, memory): it carries the load. The other components are lightweight.
3. Sending data #
OTLP, as everywhere.
Variables #
export OTEL_SERVICE_NAME=commandes
export OTEL_EXPORTER_OTLP_ENDPOINT=http://signoz-host:4318
export OTEL_RESOURCE_ATTRIBUTES=deployment.environment=production
java -javaagent:opentelemetry-javaagent.jar -jar commandes.jarLogs, traces and metrics from an instrumented application arrive together and are linked by trace_id and service.name.
My progress
Sign in to track your progress and take notes. Sign in
💬 Questions about this lesson
No questions yet: be the first to ask for help or share your configuration.
Recommended Articles
Using SigNoz: APM, traces, logs, dashboards and alerts
Use SigNoz day to day: APM view of services, traces and logs explorers, query builder, ClickHouse...
Observability on ClickHouse: why a columnar database changes the game
Why more and more observability platforms store logs, traces and metrics in ClickHouse: columnar ...
SigNoz, ClickStack and ClickHouse best practices for observability
Best practices for observability on ClickHouse with SigNoz or ClickStack: OpenTelemetry instrumen...
Installing and deploying ClickStack: all-in-one, Docker Compose, Helm and Managed ClickStack
Deploying ClickStack to fit the need: all-in-one container with persistence, Docker Compose and i...
ClickStack: architecture, components and offerings (ClickHouse, HyperDX, OpenTelemetry)
ClickStack, ClickHouse's official observability stack: role of ClickHouse, the UI (HyperDX), the ...
Operating an observability platform on ClickHouse and choosing a tool
Operate ClickHouse for telemetry (replication, disks, merges, object storage, monitoring) and com...
OpenTelemetry architecture: understanding the 3 levels
A deep dive into the OpenTelemetry architecture. Learn how data flows from the application to the...
The observability trilemma: cost, completeness and performance, and how solutions resolve it
Understanding the observability trilemma (cost, data completeness, query performance), its three ...
The LGTM stack (Loki, Grafana, Tempo, Mimir): architecture and setup
Grafana Labs' LGTM stack: Loki for logs, Grafana for visualization, Tempo for traces, Mimir for m...