Hello
I have grafana alloy configuration + tempo installation and I’d like to know why only I have load only on my certain alloy pods
As you can see from picture, only some distributor pods has been utilizated
My alloy configuration
apiVersion: apps/v1
kind: Deployment
metadata:
name: alloy
spec:
replicas: 20
selector:
matchLabels:
app: alloy
template:
metadata:
labels:
app: alloy
spec:
containers:
- name: alloy
image: grafana/alloy:latest
ports:
- containerPort: 12345
- containerPort: 4318
volumeMounts:
- name: config-volume
mountPath: /etc/alloy
volumes:
- name: config-volume
configMap:
name: alloy-config
Its config
otelcol.receiver.otlp "demo" {
grpc {
endpoint = "0.0.0.0:4318"
}
output {
traces = [otelcol.exporter.otlp.tempo.input]
}
}
otelcol.exporter.otlp "tempo" {
client {
endpoint = "monitoring-tempo-distributor:4317"
tls {
insecure = true
}
}
}
And my tempo values is
tempo-distributed:
storage:
trace:
backend: s3
s3:
access_key: xxx
secret_key: xxxx
bucket: xxx
endpoint: xxxxx
pool:
max_workers: 400
queue_depth: 20000
compactor:
config:
compaction:
block_retention: 3h
compaction_window: 5m
distributor:
replicas: 20
ingester:
replicas: 20
traces:
otlp:
grpc:
enabled: true
http:
enabled: true
zipkin:
enabled: false
jaeger:
thriftHttp:
enabled: false
opencensus:
enabled: false
minio:
enabled: false
metricsGenerator:
enabled: true
registry:
external_labels:
source: tempo
config:
storage:
remote_write:
- url: "http://prometheus:9090/api/v1/write"
send_exemplars: true
global_overrides:
metrics_generator_processors: [service-graphs, span-metrics]
It seems to me that my alloy configuration forward traffic only for certain tempo instances. How can I avoid this??
Thank you for help!