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
ClickStack: architecture, components and offerings (ClickHouse, HyperDX, OpenTelemetry)
ClickStack, ClickHouse's official observability stack: role of ClickHouse, the UI (HyperDX), the ...
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...
Sending telemetry to ClickStack: OpenTelemetry SDKs, collectors, logs, Kubernetes and browser sessions
Feeding ClickStack: ingestion key, OpenTelemetry SDK variables, forwarding through an existing co...
Installing OpenObserve and ingesting your first data
Install OpenObserve with Docker Compose or the binary, configure it with its ZO_* variables, send...
Installing Phoenix and tracing your first LLM application
Install Arize Phoenix (pip, Docker), send your first OpenInference traces from an OpenAI applicat...
Exploring with the ClickStack UI: sources, search, traces, sessions and SQL
Using the ClickStack UI (HyperDX): data sources, property and full-text search syntax, SQL mode, ...
Alerts and dashboards in ClickStack
Building charts and dashboards in ClickStack, creating alerts on a search or a chart, sending the...
Installing Zabbix and monitoring your first host
Install Zabbix with Docker Compose (server, PostgreSQL, web interface), install agent 2 on a Linu...
Sending logs, metrics and traces to OpenObserve
OpenObserve receiving endpoints: JSON, bulk, OTLP with the OpenTelemetry Collector, Prometheus re...