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

honeycomb: adjust the sample rate using an attribute on the span #1162

Merged
merged 2 commits into from
Oct 7, 2020

Conversation

chris-smith-zocdoc
Copy link
Contributor

Description:
Allows setting Honeycomb's sample rate using an attribute on span.

This allows either a custom processor (my use case) or the application sdks to adjust the sample rate value for honeycomb. Once the sampling otel is finalized this implementation could be adjusted to use that instead of a custom attribute.

Testing:
Added unit test

Documentation:
Updated exporter readme

@chris-smith-zocdoc chris-smith-zocdoc requested a review from a team September 30, 2020 20:39
@codecov
Copy link

codecov bot commented Sep 30, 2020

Codecov Report

Merging #1162 into master will increase coverage by 0.02%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1162      +/-   ##
==========================================
+ Coverage   89.80%   89.82%   +0.02%     
==========================================
  Files         274      274              
  Lines       13475    13486      +11     
==========================================
+ Hits        12101    12114      +13     
+ Misses       1009     1008       -1     
+ Partials      365      364       -1     
Flag Coverage Δ
#integration 73.57% <ø> (ø)
#unit 88.96% <100.00%> (+0.02%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
exporter/honeycombexporter/factory.go 100.00% <100.00%> (ø)
exporter/honeycombexporter/honeycomb.go 79.83% <100.00%> (+1.76%) ⬆️
receiver/k8sclusterreceiver/watcher.go 97.64% <0.00%> (+2.35%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 42fbb3e...7341d1b. Read the comment docs.

@dmitryax
Copy link
Member

dmitryax commented Oct 5, 2020

@chris-smith-zocdoc please fix the linter issues

@william-tran
Copy link

To link the original spec issue: open-telemetry/opentelemetry-specification#570.

Many thanks for this!

ljmsc referenced this pull request in ljmsc/opentelemetry-collector-contrib Feb 21, 2022
Don't bother to add a report unless there has been a coverage change.

Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
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.

4 participants