Hello,
I’m trying to implement horizontal scaling (monolithic) with Tempo because we don’t have Kubernetes or containers with this configuration.
server:
http_listen_port: 3200
log_level: debug
distributor:
receivers:
otlp:
protocols:
http:
grpc:
endpoint: 0.0.0.0:4317
ingester:
#lifecycler:
# ring:
# kvstore:
# store: memberlist
# replication_factor: 2
max_block_duration: 1h # cut the headblock when this much time passes. this is being set for demo purposes and should probably be left alone normally
compactor:
compaction:
block_retention: 240h # overall Tempo trace retention. set for demo purposes, default is 14 days
memberlist:
abort_if_cluster_join_fails: false
bind_port: 7946
join_members:
- tempo-01.test.local:7946
- tempo-02.test.local:7946
storage:
trace:
backend: s3
wal:
path: /var/tempo/wal
s3:
bucket:
endpoint:
access_key:
secret_key:
metrics_generator:
# ring:
# kvstore:
# store: memberlist
registry:
external_labels:
source: tempo
cluster: tempo.test.local
storage:
path: /var/tempo/generator/wal
remote_write:
- url: http://192.168.0.5:9090/api/v1/write
send_exemplars: true
processor:
service_graphs:
enable_virtual_node_label: true
span_metrics:
intrinsic_dimensions:
status_message: true
dimensions: # possibilité d'ajouter des labels aux metrics
- service.version
#querier:
# frontend_worker:
# frontend_address: tempo.test.local:9095
overrides:
defaults:
global:
max_bytes_per_trace: 50000000
metrics_generator:
processors: [service-graphs, span-metrics] # enables metrics generator
However, when consulting /memberlist, I see this get this message : This instance doesn’t use memberlist.
What’s wrong with my configuration please? Any idea how I can improve my configuration to scale tempo please?
Note : firewalls are disabled on both servers
TEmpo are reachable on port 3200 by using a F5 loadbalancer