Overview

Use Observability Pipelines’ HTTP Client destination to send logs to an HTTP client, such as a logging platform or SIEM.

Set up destination

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

1. Select your authorization strategy (None, Basic, or Bearer).
2. JSON is the only available encoder.
3. Optionally, toggle the switch to enable compression. If enabled:
   1. GZIP is the only available compression algorithm.
   2. Select the compression level you want to use.
4. 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.
5. 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

• HTTP/S client URI endpoint:
  • Stored in the environment variable DD_OP_DESTINATION_HTTP_CLIENT_URI.
• HTTP/S Client TLS passphrase (when enabled):
  • Stored in the environment variable DD_OP_DESTINATION_HTTP_CLIENT_KEY_PASS.
• If you are using basic authentication:
  • HTTP/S endpoint authentication username and password.
  • Stored in the environment variable DD_OP_DESTINATION_HTTP_CLIENT_USERNAME and DD_OP_DESTINATION_HTTP_CLIENT_PASSWORD.
• If you are using bearer authentication:
  • HTTP/S endpoint bearer token.
  • Stored in the environment variable DD_OP_DESTINATION_HTTP_CLIENT_BEARER_TOKEN.

How the destination works

Event batching

A batch of events is flushed when one of these conditions occurs. See event batching for more information.