Implement max trace size parameter #7810
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Parship Chowdhury <[email protected]>
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #7810 +/- ##
==========================================
- Coverage 95.53% 95.50% -0.04%
==========================================
Files 307 307
Lines 15911 15956 +45
==========================================
+ Hits 15201 15239 +38
- Misses 558 562 +4
- Partials 152 155 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
yurishkuro
requested changes
Dec 31, 2025
cmd/jaeger/internal/extension/jaegerquery/internal/querysvc/v2/querysvc/service_test.go
Outdated
Show resolved
Hide resolved
Co-authored-by: Yuri Shkuro <[email protected]> Signed-off-by: Parship Chowdhury <[email protected]>
Parship12
force-pushed
the
max-trace-size-2
branch
from
84d5c03 to
5694c37
Compare
Contributor
Author
|
closed and reopened to re-run some failing checks. |
2. remove same code at aggregator.go 3. remove skipCurrentTrace and do an early exit from mergeTraces if the current count is already at max 4. remove redundant checks at aggregator.go Signed-off-by: Parship Chowdhury <[email protected]>
2. use range with .All() in copySpansUpToLimit 3. argument order to (dest, src, ...) Signed-off-by: Parship Chowdhury <[email protected]>
Signed-off-by: Parship Chowdhury <[email protected]>
Parship12
force-pushed
the
max-trace-size-2
branch
from
df74359 to
5b73044
Compare
yurishkuro
requested changes
Jan 1, 2026
| } | ||
|
|
||
| // add a warning to the first span of the trace | ||
| func (qs QueryService) addTruncationWarning(trace ptrace.Traces) { |
Member
There was a problem hiding this comment.
isn't this what jptrace.IsTraceTruncated() already checking for? Why do the same thing twice?
Contributor
Author
There was a problem hiding this comment.
They are checking different attributes for different purposes - one is an internal boolean flag, the other is a user-facing message.
Contributor
Author
There was a problem hiding this comment.
Ok simplified it.
Removed @jaeger@truncated boolean marker, IsTraceTruncated() and addTruncationWarning()
Changed the markTraceTruncated() to directly adds the warning
Co-authored-by: Yuri Shkuro <[email protected]> Signed-off-by: Parship Chowdhury <[email protected]>
Co-authored-by: Yuri Shkuro <[email protected]> Signed-off-by: Parship Chowdhury <[email protected]>
…f copySpansUpToLimit, fix early return Signed-off-by: Parship Chowdhury <[email protected]>
Signed-off-by: Parship Chowdhury <[email protected]>
Metrics Comparison SummaryTotal changes across all snapshots: 0 Detailed changes per snapshotsummary_metrics_snapshot_cassandra📊 Metrics Diff SummaryTotal Changes: 0
|
Member
|
bummer, merge conflicts, please resolve |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
Description of the changes
max_trace_sizeconfiguration parameter to limit spans per traceHow was this change tested?
Checklist
jaeger:make lint testjaeger-ui:npm run lintandnpm run test