Skip to content
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

feat: Add WindowedThroughput sampler #709

Merged
merged 6 commits into from
Jun 9, 2023
Merged

Conversation

kentquirk
Copy link
Contributor

Depends on #708

Which problem is this PR solving?

  • Adds the other new sampler from the latest dynsampler-go.

Short description of the changes

  • Add the sampler and its config info
  • Update the docs
  • Add a basic test (dynsampler has all the sampler testing)

@kentquirk kentquirk requested a review from a team as a code owner June 9, 2023 02:02
@kentquirk kentquirk added this to the v2.0 milestone Jun 9, 2023
@kentquirk kentquirk mentioned this pull request Jun 9, 2023
Base automatically changed from kent.add_emathroughput to main June 9, 2023 15:50
@kentquirk kentquirk force-pushed the kent.add_windowedthroughput branch from e3d06ce to 2ed3ee3 Compare June 9, 2023 15:52
@@ -402,6 +402,111 @@ groups:
is a useful indicator of traces you'd like to see in Honeycomb, set
this to true.

- name: WindowedThroughputSampler
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we even need the ThroughputSampler anymore?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, mainly for compatibility. I do hope to deprecate it but don't think we need to do that for 2.0.

@kentquirk kentquirk merged commit e578209 into main Jun 9, 2023
@kentquirk kentquirk deleted the kent.add_windowedthroughput branch June 9, 2023 17:27
kentquirk added a commit that referenced this pull request Jun 9, 2023
Depends on #709 

## Which problem is this PR solving?

- The MaxKeys value is supported in most samplers, but it wasn't always
included in the config
- It defaulted to 0 which means "no max" -- Honeycomb CAs agree this is
not a useful setting.

## Short description of the changes

- Support MaxKeys in all dynamic samplers
- 0 now means 500
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants