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

Add Metrics Only Receiver Factory type #1333

Closed
wants to merge 1 commit into from
Closed

Add Metrics Only Receiver Factory type #1333

wants to merge 1 commit into from

Conversation

keitwb
Copy link
Contributor

@keitwb keitwb commented Jul 13, 2020

It is kind of annoying to have to define a boilerplate method for traces when
it has nothing to do with the receiver.

It is kind of annoying to have to define a boilerplate method for traces when
it has nothing to do with the receiver.
@codecov
Copy link

codecov bot commented Jul 13, 2020

Codecov Report

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

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1333      +/-   ##
==========================================
+ Coverage   89.76%   89.79%   +0.02%     
==========================================
  Files         214      214              
  Lines       15138    15138              
==========================================
+ Hits        13589    13593       +4     
+ Misses       1132     1128       -4     
  Partials      417      417              
Impacted Files Coverage Δ
service/builder/receivers_builder.go 76.30% <100.00%> (+2.31%) ⬆️
translator/internaldata/resource_to_oc.go 83.72% <0.00%> (-2.33%) ⬇️
service/builder/pipelines_builder.go 83.00% <0.00%> (+1.30%) ⬆️

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 144f11e...d59698a. Read the comment docs.

@bogdandrutu
Copy link
Member

@keitwb I would like you to look at this approach #1334, what do you think?

I think we remove more boilerplate that way - no type function, no marshaler, etc.

@bogdandrutu
Copy link
Member

Probably we can use options pattern to allow users to set optional params like the custom marshaler and reduce the signature for the New funcs.

@keitwb
Copy link
Contributor Author

keitwb commented Jul 14, 2020

@bogdandrutu yeah what you did seems pretty flexible long term.

@keitwb keitwb closed this Jul 14, 2020
@keitwb keitwb deleted the metrics-receiver branch July 14, 2020 14:52
MovieStoreGuy pushed a commit to atlassian-forks/opentelemetry-collector that referenced this pull request Nov 11, 2021
* Add parent context to SpanProcessor.OnStart

The spec requires doing so. Right now SpanProcessor implementations
aren't doing anything with this argument.

* Update changelog

* Fix typo in test name
Troels51 pushed a commit to Troels51/opentelemetry-collector that referenced this pull request Jul 5, 2024
Co-authored-by: Lalit Kumar Bhasin <lalit_fin@yahoo.com>
swiatekm pushed a commit to swiatekm/opentelemetry-collector that referenced this pull request Oct 9, 2024
* Update examples for v1beta1

fixes open-telemetry#1333

* bump minor version and run generate-examples

is this really what they want me to do?

* bump the patch version, not the minor version
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.

3 participants