datadog分析之opentelemetry

datadog支持应用侧使用open telemetry的sdk或agent，此时有2种方法可以接入datadog后端：

image.png

使用otel sdk代替datadog的sdk，会损失一些dd的特殊能力：
Application Security Management, Continuous Profiler, Runtime Metrics, and Ingestion Rules

1、使用otel collector，使用[ Datadog exporter] 接入到datadog

配置文件：

receivers:
  otlp:
    protocols:
      http:
      grpc:
  # The hostmetrics receiver is required to get correct infrastructure metrics in Datadog.
  hostmetrics:
    collection_interval: 10s
    scrapers:
      paging:
        metrics:
          system.paging.utilization:
            enabled: true
      cpu:
        metrics:
          system.cpu.utilization:
            enabled: true
      disk:
      filesystem:
        metrics:
          system.filesystem.utilization:
            enabled: true
      load:
      memory:
      network:
      processes:
  # The prometheus receiver scrapes metrics needed for the OpenTelemetry Collector Dashboard.
  prometheus:
    config:
      scrape_configs:
      - job_name: 'otelcol'
        scrape_interval: 10s
        static_configs:
        - targets: ['0.0.0.0:8888']

  filelog:
    include_file_path: true
    poll_interval: 500ms
    include:
      - /var/log/**/*example*/*.log

processors:
  batch:
    send_batch_max_size: 100
    send_batch_size: 10
    timeout: 10s

exporters:
  datadog:
    api:
      site: <DD_SITE>
      key: ${env:DD_API_KEY}

service:
  pipelines:
    metrics:
      receivers: [hostmetrics, otlp]
      processors: [batch]
      exporters: [datadog]
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [datadog]
    logs:
      receivers: [otlp, filelog]
      processors: [batch]
      exporters: [datadog]

2、otel sdk或agent直接对接到datadog的agent

因为dd的agent也实现了otel otlp接口

datadog agent的配置文件：

otlp_config:
  receiver:
    protocols:
      grpc:
        endpoint: localhost:4317

otel agent设置：
OTEL_EXPORTER_OTLP_ENDPOINT=http://<datadog-agent>:4318.