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
Is your feature request related to a problem? Please describe.
There has been some discussion before regarding how Tempo can protect itself from very large traces: #976, #1133. This request is specifically for Tempo to return an error if a trace exceeds max trace size on query. This will help prevent very large traces from OOMing components of the query path.
The text was updated successfully, but these errors were encountered:
This has already been implemented on the search path, but not the "trace by id" path. Given that we intend to make radical changes to our block format in the near future we've decided to punt on this one. Also note that we have made additional protections during compaction to prevent larger traces from being formed.
This issue has been automatically marked as stale because it has not had any activity in the past 60 days.
The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed after 15 days if there is no new activity.
Please apply keepalive label to exempt this Issue.
Is your feature request related to a problem? Please describe.
There has been some discussion before regarding how Tempo can protect itself from very large traces: #976, #1133. This request is specifically for Tempo to return an error if a trace exceeds max trace size on query. This will help prevent very large traces from OOMing components of the query path.
The text was updated successfully, but these errors were encountered: