1472aac289
* replace grafana agent example by alloy * changelog * update documentation * add tracing to distributor again and fix wording
2.3 KiB
Scalable Single Binary
** Note: This method of deploying Tempo is referred to by documentation as "scalable monolithic mode" **
In this example Tempo is configured to write data to MinIO which presents an
S3-compatible API. Additionally, memberlist is enabled to demonstrate how a
single binary can run all services and still make use of the cluster-awareness
that memberlist provides.
- Start up the local stack.
docker compose up -d
At this point, the following containers should be spun up:
docker compose ps
Name Command State Ports
------------------------------------------------------------------------------------------------------------------------------
scalable-single-binary_grafana_1 /run.sh Up 0.0.0.0:3000->3000/tcp,:::3000->3000/tcp
scalable-single-binary_k6-tracing_1 /k6-tracing run /example-s ... Up
scalable-single-binary_minio_1 sh -euc mkdir -p /data/tem ... Up 9000/tcp,
0.0.0.0:9001->9001/tcp,:::9001->9001/tcp
scalable-single-binary_prometheus_1 /bin/prometheus --config.f ... Up 9090/tcp
scalable-single-binary_tempo1_1 /tempo -target=scalable-si ... Up 0.0.0.0:3200->3200/tcp,:::3200->3200/tcp
scalable-single-binary_tempo2_1 /tempo -target=scalable-si ... Up
scalable-single-binary_tempo3_1 /tempo -target=scalable-si ... Up
scalable-single-binary_vulture_1 /tempo-vulture -prometheus ... Up
-
If you're interested you can see the WAL/blocks as they are being created. Navigate to MinIO at http://localhost:9001 and use the username/password of
tempo/supersecret. -
Navigate to Grafana select the Tempo data source and use the "Search" tab to find traces. Also notice that you can query Tempo metrics from the Prometheus data source setup in Grafana.
-
To stop the setup use:
docker compose down -v