Socket Source

This product is not supported for your selected Datadog site. ().
このページは日本語には対応しておりません。随時翻訳に取り組んでいます。
翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。
次で利用可能:

Logs

Overview

Use Observability Pipelines’ Socket source to send logs to the Worker over a socket connection (TCP or UDP).

Prerequisites

If your forwarders are globally configured to enable SSL, you need the appropriate TLS certificates and the password for your private key.

Setup

Set up this source when you set up a pipeline. You can set up a pipeline in the UI, using the API, or with Terraform. The instructions in this section are for setting up the source in the UI.

For Secrets Management: Only enter the identifiers for the socket address and, if applicable, the TLS key pass. Do not enter the actual values.
If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP_. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.

After you select the Socket source in the pipeline UI:

  1. Enter the identifier for your socket address. If you leave it blank, the default is used.
  2. In the Mode dropdown menu, select the socket type to use.
  3. In the Framing dropdown menu, select how to delimit the stream of events.
    FRAMING METHODDESCRIPTION
    newline_delimitedByte frames are delimited by a newline character.
    bytesByte frames are passed through as-is according to the underlying I/O boundaries (for example, split between messages or stream segments).
    character_delimitedByte frames are delimited by a chosen character.
    chunked_gelfByte frames are chunked GELF messages.
    octet_countingByte frames are delimited according to the octet counting format.

Optional TLS settings

Toggle the switch to Enable TLS.

  • If you are using Secrets Management, enter the identifier for the key pass. See Set secrets for the default used if the field is left blank.
  • 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, PEM, or CRT (X.509).
    • CA Certificate Path: The path to the certificate file that is your Certificate Authority (CA) root file in DER, PEM, or CRT (X.509).
    • Private Key Path: The path to the .key private key file that belongs to your Server Certificate Path in DER, PEM, or CRT (PKCS #8) format.
    • Notes:
      • The configuration data directory /var/lib/observability-pipelines-worker/config/ is automatically appended to the file paths. See Advanced Worker Configurations for more information.
      • The file must be readable by the observability-pipelines-worker group and user.
  • (Optional) Toggle Verify certificate to require connecting clients to present a valid client certificate. This enforces mutual TLS (mTLS), where the Worker verifies the identity of each connecting client.

Secret defaults

These are the defaults used for secret identifiers and environment variables.

    • Socket address identifier:
      • References the address and port where the Observability Pipelines Worker listens for incoming logs.
      • The default identifier is SOURCE_SOCKET_ADDRESS.
    • Socket TLS passphrase identifier (when TLS is enabled):
      • The default identifier is SOURCE_SOCKET_KEY_PASS.

    • Socket address:

      • The address and port where the Observability Pipelines Worker listens for incoming logs.
      • The default environment variable is DD_OP_SOURCE_SOCKET_ADDRESS.

    • TLS passphrase (when enabled):

      • The default environment variable is DD_OP_SOURCE_SOCKET_KEY_PASS.