-
Notifications
You must be signed in to change notification settings - Fork 821
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
Use http keep-alive for OTLP/HTTP #1638
Comments
Hi @mwear, I would like to work on this. |
@lonewolf3739 Feel free to ping if you want some help ! |
@vmarchaud , Thanks! I have a question regarding the value setting for header. What values should be set for |
I think everything should be configurable from the exporter config (it should be possible to disable keep alive too). For the defaults, i believe nodejs already defaults no ? |
Yes, makes sense. May we should add some env like
Yes, it does. Thank you. |
As discussed at the SIG meeting earlier today, we can improve the performance of our collector exporter by reusing http connections with http keep-alive. This strategy would apply to proto over http and json over http export formats.
The text was updated successfully, but these errors were encountered: