Datadog Agent Source

This product is not supported for your selected Datadog site. ().
このページは日本語には対応しておりません。随時翻訳に取り組んでいます。
翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。
次で利用可能:

Logs | Metrics

Use Observability Pipelines’ Datadog Agent source to receive logs or metrics (PREVIEW indicates an early access version of a major product or feature that you can opt into before its official release.Glossary) from the Datadog Agent.

Note: If you are using the Datadog Distribution of OpenTelemetry (DDOT) Collector for logs, you must use the OpenTelemetry source to send logs to Observability Pipelines.

Prerequisites

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

You have the following information available:

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.

To configure your Datadog Agent source:

Only enter the identifier for the Datadog Agent address and, if applicable, the TLS key pass. Do not enter the actual values.

Enter the identifier for your Datadog Agent address. If you leave it blank, the default is used.

Optional settings

Toggle the switch to 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 Worker Configurations for more information. The file must be owned by the observability-pipelines-worker user and group, or at least readable by the group or user.

  • Enter the identifier for your Datadog Agent key pass. If you leave it blank, the default is used.
    • Note: Only enter the identifier for the key pass. Do not enter the actual key pass.
  • 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.

Set secrets

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

Note: 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.

    • Datadog Agent address identifier:
      • References the bind address on which the Observability Pipelines Worker listens to receive logs from the Datadog Agent.
      • The default identifier is SOURCE_DATADOG_AGENT_ADDRESS.
    • Datadog Agent TLS passphrase identifier (when TLS is enabled):
      • The default identifier is SOURCE_DATADOG_AGENT_KEY_PASS.
    • Datadog Agent address:
      • The Observability Pipelines Worker listens to this socket address to receive logs from the Datadog Agent.
      • The default environment variable is DD_OP_SOURCE_DATADOG_AGENT_ADDRESS.
    • Datadog Agent TLS passphrase (when enabled):
      • The default environment variable is DD_OP_SOURCE_DATADOG_AGENT_KEY_PASS.

    Connect the Datadog Agent to the Observability Pipelines Worker

      Use the Agent configuration file or the Agent Helm chart values file to connect the Datadog Agent to the Observability Pipelines Worker.

      Note: If your Agent is running in a Docker container, you must exclude Observability Pipelines logs using the DD_CONTAINER_EXCLUDE_LOGS environment variable. For Helm, use datadog.containerExcludeLogs. This prevents duplicate logs, as the Worker also sends its own logs directly to Datadog. See Docker Log Collection or Setting environment variables for Helm for more information.

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

      Use the Agent configuration file or the Agent Helm chart values file to connect the Datadog Agent to the Observability Pipelines Worker.

      Note: If your Agent is running in a Docker container, you must exclude Observability Pipelines metrics, such as utilization and events in/out metrics, using the DD_CONTAINER_EXCLUDE_METRICS environment variable. For Helm, use datadog.containerExcludeMetrics. This prevents duplicate metrics, as the Worker also sends its own metrics directly to Datadog. See Docker Metrics Collection or Setting environment variables for Helm for more information.

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

      observability_pipelines_worker:
  metrics:
    enabled: true
    url: "http://<OPW_HOST>:8383"

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

      Note: If the Worker is listening for logs on port 8282, you must use another port for metrics, such as 8383.

      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 metrics 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_METRICS_ENABLED
      value: true
    - name: DD_OBSERVABILITY_PIPELINES_WORKER_METRICS_URL
      value: "http://<OPW_HOST>:8383"

      <OPW_HOST> is the host IP address or the load balancer URL 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>.

      Note: If the Worker is listening for logs on port 8282, you must use another port for metrics, such as 8383.

      Further Reading

      お役に立つドキュメント、リンクや記事:

      Manage metric volume and tags in your environment with Observability PipelinesBLOG more more