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.
   Note: Buffering options is in Preview. Contact your account manager to request access.
   • If left disabled, the maximum size for buffering is 500 events.
   • If enabled:
     1. Select the buffer type you want to set (Memory or Disk).
     2. Enter the buffer size and select the unit.

Set the environment variables

• HTTP/S client URI endpoint
  • Stored as the environment variable DD_OP_DESTINATION_HTTP_CLIENT_URI.
• If you are using basic authentication:
  • HTTP/S endpoint authentication username and password.
  • Stored as the environment variables: 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 as 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.