What you will learn in this TP
- Deploy the all-in-one container with volumes
- Use the ingestion key
- Send traces and logs over OTLP
- Search by properties and in SQL
- Check persistence
Introduction #
What you will learn in this section
- Deploy the all-in-one container with volumes
- Use the ingestion key
- Send traces and logs over OTLP
- Search by properties and in SQL
- Check persistence
Context. You are evaluating ClickStack for your team. You need a demo instance that keeps its data from one day to the next and realistic data to show.
Prerequisites: a machine with Docker (4 GB free memory), curl and jq · Estimated time: 45 min
A persistent ClickStack instance fed with traces and logs, explored by search and in SQL.Setup #
Guided steps, with their solution.
1. Start ClickStack
Why? Without volumes, everything would be lost when the container is removed.
Start theclickhouse/clickstack-all-in-onecontainer with the three volumes (MongoDB, ClickHouse data and logs) on anobsDocker network.2. Create the account and get the ingestion key
Why? The collector rejects requests without a key.
Openhttp://localhost:8080, create the first account, then copy the key from Team Settings › API Keys into a variable.3. Send traces and logs
Why? telemetrygen produces realistic OTLP telemetry without writing an application.
Send traces for theboutiqueandpaiementservices (including errors), then info and error logs.4. Search and correlate
Why? Property search covers most needs.
In Search, Logs source: findpaiementerrors, then the exact phrase"timeout banque". Traces source: filter error spans and open a waterfall. Finally switch to SQL mode.5. Check in SQL and test persistence
Why? A demo that loses its data on restart convinces nobody.
Count logs and spans per service withclickhouse-client, remove and recreate the container, and check the numbers and your account are still there.
Difficulty level : ●●○○○ (2/5)
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
SigNoz, ClickStack and ClickHouse best practices for observability
Best practices for observability on ClickHouse with SigNoz or ClickStack: OpenTelemetry instrumen...
Observability on ClickHouse: why a columnar database changes the game
Why more and more observability platforms store logs, traces and metrics in ClickHouse: columnar ...
Telemetry in ClickHouse: schema, SQL, materialized views and retention
Telemetry in ClickHouse: otel_logs, otel_traces, otel_metrics_* and hyperdx_sessions tables, sort...
Operating ClickHouse for ClickStack: sizing, replication, monitoring, security and backup
Running ClickHouse in production for observability: estimating volume and disk, replicating with ...
Installing Jaeger v2: all-in-one, configuration and storage
Run Jaeger v2 as all-in-one, understand its configuration file (jaeger_storage and jaeger_query e...
Correlations in Grafana: jump from one data source to another
Create links between data sources in Explore: query and external correlations, variables, regex a...
Operating an observability platform on ClickHouse and choosing a tool
Operate ClickHouse for telemetry (replication, disks, merges, object storage, monitoring) and com...
Sending traces to Tempo: OpenTelemetry instrumentation and Alloy
Produce and route traces to Tempo: Python/Java/Node auto-instrumentation, the manual SDK, OTEL en...
Logs with OpenTelemetry: data model, appenders, correlation and collection
Master the log signal: the LogRecord data model, the Logs Bridge API and appenders (Logback, Log4...