You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to incorporate OTLP into an existing server application that forks the process to handle each client request.
So far I've found that gRPC is a no-go without rebuilding with fork support, but even then I'm not sure how to enable this through opentelemetry-cpp. HTTP seems to work fine for a while, but under enough load the number of ephemeral sockets is exhausted because of time wait (I haven't worked out if the library is letting curl maintain 1 connection per-process yet or if a new connection is made per log entry, but I'm suspecting the former).
Are there any known strategies for using the library in forking applications?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm trying to incorporate OTLP into an existing server application that forks the process to handle each client request.
So far I've found that gRPC is a no-go without rebuilding with fork support, but even then I'm not sure how to enable this through opentelemetry-cpp. HTTP seems to work fine for a while, but under enough load the number of ephemeral sockets is exhausted because of time wait (I haven't worked out if the library is letting curl maintain 1 connection per-process yet or if a new connection is made per log entry, but I'm suspecting the former).
Are there any known strategies for using the library in forking applications?
Beta Was this translation helpful? Give feedback.
All reactions