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

[extension/jaegerremotesampling] This extension may be broken after importing Jaeger v1.42 code #18047

Closed
yurishkuro opened this issue Jan 26, 2023 · 7 comments

Comments

@yurishkuro
Copy link
Member

Component(s)

extension/jaegerremotesampling

Describe the issue you're reporting

This is just a heads-up issue with some pointers.

This extension uses json.Marshal from stdlib to render the sampling strategy:

and has a unit test that validates the format (kudos):

assert.Equal(t, `{"strategyType":"PROBABILISTIC"}`, body)

However, it passes an auto-inferred type from samplingStore to json.Marshal, which happens to be Thrift-gen struct. This is changing in the next Jaeger release (jaegertracing/jaeger#4181) to return Protobuf-gen struct, that may not work with stdlib json.Marshal (in Jaeger we're using jsonpb.Marshal from gogoproto).

Related issues:

Also, this extension attempts to emulate Jaeger agent endpoints, but their behavior on / and /sampling endpoint is actually different (explained in open-telemetry/opentelemetry-go-contrib#3184)

@yurishkuro yurishkuro added the needs triage New item requiring triage label Jan 26, 2023
@github-actions
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@jpkrohling
Copy link
Member

@frzifus, are you able to handle this one?

@github-actions
Copy link
Contributor

github-actions bot commented May 8, 2023

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label May 8, 2023
@jpkrohling
Copy link
Member

ping @frzifus

@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Aug 28, 2023
@frzifus frzifus removed the Stale label Aug 28, 2023
codeboten pushed a commit that referenced this issue Sep 6, 2023
…ypes for sampling strategies (#18485)

Add featuregates to replace Thrift-gen with Proto-gen types for sampling strategies. Available featuregates are:
  - extension.jaegerremotesampling.replaceThriftWithProto
  - receiver.jaegerreceiver.replaceThriftWithProto
 
Closes #18401 
Ref #18047

--

cc @jpkrohling

---------

Signed-off-by: Benedikt Bongartz <[email protected]>
Co-authored-by: Juraci Paixão Kröhling <[email protected]>
@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Oct 30, 2023
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants