Too many installs are having issues with file permissions for the core agent unix socket. The core agent has the ability to listen on a TCP socket. Change the agent code to default to using only the TCP socket, but make sure we can still use the unix socket option too.
Change the default core_agent_socket_path to tcp://127.0.0.1:6590.
Any socket path that begins with tcp:// connect via a TCP socket instead of the current Unix Domain Socket
Start the core agent with the --tcp <bind> flag to match.
Ensure the socket behaves the same as with unix socket - e.g. reconnecting after unexpected disconnect, etc.
The argument to start the core agent with a TCP socket:
--tcp <tcp-bind> TCP Socket to bind to, in form of ip:port (0.0.0.0:8383 for instance). If unset, no TCP socket is created.
Too many installs are having issues with file permissions for the core agent unix socket. The core agent has the ability to listen on a TCP socket. Change the agent code to default to using only the TCP socket, but make sure we can still use the unix socket option too.
core_agent_socket_pathtotcp://127.0.0.1:6590.--tcp <bind>flag to match.The argument to start the core agent with a TCP socket:
See-Also Matching Python Agent Issue