-
Notifications
You must be signed in to change notification settings - Fork 527
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
TraceQL Search against Serverless Returns 400 #2114
Comments
I was going to suggest reviewing your Lambda settings to make sure things are setup correctly, but if you're confident you've run normal search queries through Lambdas then everything is likely correct. I'm curious as to what the Lambda code is receiving. Can we debug by dumping the values in this loop and see if anything looks off: https://github.com/grafana/tempo/blob/main/cmd/tempo-serverless/lambda/main.go#L59? Or maybe the Lambda itself does request/response logging? Perhaps it has a clue. We have not seen this issue internally, but I can't say we've run traceql through AWS lambda functions except through our integration tests. |
@joe-elliott - Yep, standard search is working. I added in the print statements, here's the result: Standard Search
TraceQL Search
Edit: Made sure the "query" was the same between both. |
Adding a decode on the value seems to fix the issue:
Logged output:
Standard search also continues to work with this fix. I would submit a MR...buuuuuut I did this at work soooo I can only "suggest" this as a fix :) |
haha :) well, thank you for the suggestion! |
i appreciate your help here. great find! the PR is up and will be backported to 2.0.1! |
Describe the bug
When deploying Tempo Serverless for Search on AWS Lambda, and using the
TraceQL
section of Grafana Explore, I receive the following error:To Reproduce
Steps to reproduce the behavior:
prefer_self: 0
so all Search Hits go to the External EndpointExpected behavior
I expect TraceQL to return the same results as it does when the Queriers return the result (
prefer-self: >0
)Environment:
go1.x
runtime.Additional Context
This is coming from Grafana Explore. I tried both 9.4.0-beta & 9.3.6.
Here's an example URL taken from Grafana's Inspector:
This is what the querier reports as the error:
Doing a curl against the Querier directly does the same:
In addition, normal Search works completely fine. It seems to be only an error when using TraceQL. Could the Serverless Function not be url parsing correctly?
The text was updated successfully, but these errors were encountered: