OtelTraceProvider.Builder introduce the trace rate limit property #2086
Conversation
mariusc83
force-pushed
the
mconstantin/introduce-trace-rate-limit-property
branch
2 times, most recently
from
d523380 to
46b4195
Compare
mariusc83
force-pushed
the
mconstantin/introduce-trace-rate-limit-property
branch
from
46b4195 to
83e190e
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #2086 +/- ##
===========================================
+ Coverage 68.86% 69.00% +0.13%
===========================================
Files 708 708
Lines 26289 26297 +8
Branches 4424 4422 -2
===========================================
+ Hits 18103 18144 +41
+ Misses 6984 6951 -33
Partials 1202 1202
|
| * @param traceRateLimit the trace rate limit as a value between 1 and Int.MAX_VALUE (default is Int.MAX_VALUE) | ||
| */ | ||
| fun setTraceRateLimit( | ||
| @IntRange(from = 1, to = Int.MAX_VALUE.toLong()) traceRateLimit: Int |
There was a problem hiding this comment.
why min value is 1? shouldn't it be 0 instead to be consistent with sample rate? there we allow setting 0, meaning no traces will be sent.
There was a problem hiding this comment.
that's what they have in the code base
There was a problem hiding this comment.
it is a Math.max(1, traceLimit) that it's being used in that class so 0 will not be taken into account.
| @@ -769,7 +770,7 @@ internal class OtelTracerProviderTest { | |||
| } | |||
| } | |||
|
|
|||
| @Test | |||
| @RepeatedTest(10) | |||
There was a problem hiding this comment.
do we have any added value from repeating this test, given that we already have quite large number of spans in the test itself?
There was a problem hiding this comment.
not quite...you are right, going to lower it.
mariusc83
force-pushed
the
mconstantin/introduce-trace-rate-limit-property
branch
from
83e190e to
275c4b3
Compare
What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)