Quick Guide for Datadog Agent on Kubernetes for Traces

  1. Add the Datadog Helm repository.

    helm repo add datadog https://helm.datadoghq.com
helm repo update
    yaml

  2. Configure datadog-values.yaml.

    For pod-level traces, add Datadog annotations to enable scraping.

  3. Base configuration

    fullnameOverride: "kfuse-agent"
nameOverride: "kfuse-agent"
datadog:
  apiKey: " "
  #
  # Scenario default: Assumes that Kloudfuse stack & agent both in same VPC and in same K8S cluster
  #
  dd_url: "http://kfuse-ingress-nginx-controller-internal.kfuse/ingester"
  #
  # Scenario 1: Kloudfuse stack & agent both in same VPC, but in different K8S cluster
  #
  # dd_url: "http://<ingress-ip>/ingester"
  #
  # Scenario 2: Kloudfuse stack hosted in a different VPC (hosted at “customer.kloudfuse.io”)
  #
  # dd_url: "https://customer.kloudfuse.io/ingester"
  #
    yaml

  4. Enable tracing.

    ...
datadog:
  ...
  apm:
    enabled: true
    portEnabled: true

agents:
  customAgentConfig:
  ...
  apm_config:
    enabled: true
    apm_non_local_traffic: true
    #
    # Scenario default: Assumes that Kloudfuse stack & agent both in same VPC and in same K8S cluster
    #
    apm_dd_url: "kfuse-ingress-nginx-controller-internal.kfuse:80/ingester"
    #
    # Scenario 1: Kloudfuse stack & agent both in same VPC, but in different K8S cluster
    #
    # apm_dd_url: "http://<ingress-ip>/ingester"
    #
    # Scenario 2: Kloudfuse stack hosted in a different VPC (hosted at “customer.kloudfuse.io”)
    #
    # apm_dd_url: "https://customer.kloudfuse.io/ingester"
    yaml

  5. Verify that the agent runs in the cluster, and that data flows into Kloudfuse.