-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add batch size metric #1241
Add batch size metric #1241
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1241 +/- ##
==========================================
- Coverage 88.61% 88.23% -0.39%
==========================================
Files 207 201 -6
Lines 15110 14630 -480
==========================================
- Hits 13390 12909 -481
- Misses 1287 1290 +3
+ Partials 433 431 -2
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Pavol Loffay <ploffay@redhat.com>
c652e33
to
0f4e1a8
Compare
Rebased. Could be this merged? |
Can somebody restart windows and load tests? |
Signed-off-by: Pavol Loffay <ploffay@redhat.com>
* Add batch size metric to otel collector Signed-off-by: Pavol Loffay <ploffay@redhat.com> * Rename variable Signed-off-by: Pavol Loffay <ploffay@redhat.com>
Bumps golang from 1.17.6-stretch to 1.17.7-stretch. --- updated-dependencies: - dependency-name: golang dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Description: <Describe what has changed.
Add batch size metric (units send in a batch). This metric helps us to tune batch processor size.
Link to tracking Issue:
Related to jaegertracing/jaeger#2165 (comment)
Related to #662
Related to https://github.com/open-telemetry/opentelemetry-collector/issues/1139
Testing: < Describe what testing was performed and which tests were added.>
Documentation: < Describe the documentation added.>