Fuente del Datadog Agent

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

Utiliza la fuente del Datadog Agent de Observability Pipelines para recibir logs de tu Datadog Agent. Selecciona y configura esta fuente cuando configures un pipeline.

Requisitos previos

You already have the Datadog Agent installed to collect and route your logs to Datadog Log Management. If you do not have Datadog Agents set up, see the Datadog Agent documentation for more information.

You have the following information available:

Configurar la fuente en la interfaz de usuario del pipeline

Optionally, toggle the switch to enable TLS. If you enable TLS, 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 or PEM (X.509) format.
  • CA Certificate Path: The path to the certificate file that is your Certificate Authority (CA) Root File in DER or PEM (X.509) format.
  • 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.

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.

Conectar el Datadog Agent al worker de Observability Pipelines

Utiliza el archivo de configuración del Agent o el archivo de valores del Helm chart del Agent para conectar el Datadog Agent al worker de Observability Pipelines.

    To send Datadog Agent logs to the Observability Pipelines Worker, update your Agent configuration file with the following:

    observability_pipelines_worker:
  logs:
    enabled: true
    url: "http://<OPW_HOST>:8282"

    <OPW_HOST> is the host IP address or the load balancer URL associated with the Observability Pipelines Worker.

    For CloudFormation installs, use the LoadBalancerDNS CloudFormation output for the URL.

    For Kubernetes installs, you can use the internal DNS record of the Observability Pipelines Worker service. For example: http://opw-observability-pipelines-worker.default.svc.cluster.local:<PORT>.

    After you restart the Agent, your observability data should be going to the Worker, processed by the pipeline, and delivered to Datadog.

    To send Datadog Agent logs to the Observability Pipelines Worker, update your Datadog Helm chart datadog-values.yaml with the following environment variables. See Agent Environment Variables for more information.

    datadog:
  env:
    - name: DD_OBSERVABILITY_PIPELINES_WORKER_LOGS_ENABLED
      value: true
    - name: DD_OBSERVABILITY_PIPELINES_WORKER_LOGS_URL
      value: "http://<OPW_HOST>:8282"

    <OPW_HOST> is the IP/URL of the host (or load balancer) associated with the Observability Pipelines Worker.

    For Kubernetes installs, you can use the internal DNS record of the Observability Pipelines Worker service. For example: http://opw-observability-pipelines-worker.default.svc.cluster.local:<PORT>.