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

Unknown extensions type "jaegerremotesampling" #8554

Closed
sakthiraam opened this issue Mar 19, 2022 · 1 comment
Closed

Unknown extensions type "jaegerremotesampling" #8554

sakthiraam opened this issue Mar 19, 2022 · 1 comment
Labels
bug Something isn't working comp:jaeger Jaeger related issues

Comments

@sakthiraam
Copy link

sakthiraam commented Mar 19, 2022

Describe the bug
I'm using the latest version of otel collector contrib and getting Unknown extensions type "jaegerremotesampling"

Steps to reproduce
run the otel collector contrib executable with the below yaml configuration.

What did you expect to see?
otel collector to start with jaegerremotesampling extension listening of gRPC and http port number defined in the config

What did you see instead?
A error as below

$ ./otelcol-contrib --config=file:./otel_test_config.yml
2022/03/19 12:08:08 proto: duplicate proto type registered: jaeger.api_v2.PostSpansRequest
2022/03/19 12:08:08 proto: duplicate proto type registered: jaeger.api_v2.PostSpansResponse
Error: failed to get config: cannot unmarshal the configuration: unknown extensions type "jaegerremotesampling" for "jaegerremotesampling" (valid values: [zpages oidc pprof memory_ballast k8s_observer asapclient fluentbit oauth2client host_observer awsproxy basicauth bearertokenauth health_check http_forwarder file_storage])
2022/03/19 12:08:08 collector server run finished with error: failed to get config: cannot unmarshal the configuration: unknown extensions type "jaegerremotesampling" for "jaegerremotesampling" (valid values: [zpages oidc pprof memory_ballast k8s_observer asapclient fluentbit oauth2client host_observer awsproxy basicauth bearertokenauth health_check http_forwarder file_storage])

What version did you use?
Version: otel collector contrib - 0.47.0

What config did you use?

extensions:
  memory_ballast:
    size_in_percentage: 40
  zpages:
    endpoint: 0.0.0.0:55679
  health_check:
    endpoint: 0.0.0.0:13133
  health_check/1:
    endpoint: 0.0.0.0:13134
    check_collector_pipeline:
      enabled: true
      interval: "5m"
      exporter_failure_threshold: 5
  pprof:
    endpoint: 0.0.0.0:1888
  jaegerremotesampling:
    http:
      endpoint: :5878
    source:
      file: /home/test/otel/strategy.json
receivers:
  otlp:
    protocols:
      grpc:
      http:
processors:
  batch:
  memory_limiter:
    limit_mib: 1536
    spike_limit_mib: 512
    check_interval: 5s
exporters:
  logging:
    logLevel: debug
service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [memory_limiter, batch]
      exporters: [logging]
    metrics:
      receivers: [otlp]
      processors: [memory_limiter, batch]
      exporters: [logging]
  extensions: [memory_ballast, zpages, health_check, pprof, jaegerremotesampling]

Environment
OS: CentOS 7

Additional context
Add any other context about the problem here.

@sakthiraam sakthiraam added the bug Something isn't working label Mar 19, 2022
@jpkrohling
Copy link
Member

The Jaeger Remote Sampling extension isn't functional yet, and because of that, it hasn't been added to the distribution. See #6510 to keep an eye on the progress.

@jpkrohling jpkrohling added the comp:jaeger Jaeger related issues label Jul 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working comp:jaeger Jaeger related issues
Projects
None yet
Development

No branches or pull requests

2 participants