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.
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
[WIP] Add E2E Integration Test For Adaptive Sampling Processor #5951
base: main
Are you sure you want to change the base?
[WIP] Add E2E Integration Test For Adaptive Sampling Processor #5951
Changes from 19 commits
6cc7c1b
e4eb3b6
ea76c8e
5483545
8ff74a7
6a9699a
a65c190
3018caf
d7ba2ce
c3b1ca4
7561945
9aaaf75
3dc923d
7dd33d1
b2be33c
b996270
d661a0f
7aba57e
c9811ab
735704c
f485cc8
54cd6b8
cf8dd9c
e18d8d5
24d11d4
9ebf133
ca9a8c9
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
@yurishkuro what kind of a config do we want to add to perform this override?
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.
something like "do not check sampler tags"
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.
@yurishkuro should this config be exposed as part of the YAML configuration? or do we just want it to be internal?
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.
It should be user settable
Check failure on line 41 in plugin/sampling/strategyprovider/adaptive/post_aggregator.go
GitHub Actions / lint
Check failure on line 379 in plugin/sampling/strategyprovider/adaptive/post_aggregator.go
GitHub Actions / lint
Check failure on line 380 in plugin/sampling/strategyprovider/adaptive/post_aggregator.go
GitHub Actions / lint
Check failure on line 381 in plugin/sampling/strategyprovider/adaptive/post_aggregator.go
GitHub Actions / lint
Check failure on line 382 in plugin/sampling/strategyprovider/adaptive/post_aggregator.go
GitHub Actions / lint
Check failure on line 383 in plugin/sampling/strategyprovider/adaptive/post_aggregator.go
GitHub Actions / lint
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.
@yurishkuro this causes the unit tests to fail and I believe its messing with the calculations as well. Any ideas on how we can get around this? If we don't hardcode this here however, the probability only gets calculated once.
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.
it's very difficult to troubleshoot like this. I would suggest maybe altering tracegen and manually adding the sampler.type=probabilistic / sampler.param=0.5 (any value for now) attributes to the span to see how the system reacts to this. To my knowledge aside from this check the probability used by the sampler should not be affecting the calculations, but I may be wrong.
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.
and another thing would help is to expose internal state via expvar so that we can actually monitor how that state changes.