Use Observability Pipelines’ Socket destination to send logs to a socket endpoint.

Setup

Set up the Socket destination and its environment variables when you set up a pipeline. The following information is configured in the pipelines UI.

Set up the destination

1. In the Mode dropdown menu, select the socket type to use.
2. In the Encoding dropdown menu, select either JSON or Raw message as the output format.
3. Optionally, toggle the switch to enable TLS. If you enable TLS, the following certificate and key files are required:
   • Server Certificate Path: The path to the certificate file that has been signed by your Certificate Authority (CA) Root File in DER or PEM (X.509).
   • CA Certificate Path: The path to the certificate file that is your Certificate Authority (CA) Root File in DER or PEM (X.509).
   • Private Key Path: The path to the .key private key file that belongs to your Server Certificate Path in DER or PEM (PKCS#8) format.

Set the environment variables

• Socket address:
  • The address to which the Observability Pipelines Worker sends processed logs.
  • Stored as the environment variable DD_OP_DESTINATION_SOCKET_ADDRESS.
• TLS passphrase:
  • Stored as the environment variable DD_OP_DESTINATION_SOCKET_KEY_PASS.

How the destination works

Event batching

The Socket destination does not batch events.