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

otlp: want error went WithInsecure is needed #1735

Closed
andreimatei opened this issue Mar 26, 2021 · 1 comment · Fixed by #1737
Closed

otlp: want error went WithInsecure is needed #1735

andreimatei opened this issue Mar 26, 2021 · 1 comment · Fixed by #1737
Milestone

Comments

@andreimatei
Copy link
Contributor

I spent a bunch of time figuring out that a basic example app trying to send traces to an OpenTelemetry collector running locally wants an otlp.WithInsecure() in order to work.
Some sort of error or log message to tell me this would have been great.

I was getting an "exporter disconnected" log message from somewhere, but I couldn't tell much from that.

@paivagustavo
Copy link
Member

Hey @andreimatei, sorry for that unhelpful error message.

The OTLP gRPC driver only checks if the connections is still active and if not it returns a default "exporter disconnected" error.

I think this should be easily fixed if we wrap the connection error, giving a more detailed error message, for example:

2021/03/26 18:11:24 exporter disconnected: grpc: no transport security set (use grpc.WithInsecure() explicitly or set credentials)

I'll be creating a PR to fix this soon.

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 a pull request may close this issue.

3 participants