Présentation

Ce document explique comment envoyer les journaux fournis par AWS avec le Datadog Lambda Forwarder vers Observability Pipelines. Les étapes de configuration sont les suivantes:

• Configurez un pipeline avec la source HTTP/S Server.
• Déployez le Datadog Forwarder.

Consultez Datadog Forwarder pour en savoir plus à ce sujet.

Remarque : Le Datadog Forwarder envoie des journaux marqués avec ddsource et ddtags, et non source et tags. Lorsque vous définissez des requêtes ou des filtres de processeur pour ces logs, utilisez ddsource et ddtags.

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

Déployez le 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 the DNS or IP address of the load balancer or your VM. Note: Datadog recommends fronting your Worker with a load balancer.
2. Enter the port in the DdPort field, such as 9997.
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.

Métriques de santé

Pour les métriques de composant et les métriques de tampon source émises par toutes les sources, consultez la documentation Pipelines Usage Metrics. Puisque vous utilisez la source HTTP Server pour envoyer des journaux du Lambda Forwarder vers Observability Pipelines, utilisez le tag component_type:http_server pour filtrer les métriques pertinentes.