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

Collector Contrib fails to recognise "insecure" option #5377

Closed
iNikem opened this issue Sep 22, 2021 · 10 comments
Closed

Collector Contrib fails to recognise "insecure" option #5377

iNikem opened this issue Sep 22, 2021 · 10 comments
Labels
bug Something isn't working

Comments

@iNikem
Copy link
Contributor

iNikem commented Sep 22, 2021

Describe the bug
When provided with the following simple configuration, collector-contrib fails to start:

receivers:
  otlp:
    protocols:
      grpc:

exporters:
  otlp:
    endpoint: backend:8080
    insecure: true

service:
  pipelines:
    traces:
      receivers: [ otlp ]
      exporters: [ otlp ]

Error:

Error: cannot load configuration: error reading exporters configuration for otlp: 1 error(s) decoding:

* '' has invalid keys: insecure

What version did you use?
Docker image otel/opentelemetry-collector-contrib:latest, version 0.34.0

Docker image otel/opentelemetry-collector:latest, version 0.34.0 works find without any error.

@iNikem iNikem added the bug Something isn't working label Sep 22, 2021
@iNikem
Copy link
Contributor Author

iNikem commented Sep 22, 2021

I have just noticed, why latest docker image uses 0.34, when latest version is 0.36? But still, this does not explain the difference between core and contrib collectors

@mx-psi
Copy link
Member

mx-psi commented Sep 22, 2021

open-telemetry/opentelemetry-collector#4063 changed the way this setting is specified (it is now under the tls section), so probably it explains this

@bogdandrutu
Copy link
Member

@iNikem see previous comment, that was a breaking change unfortunately.

@iNikem
Copy link
Contributor Author

iNikem commented Sep 22, 2021

Does this mean that https://opentelemetry.io/docs/collector/configuration/#exporters and https://github.com/open-telemetry/opentelemetry-collector/blob/main/exporter/otlpexporter/README.md and related docs were left unchanged?

@iNikem
Copy link
Contributor Author

iNikem commented Sep 22, 2021

Also, why the difference between core and contrib images?

@almeidaalex
Copy link

open-telemetry/opentelemetry-collector#4063 changed the way this setting is specified (it is now under the tls section), so probably it explains this

I've changed my config to:

 jaeger:
    endpoint: jaeger-all-in-one:14250
    tls:
      insecure: true

Now it's not complaining about this error

@ganga-sah
Copy link

open-telemetry/opentelemetry-collector#4063 changed the way this setting is specified (it is now under the tls section), so probably it explains this

I've changed my config to:

 jaeger:
    endpoint: jaeger-all-in-one:14250
    tls:
      insecure: true

Now it's not complaining about this error

thanks @almeidaalex for the tip! You unblocked me!

@dmitryax
Copy link
Member

Closing the issues since all the documentation looks updated to the new configuration interface

hex1848 pushed a commit to hex1848/opentelemetry-collector-contrib that referenced this issue Jun 2, 2022
* [docs] add status header for OTLP receiver

Fixes open-telemetry#5376

* add stability per signal

* Update README.md
@delanym
Copy link

delanym commented Jul 13, 2022

Just got burnt by this again because I forget that
https://hub.docker.com/r/otel/opentelemetry-collector/tags?page=1&name=latest
isn't updated anymore

@mx-psi
Copy link
Member

mx-psi commented Jul 13, 2022

Just got burnt by this again because I forget that https://hub.docker.com/r/otel/opentelemetry-collector/tags?page=1&name=latest isn't updated anymore

This is tracked at open-telemetry/opentelemetry-collector-releases/issues/73, please upvote the issue there if fixing this would have helped you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

7 participants