-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Expose tunning options via expvar #2496
Expose tunning options via expvar #2496
Conversation
@jpkrohling is it CI-related issue https://travis-ci.org/github/jaegertracing/jaeger/jobs/728900004 ? |
This test has indeed been flaky... |
Codecov Report
@@ Coverage Diff @@
## master #2496 +/- ##
==========================================
- Coverage 95.36% 95.33% -0.04%
==========================================
Files 208 208
Lines 9222 9248 +26
==========================================
+ Hits 8795 8817 +22
- Misses 350 354 +4
Partials 77 77
Continue to review full report at Codecov.
|
Tests are passing now :-) |
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.
I like the base idea, but I think the actual registration with expvar could be closer to where the values are used or defined.
I would also love to see other values, although they might come in a later PR:
--memory.max-traces
--span-storage.type (not sure the storate type is actually stored there)
--downsampling.ratio
6f6a216
to
0bd8431
Compare
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.
Looks good to me. One thing that we might want to add is the storage type. What do you think?
Sure, wilco |
ce2eb02
to
2231f49
Compare
@jpkrohling Is it known issue https://travis-ci.org/github/jaegertracing/jaeger/jobs/729295839? |
Doesn't sound like it, looks like it's a real problem with the new test:
|
My bad, didn't notice... |
d8913fb
to
e1184dc
Compare
e1184dc
to
c6bbaf9
Compare
Always mount expvar /debug/vars handler regardless of chosen metrics backend. Store the following collector's options in expvar: - collector.num-workers - collector.queue-size Store the following agent's options in expvar: - processor.*.server-max-packet-size - processor.*.server-queue-size - processor.*.workers Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com>
Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com>
Put expvar logic into private funcs of builders. Use different values in tests. Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com>
Store following storage-related options in expvar: - memory.max-traces - downsampling.ratio Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com>
Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com>
Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com>
Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com>
Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com>
Delete direct expvar calls. Vendor latest jaeger-lib. Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com>
Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com>
Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com>
Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com>
20d5e36
to
e877351
Compare
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.
Looks great! The only question is about otel/go.mod
I am going to merge it, please put another PR for otel/go.mod |
Which problem is this PR solving?
Short description of the changes
--metrics-backend