-
Notifications
You must be signed in to change notification settings - Fork 522
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting error with tempo deployment #4339
Comments
Hi @Aniketsingh1. The key for the frontend's config block is |
I have made the changes as per your suggestion . Please see below - apiVersion: apps/v1 apiVersion: v1
apiVersion: v1
apiVersion: v1
But for this my tempo pods keep on restarting and give following logs: level=error ts=2024-11-18T11:19:35.927530275Z caller=frontend_processor.go:76 msg="error contacting frontend" address=10.100.57.252:9095 err="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 10.100.57.252:9095: connect: connection refused"" Am i missing something? |
The following successfully deployed tempo as daemonset on one evening:
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: tempo
labels:
app: tempo
spec:
selector:
matchLabels:
app: tempo
template:
metadata:
labels:
app: tempo
spec:
nodeSelector:
nodepool: aksuser
containers:
- name: tempo
image: grafana/tempo:latest
args:
- -config.file=/etc/tempo/tempo.yaml
ports:
- containerPort: 3200
- containerPort: 4317 # OTLP gRPC port
- containerPort: 4318 # OTLP HTTP port
- containerPort: 9095 # Frontend port
volumeMounts:
- name: tempo-config
mountPath: /etc/tempo
- name: tempo-storage
mountPath: /var/tempo
securityContext:
runAsUser: 10001
runAsGroup: 10001
readinessProbe:
httpGet:
path: /metrics
port: 3200
initialDelaySeconds: 5
periodSeconds: 10
livenessProbe:
httpGet:
path: /metrics
port: 3200
initialDelaySeconds: 5
periodSeconds: 10
volumes:
- name: tempo-config
configMap:
name: tempo-config
- name: tempo-storage
persistentVolumeClaim:
claimName: tempo-pvc
apiVersion: v1
kind: ConfigMap
metadata:
name: tempo-config
labels:
app: tempo
data:
tempo.yaml: |
server:
http_listen_port: 3200
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: tempo-pvc
labels:
app: tempo
spec:
accessModes:
storageClassName: azurefile
resources:
requests:
storage: 20Gi
apiVersion: v1
kind: Service
metadata:
name: tempo
labels:
app: tempo
spec:
ports:
targetPort: 3200
protocol: TCP
name: http
targetPort: 4317
protocol: TCP
name: otlp-grpc
targetPort: 4318
protocol: TCP
name: otlp-http
targetPort: 9095
protocol: TCP
name: frontend
selector:
app: tempo
but suddenly i have started getting error
Found 8 pods, using pod/tempo-d6mm5
failed parsing config: failed to parse configFile /etc/tempo/tempo.yaml: yaml: unmarshal errors:
line 48: field frontend not found in type app.Config
which i am not able to get.
If i remove the section
frontend:
queue:
size: 10000
workers: 10
then nothing appears on grafana.
Please help in solving this
The text was updated successfully, but these errors were encountered: