You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you cancel the request before it completes, this log does not appear.
To Reproduce
Steps to reproduce the behavior:
Run Tempo (single binary or distributed, shouldn't matter)
Monitor logs from the query-frontend
Perform a query that is slow (so you have enough time to cancel it)
Cancel the request
Nothing is logged by the query-frontend
Note: it's surprisingly difficult to get a slow query in a normal sized Tempo. To makes this easier to test you might want to introduce a time.Sleep(5 * time.Second) somewhere in the query path.
Expected behavior
I'd expect to see the usual logline, but with status=499.
Describe the bug
The query-frontend logs some details about the query when it completes, for example:
If you cancel the request before it completes, this log does not appear.
To Reproduce
Steps to reproduce the behavior:
Note: it's surprisingly difficult to get a slow query in a normal sized Tempo. To makes this easier to test you might want to introduce a
time.Sleep(5 * time.Second)
somewhere in the query path.Expected behavior
I'd expect to see the usual logline, but with
status=499
.Additional Context
The log line is printed here:
tempo/modules/frontend/handler.go
Lines 96 to 104 in ba93a40
I believe we should not return early when the request fails:
tempo/modules/frontend/handler.go
Lines 67 to 76 in ba93a40
The text was updated successfully, but these errors were encountered: