1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
# Grafana Tempo — local traces backend.
#
# Mirrors the production Tempo config generated by the deployment agent.
# Differences from production, all deliberate:
# - storage points at MinIO rather than AWS S3
# - the OTLP gRPC receiver stays on the standard 4317; production moves it to
# 4319 only because its containers share one ECS awsvpc network namespace
# with the collector. Local containers do not, so there is no collision.
# - `stream_over_http_enabled` is on, see below. Production does not need it.
#
# NOTE: this file previously carried `partition_ring_live_store`,
# `query_live_store` and an `ingest:`/Kafka block. Those keys do not exist in
# the Tempo release this stack now pins, and Tempo crash-looped on startup as a
# result — the local trace pipeline was dead. Pinning the image is what keeps
# this config and the binary in agreement.
multitenancy_enabled: true
# LOCAL ONLY. Grafana's Tempo datasource can stream TraceQL search results over
# gRPC on the HTTP port, which is what the Explore UI uses by default; this
# setting is what lets Tempo serve that. Carried over from the previous local
# config rather than dropped, since removing it would silently change the
# Explore search path. Production has no Grafana and so never needs it.
#
# Note: Grafana's non-streaming search (/api/search over HTTP) works with or
# without this, so a headless query check will not tell the two apart.
stream_over_http_enabled: true
server:
http_listen_port: 3200
grpc_listen_port: 9097
log_level: warn
distributor:
receivers:
otlp:
protocols:
grpc:
endpoint: 0.0.0.0:4317
storage:
trace:
backend: s3
s3:
bucket: forklaunch-telemetry
endpoint: minio:9000
access_key: minioadmin
secret_key: minioadmin
insecure: true
forcepathstyle: true
wal:
path: /var/tempo/wal
usage_report:
reporting_enabled: false