Regenerate stats payload to add is_trace_root#2856
Conversation
BenchmarksBenchmark execution time: 2024-09-11 18:14:56 Comparing candidate commit d893820 in PR branch Found 1 performance improvements and 7 performance regressions! Performance is the same for 50 metrics, 1 unstable metrics. scenario:BenchmarkPartialFlushing/Disabled-24
scenario:BenchmarkPartialFlushing/Enabled-24
scenario:BenchmarkSetTagString-24
scenario:BenchmarkSingleSpanRetention/no-rules-24
scenario:BenchmarkSingleSpanRetention/with-rules/match-all-24
scenario:BenchmarkSingleSpanRetention/with-rules/match-half-24
scenario:BenchmarkStartSpan-24
scenario:BenchmarkTracerAddSpans-24
|
|
@ajgajg1134 I see some unrelated generated changes and I'm worried if they were missing for a long time ago or not. |
Yeah it appears that in addition to the new field there's also more specific error messages when a field fails to serialize. This seems fine to include here as well, do you see any other changes I'm missing? |
knusbaum
left a comment
There was a problem hiding this comment.
Thanks for fixing this.
Not really, but I was surprised by all the changes. In the generator we trust. |
What does this PR do?
Regenerate the stats payload msgp encoder as it was missing the new is_trace_root field.
Motivation
We want is_trace_root to be available for these metrics. Eventually this code will go away with my PR here #2817, but until that PR is ready after an agent review (still a few weeks out at least) then this will resolve the problem before then.
Reviewer's Checklist
Unsure? Have a question? Request a review!