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

can't exporter jaeger gRPC #2694

Closed
tonycody opened this issue May 16, 2022 · 14 comments
Closed

can't exporter jaeger gRPC #2694

tonycody opened this issue May 16, 2022 · 14 comments
Labels
bug Something isn't working

Comments

@tonycody
Copy link
Contributor

tonycody commented May 16, 2022

The following was installed before use

pip install opentelemetry-api
pip install opentelemetry-sdk
pip install opentelemetry-exporter-jaeger-proto-grpc

Export Jaeger using gRPC.

opentelemetry-instrument --service_name=python-server-otel-demo --log_level=debug --exporter_jaeger_endpoint=http://localhost:14250 --traces_exporter=jaeger_proto python server_uninstrumented.py

There are no errors.How do I Enable Debug?

Sample script:https://github.com/open-telemetry/opentelemetry-python/tree/main/docs/examples/auto-instrumentation

@tonycody tonycody added the bug Something isn't working label May 16, 2022
@srikanthccv
Copy link
Member

Did you install opentelemetry-distro as mentioned in docs? Can you see the traces with the console exporter?

@tonycody
Copy link
Contributor Author

Did you install opentelemetry-distro as mentioned in docs? Can you see the traces with the console exporter?

It has been installed.
--traces_exporter=console is OK

@srikanthccv
Copy link
Member

Does the collector has encryption, you probably need to set insecure=True? Do you see any warning logs with message "Failed to export batch. Status code: xxx"?

@tonycody
Copy link
Contributor Author

Does the collector has encryption, you probably need to set insecure=True? Do you see any warning logs with message "Failed to export batch. Status code: xxx"?

Without any hint.
insecure=True is not set separately

@srikanthccv
Copy link
Member

If you don't set it to True it assumes that encryption is enabled and uses secure_channel which might be causing the problem.

@tonycody
Copy link
Contributor Author

If you don't set it to True it assumes that encryption is enabled and uses secure_channel which might be causing the problem.

How to set up insecure=True?

@srikanthccv
Copy link
Member

looks like there is no way to do that with command line arg, Here is an example showing the usage https://opentelemetry-python.readthedocs.io/en/latest/exporter/jaeger/jaeger.html#id1.

@tonycody
Copy link
Contributor Author

looks like there is no way to do that with command line arg, Here is an example showing the usage https://opentelemetry-python.readthedocs.io/en/latest/exporter/jaeger/jaeger.html#id1.

This is set through the code, I am through the autoinstrument, I do not quite understand how to set

@tonycody
Copy link
Contributor Author

looks like there is no way to do that with command line arg, Here is an example showing the usage https://opentelemetry-python.readthedocs.io/en/latest/exporter/jaeger/jaeger.html#id1.

How do I turn on debug mode when using-- traces_exporter=jaeger_proto? Can you display the export log? In a way similar to OTEL_JAVAAGENT_DEBUG=true?

@srikanthccv
Copy link
Member

There isn't really a debug mode in python auto instrumentation, we try to log the warning/error messages in an event of issues from the backends like jaeger/otlp/zipkin. If you are able to get the console exporter working then the trace pipeline is working fine but you have issue with setting up the jaeger exporter. I suspect it's the creds issue.

@tonycody
Copy link
Contributor Author

There isn't really a debug mode in python auto instrumentation, we try to log the warning/error messages in an event of issues from the backends like jaeger/otlp/zipkin. If you are able to get the console exporter working then the trace pipeline is working fine but you have issue with setting up the jaeger exporter. I suspect it's the creds issue.

Try submitting PR, review and have a look

@pythrick
Copy link

I was facing similar problem just a few hours ago, this thread help me understand that auto-instrumentation does work with grpc, only with http: open-telemetry/opentelemetry-operator#862 (comment)

@srikanthccv
Copy link
Member

The statement that auto-instrumentation only works with http is not true. It works with both grpc and http. But the operator doesn't support for the reason they explained here.

@srikanthccv
Copy link
Member

Added support for insecure env in #2696 . Please try setting it to true and try again.

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

3 participants