Destino de socket

Este producto no es compatible con el sitio Datadog seleccionado. ().
Disponible para:

Registros

Descripción general

Utilice el destino de socket de Observability Pipelines para enviar registros a un punto de conexión de socket.

Configuración

Para la gestión de secretos: ingrese únicamente el identificador para la dirección del socket y, si corresponde, el key pass. No ingrese los valores reales.

Configure el destino de socket cuando configure un pipeline. Puede configurar un pipeline en la UI, utilizando la API o con Terraform. Los pasos en esta sección se configuran en la interfaz de usuario.

Después de seleccionar el destino de socket en la UI del pipeline:

  1. Ingrese el identificador para su dirección. Si lo deja en blanco, se utiliza el predeterminado.
  2. En el menú desplegable Mode, seleccione el tipo de socket que desea utilizar.
  3. En el menú desplegable Encoding, seleccione JSON o Raw message como formato de salida.
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.

Configuración opcional

Habilitar TLS

Toggle the switch to Enable TLS.

  • If you are using Secrets Management, enter the identifier for the key pass. See Secret defaults for the default used if the field is left blank.
  • Enter the following certificate and key files:
    • 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).
    • (Optional) CA Certificate Path: The path to the certificate file that is your Certificate Authority (CA) root file in DER, PEM, or CRT (X.509).
    • (Optional) 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.

Almacenamiento en búfer

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 data to disk, ensuring buffered data persists through a Worker restart. See Destination buffers 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.
      1. Maximum memory buffer size is 128 GB.
      2. Maximum disk buffer size is 5 TB.
        • Note: For Worker versions 2.20.x and older, the maximum disk buffer size is 500 GB.
    3. In the Behavior on full buffer dropdown menu, select whether you want to block events or drop new events when the buffer is full.

Valores predeterminados de Secret

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

    • Identificador de dirección de socket:
      • Hace referencia a la dirección a la que el Observability Pipelines Worker envía los registros procesados.
      • El identificador predeterminado es DESTINATION_SOCKET_ADDRESS.
    • Identificador de frase de contraseña TLS del socket (cuando TLS está habilitado):
      • El identificador predeterminado es DESTINATION_SOCKET_KEY_PASS.
    • Socket address:
      • The address to which the Observability Pipelines Worker sends processed logs.
      • The default environment variable is DD_OP_DESTINATION_SOCKET_ADDRESS.
    • TLS passphrase:
      • The default environment variable is DD_OP_DESTINATION_SOCKET_KEY_PASS.

    Cómo funciona el destino

    Procesamiento por lotes de eventos

    El destino de socket no agrupa eventos.