-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Tempo Ingesters register to lokis ring #10172
Comments
Created the same issue in Tempo as well: grafana/tempo#2766. You can find the Tempo configs there as well! |
We also faced the same and faced 3 times till now in last 1 years. |
I've dealt with this randomly. What i found worked was a strong hostname for the join and a prefix like this
On the mimir side you can do the same thing.. pretty sure you can with tempo also
|
Wow, this seems to do the trick, thanks! But what a mess, how can this gotcha not be clearly documented somewhere? Edit: Spoke too soon, the problem persists... Edit 2: Not sure if fixed or not. At least I have not seen the error for a day now. Seemed that it took a greater part of the weekend to stabilize. |
Describe the bug
Tempo Ingesters registerd to lokis ingester ring which caused loki to go down and stop returning logs.
To Reproduce
Steps to reproduce the behavior:
Unsure of how to reproduce this issue as it has never happened in our current deployment before.
Expected behavior
Loki ingesters should register to loki and tempo ingesters should register to tempo.
Environment:
Current deployed is using tempo-distributed helm chart into eks. attached is the loki config
Loki gateway nginx config
Screenshots, Promtail config, or terminal output
Only log line that directed us to the issue was:
level=warn ts=2023-08-04T14:32:18.386282517Z caller=logging.go:86 traceID=54e1a62fbdffbc09 orgID=fake msg="POST /loki/api/v1/push (500) 4.35479ms Response: \"rpc error: code = Unimplemented desc = unknown service logproto.Pusher\\n\" ws: false; Connection: close; Content-Length: 177219; Content-Type: application/x-protobuf; User-Agent: promtail/2.6.1; "
The text was updated successfully, but these errors were encountered: