Ce produit n'est pas pris en charge par le site Datadog que vous avez sélectionné. ().
Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.
Disponible pour:

Logs

Use Observability Pipelines’ Socket source to send logs to the Worker over a socket connection (TCP or UDP). Select and set up this source when you set up a pipeline.

Prerequisites

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

Set up the source in the pipeline UI

Select and set up this source when you set up a pipeline. The information below is for the source settings in the pipeline UI.

Only enter the identifiers for the socket address and, if applicable, the TLS key pass. Do not enter the actual values.
  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 settings

If you selected TCP mode, toggle the switch to Enable TLS. The following certificate and key files are required for TLS.
Note: All file paths are made relative to the configuration data directory, which is /var/lib/observability-pipelines-worker/config/ by default. See Advanced Worker Configurations for more information. The file must be owned by the observability-pipelines-worker group and observability-pipelines-worker user, or at least readable by the group or user.

  • Enter the identifier for your socket key pass. If you leave it blank, the default is used.
  • 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 secrets

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

Note: If you enter identifiers for your secrets 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.

  • 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.