-
Notifications
You must be signed in to change notification settings - Fork 65
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
Support for custom exporter broke with versions V 3.1.1 #368
Comments
Hi @DarioBernardo , thanks for the message and apologies for the issue you are facing. With 3.1.1 we added native support for OTEL collector setups. While this should not have ideally impacted your setup, could you make sure you have the following env vars setup correctly?
This will ensure langtrace automatically picks up Also could you please upgrade to the latest version 3.3.14 so we can rule out any other issues. Please let me know if you face any issues. |
Also check out our guide here - https://www.langtrace.ai/blog/monitoring-a-langchain-rag-application-with-signoz-and-langtrace |
@DarioBernardo - please let us know if you were able to get this sorted. Thanks |
Hi @karthikscale3, Thank you for your quick reply and apologies with the delay of mine.
The above set up works fine with langtrace
and i don't see any trace. However, If I set the following env variable:
which is a good sign, however my application crashes with this error:
Therefore I had to immediately revert. Note: I didn't set the OTEL_EXPORTER_OTLP_HEADERS as I don't think i am requiring any access token, my application runs fine without. Thank you for your help |
Hey @DarioBernardo, apologies for the issue you're facing from the code you just shared, i see that some logic is being duplicated for setting up open-telemetry which is actually abstracted away by langtrace it self.
also can you expand how are you using signoz without access_token? as far as i know it's essential to connect to signoz and send traces also i want to share an example with you sending traces to signoz maybe could point out some tips
Enviroment variables
The issue is still not 100% clear but will be more than happy to help you out with any assistance you need, we will be prioritising this issue anytime! |
I am using signoz deployed on a private kubernetes cluster, so maybe for that reason the key is not necessary. I am not using signoz on cloud.
If I comment out the line you suggested I won't be able to initialize with the
Later it doesn't work because it requires a key, and I don't get any traces. |
This issue has been automatically marked as stale due to inactivity. It will be closed in 3 days if no further activity occurs. |
Hey @DarioBernardo, apologies for the long time taken on this issue can i kindly ask you to change langtrace initialization to just
Env variables to be set
hopefully this should work with your setup, will be waiting for feedback and will be more than happy to help and apologies again |
Hello,
First, thank you for the excellent work on
langtrace
. It's been incredibly useful for our organization.I’ve been using the SDK to export traces to our internal OpenTelemetry server (Signoz). Everything worked perfectly with
langtrace-python-sdk==2.3.22
. However, after upgrading to version 3.1.1 (and later), I stopped seeing traces in Signoz.It seems like something might have changed in how custom exporters are set up. I noticed the documentation mentions that an API key is not required (despite the red warning), but I no longer see the familiar log message: "Exporting spans to custom remote exporter...".
Could you clarify if there are new setup requirements or changes affecting custom exporters in version 3.1.1? Any guidance would be greatly appreciated.
Thank you!
The text was updated successfully, but these errors were encountered: