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.
4. Optionally, toggle the switch to enable Buffering Options. Enable a configurable buffer on your destination to ensure intermittent latency or an outage at the destination doesn’t create immediate backpressure, and allow events to continue to be ingested from your source. Disk buffers can also increase pipeline durability by writing logs to disk, ensuring buffered logs persist through a Worker restart. See Configurable buffers for destinations for more information.
   • If left unconfigured, your destination uses a memory buffer with a capacity of 500 events.
   • To configure a buffer on your destination:
     1. Select the buffer type you want to set (Memory or Disk).
     2. Enter the buffer size and select the unit.
        • Maximum memory buffer size is 128 GB.
        • Maximum disk buffer size is 500 GB.

Set the environment variables

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

How the destination works

Event batching

The Socket destination does not batch events.