Utiliza la fuente del servidor HTTP/S de Observability Pipelines para recopilar logs HTTP del cliente. Selecciona y configura esta fuente cuando configures un pipeline.

También puedes enviar logs de AWS con el Datadog Lambda Forwarder a Observability Pipelines.

Requisitos previos

To use Observability Pipelines’ HTTP/S Server source, you need the following information available:

• The HTTP/S server address, such as 0.0.0.0:9997. The Observability Pipelines Worker listens to this socket address for your HTTP client logs.
• The HTTP authentication password.

Configurar la fuente en la interfaz de usuario del pipeline

Selecciona y configura esta fuente cuando configures un pipeline. La siguiente información se refiere a la configuración de la fuente en la interfaz de usuario del pipeline.

To configure your HTTP/S Server source, enter the following:

1. Select your authorization strategy.
2. Select the decoder you want to use on the HTTP messages. Your HTTP client logs must be in this format. Note: If you select bytes decoding, the raw log is stored in the message field.
3. Optionally, toggle the switch to enable TLS. If you enable TLS, the following certificate and key files are required.
   Note: All file paths are made relative to the configuration data directory, which is /var/lib/observability-pipelines-worker/config/ by default. See Advanced 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.
   • 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.

Enviar logs de AWS con el Datadog Lambda Forwarder a Observability Pipelines

Para enviar logs de AWS a Observability Pipelines con la fuente del servidor HTTP/S:

• Configura un pipeline con la fuente del servidor HTTP/S.
• Despliega el Datadog Forwarder.

Nota: Esto está disponible para las versiones del worker 2.51 o posteriores.

Establecer un pipeline

1. Navigate to Observability Pipelines.
2. Select the HTTP Server source:
   1. Select None in the dropdown menu for Authorization strategy.
   2. Select JSON in the dropdown menu for Decoding.
3. After you set up your destinations and processors, click Next: Install.
4. On the Install page, enter the HTTP/S Server listener address, such as 0.0.0.0:9997.
5. Follow the rest of the instructions on the page to install the Worker based on your platform.

Despliegue del Datadog Lambda Forwarder

Follow the Datadog Forwarder CloudFormation installation instructions to deploy the Datadog Forwarder. After you have filled in DdApiKey and selected the appropriate DdSite, go to the Log Forwarding (Optional) section. Enter the following information in that section to configure the Forwarder for sending logs to Observability Pipelines:

1. In the DdUrl field, enter your load balancer address, which for this example is 9997. Note: Datadog recommends fronting your Worker with a load balancer.
2. In the DdPort field, enter 80.
3. If you want to encrypt traffic from the Datadog Forwarder to your Observability Pipelines Worker load balancer, you need to create an HTTPS listener and manage a certificate on your load balancer. Consult your cloud provider’s documentation. For example in AWS, see Create an HTTPS listener for your Application Load Balancer for more information.
4. If you do not need to maintain encryption between the Datadog Forwarder and load balancer, select true in the DdNoSsl dropdown menu.
5. Click Create stack, and wait for the creation to complete.
6. You can find the installed forwarder Lambda function under the stack’s Resources tab with the logical ID Forwarder.
7. Set up triggers for the installed Datadog Forwarder.