Agent v7.59+가 필요합니다.

1. 다음 내용을 추가하여 /etc/datadog-agent/system-probe.yaml에서 system-probe 트레이스라우트 모듈을 활성화합니다.

   traceroute:
     enabled: true
   

2. network_path를 활성화하여 이 Agent에서 새로운 목적지를 모니터링하려면 /etc/datadog-agent/conf.d/network_path.d/conf.yaml 파일을 생성하거나 편집하세요.

   init_config:
     min_collection_interval: 60 # in seconds, default 60 seconds
   instances:
     # configure the endpoints you want to monitor, one check instance per endpoint
     # warning: Do not set the port when using UDP. Setting the port when using UDP can cause traceroute calls to fail and falsely report an unreachable destination.
   
     - hostname: api.datadoghq.eu # endpoint hostname or IP
       protocol: TCP
       port: 443
       tags:
         - "tag_key:tag_value"
         - "tag_key2:tag_value2"
       min_collection_interval: 120 # set min_collection_interval at the instance level
     ## optional configs:
     # max_ttl: 30 # max traceroute TTL, default is 30
     # timeout: 1000 # timeout in milliseconds per hop, default is 1s
     # tcp_method: syn # TCP probing method, default is syn, options: syn, sack, prefer_sack
     # traceroute_queries: 3 # number of traceroutes to send per check run, default is 3
     # e2e_queries: 50 # number of end-to-end probes to send per check run, default is 50
   
     # more endpoints
     - hostname: 1.1.1.1 # endpoint hostname or IP
       protocol: UDP
       tags:
         - "tag_key:tag_value"
         - "tag_key2:tag_value2"
   

3. 구성을 변경한 후 네트워크 경로가 확인되도록 Agent를 재시작합니다.

Agent v7.75+가 필요합니다.

1. 다음 내용을 추가하여 /opt/datadog-agent/etc/system-probe.yaml에서 system-probe 트레이스라우트 모듈을 활성화합니다.

   traceroute:
     enabled: true
   

2. network_path를 활성화하여 이 Agent에서 새로운 목적지를 모니터링하려면 /opt/datadog-agent/etc/conf.d/network_path.d/conf.yaml 파일을 생성하거나 편집하세요.

   init_config:
     min_collection_interval: 60 # in seconds, default 60 seconds
   instances:
     # configure the endpoints you want to monitor, one check instance per endpoint
     # warning: Do not set the port when using UDP. Setting the port when using UDP can cause traceroute calls to fail and falsely report an unreachable destination.
   
     - hostname: api.datadoghq.eu # endpoint hostname or IP
       protocol: TCP
       port: 443
       tags:
         - "tag_key:tag_value"
         - "tag_key2:tag_value2"
       min_collection_interval: 120 # set min_collection_interval at the instance level
     ## optional configs:
     # max_ttl: 30 # max traceroute TTL, default is 30
     # timeout: 1000 # timeout in milliseconds per hop, default is 1s
     # tcp_method: syn # TCP probing method, default is syn, options: syn, sack, prefer_sack
     # traceroute_queries: 3 # number of traceroutes to send per check run, default is 3
     # e2e_queries: 50 # number of end-to-end probes to send per check run, default is 50
   
     # more endpoints
     - hostname: 1.1.1.1 # endpoint hostname or IP
       protocol: UDP
       tags:
         - "tag_key:tag_value"
         - "tag_key2:tag_value2"
   

3. 구성을 변경한 후 네트워크 경로가 확인되도록 Agent를 재시작합니다.

Agent v7.72+가 필요합니다.

1. 다음 내용을 추가하여 %ProgramData%\Datadog\system-probe.yaml에서 system-probe 트레이스라우트 모듈을 활성화합니다.

   traceroute:
     enabled: true
   

2. network_path를 활성화하여 이 Agent에서 새로운 목적지를 모니터링하려면 %ProgramData%\Datadog\conf.d\network_path.d\conf.yaml 파일을 생성하거나 편집하세요.

   init_config:
     min_collection_interval: 60 # in seconds, default 60 seconds
   instances:
     # configure the endpoints you want to monitor, one check instance per endpoint
     # warning: Do not set the port when using UDP. Setting the port when using UDP can cause traceroute calls to fail and falsely report an unreachable destination.
   
     - hostname: api.datadoghq.eu # endpoint hostname or IP
       protocol: TCP
       port: 443
       tags:
         - "tag_key:tag_value"
         - "tag_key2:tag_value2"
       min_collection_interval: 120 # set min_collection_interval at the instance level
     ## optional configs:
     # max_ttl: 30 # max traceroute TTL, default is 30
     # timeout: 1000 # timeout in milliseconds per hop, default is 1s
     # tcp_method: syn # TCP probing method, default is syn, options: syn, sack, prefer_sack, syn_socket (Windows only)
     # traceroute_queries: 3 # number of traceroutes to send per check run, default is 3
     # e2e_queries: 50 # number of end-to-end probes to send per check run, default is 50
   
     # more endpoints
     - hostname: 1.1.1.1 # endpoint hostname or IP
       protocol: TCP
       tags:
         - "tag_key:tag_value"
         - "tag_key2:tag_value2"
   

3. 구성을 변경한 후 네트워크 경로가 확인되도록 Agent를 재시작합니다.

Agent v7.59+가 필요합니다.

Helm을 사용하여 Kubernetes와 함께 Network Path를 활성화하려면 values.yaml 파일에 다음 내용을 추가하세요.

datadog:
  traceroute:
    enabled: true
  confd:
    network_path.yaml: |-
      init_config:
        min_collection_interval: 60 # in seconds, default 60 seconds
      instances:
        # configure the endpoints you want to monitor, one check instance per endpoint
        # warning: Do not set the port when using UDP. Setting the port when using UDP can cause traceroute calls to fail and falsely report an unreachable destination.

        - hostname: api.datadoghq.eu # endpoint hostname or IP
          protocol: TCP
          port: 443
          tags:
            - "tag_key:tag_value"
            - "tag_key2:tag_value2"
          min_collection_interval: 120 # set min_collection_interval at the instance level
        ## optional configs:
        # max_ttl: 30 # max traceroute TTL, default is 30
        # timeout: 1000 # timeout in milliseconds per hop, default is 1s
        # tcp_method: syn # TCP probing method, default is syn, options: syn, sack, prefer_sack
        # traceroute_queries: 3 # number of traceroutes to send per check run, default is 3
        # e2e_queries: 50 # number of end-to-end probes to send per check run, default is 50

        # more endpoints
        - hostname: 1.1.1.1 # endpoint hostname or IP
          protocol: UDP
          tags:
            - "tag_key:tag_value"
            - "tag_key2:tag_value2"

Datadog Autodiscovery allows you to enable Network Path on a per-service basis through Kubernetes annotations.

1. Enable the traceroute module in the Datadog values.yaml file, which the Network Path integration depends on.

   datadog:
     traceroute:
       enabled: true
   

2. After the module is enabled, Datadog automatically detects Network Path annotations added to your Kubernetes pod. For more information, see Kubernetes and Integrations.

   apiVersion: v1
   kind: Pod
   # (...)
   metadata:
     name: '<POD_NAME>'
     annotations:
       ad.datadoghq.com/<CONTAINER_NAME>.checks: |
         {
           "network_path": {
             "init_config": {
               "min_collection_interval": 300
             },
             "instances": [
                   {
                     "protocol": "TCP",
                     "port": 443,
                     "source_service": "<CONTAINER_NAME>",
                     "tags": [
                       "tag_key:tag_value",
                       "tag_key2:tag_value2"
                     ],
                     "hostname": "api.datadoghq.eu"
                   },
                   {
                     "protocol": "UDP",
                     "source_service": "<CONTAINER_NAME>",
                     "tags": [
                       "tag_key:tag_value",
                       "tag_key2:tag_value2"
                     ],
                     "hostname": "1.1.1.1"
                   },
             ]
           }
         }
       # (...)
   spec:
     containers:
       - name: '<CONTAINER_NAME>'
   # (...)
   

   If you define pods indirectly (with deployments, ReplicaSets, or ReplicationControllers), add pod annotations under spec.template.metadata.

Agent v7.73+가 필요합니다.

1. 다음 내용을 추가하여 /etc/datadog-agent/system-probe.yaml에서 system-probe 트레이스라우트 모듈을 활성화합니다.

   traceroute:
     enabled: true
   

2. network_path를 활성화하여 CNM 연결을 모니터링하려면 /etc/datadog-agent/datadog.yaml 파일을 생성하거나 편집하세요.

   network_path:
     connections_monitoring:
       enabled: true
     # collector:
       # workers: <NUMBER OF WORKERS> # default 4
   

   For full configuration details, reference the example config, or use the following:

   network_path:
     connections_monitoring:
       ## @param enabled - bool - required - default:false
       ## Enable network path collection
       #
       enabled: true
     collector:
       ## @param workers - int - optional - default:4
       ## Number of workers that can collect paths in parallel
       ## Recommendation: leave at default
       #
       # workers: <NUMBER OF WORKERS> # default 4
   
       #@env DD_NETWORK_PATH_COLLECTOR_PATHTEST_INTERVAL - integer - optional - default: 10m
       # The `pathtest_interval` refers to the traceroute run interval for monitored connections.
       # pathtest_interval: 10m
   
       # @param pathtest_ttl - integer - optional - default: 35m
       # @env DD_NETWORK_PATH_COLLECTOR_PATHTEST_TTL - integer - optional - default: 35m
       # The `pathtest_ttl` refers to the duration (time-to-live) a connection will be monitored when it's not seen anymore.
       # The TTL is reset each time the connection is seen again.
       # pathtest_ttl: 35m
   
       ## @param filters - list - optional
       ## Include or exclude specific domains or IP ranges from dynamic monitoring.
       ## Filters are applied sequentially, with later filters taking precedence.
       ## See the "Filter syntax" section for details and examples: https://docs.datadoghq.com/network_monitoring/network_path/setup/#filter-syntax
       #
       # filters:
       #   - match_domain: '*.example.com'
       #     type: exclude
       #   - match_ip: 10.0.0.0/8
       #     type: exclude
       #   - match_domain: 'api.datadoghq.com'
       #     type: include
   

3. 구성을 변경한 후 네트워크 경로가 확인되도록 Agent를 재시작합니다.

Agent v7.73+가 필요합니다.

1. 다음 내용을 추가하여 %ProgramData%\Datadog\system-probe.yaml에서 system-probe 트레이스라우트 모듈을 활성화합니다.

   traceroute:
     enabled: true
   

2. network_path를 활성화하여 CNM 연결을 모니터링하려면 %ProgramData%\Datadog\datadog.yaml 파일을 생성하거나 편집하세요.

   최종 사용자 장치에서 Network Path를 활성화하는 경우 이 단계를 건너뛰세요.

   network_path:
     connections_monitoring:
       enabled: true
     # collector:
       # workers: <NUMBER OF WORKERS> # default 4
   

   전체 구성 세부 정보는 예제 구성을 참조하거나 다음을 사용하세요.

   network_path:
     connections_monitoring:
       ## @param enabled - bool - required - default:false
       ## Enable network path collection
       #
       enabled: true
     collector:
       ## @param workers - int - optional - default:4
       ## Number of workers that can collect paths in parallel
       ## Recommendation: leave at default
       #
       # workers: <NUMBER OF WORKERS> # default 4
   
       #@env DD_NETWORK_PATH_COLLECTOR_PATHTEST_INTERVAL - integer - optional - default: 10m
       # The `pathtest_interval` refers to the traceroute run interval for monitored connections.
       # pathtest_interval: 10m
   
       # @param pathtest_ttl - integer - optional - default: 35m
       # @env DD_NETWORK_PATH_COLLECTOR_PATHTEST_TTL - integer - optional - default: 35m
       # The `pathtest_ttl` refers to the duration (time-to-live) a connection will be monitored when it's not seen anymore.
       # The TTL is reset each time the connection is seen again.
       # pathtest_ttl: 35m
   
       ## @param filters - list - optional
       ## Include or exclude specific domains or IP ranges from dynamic monitoring.
       ## Filters are applied sequentially, with later filters taking precedence.
       ## See the "Filter syntax" section for details and examples: https://docs.datadoghq.com/network_monitoring/network_path/setup/#filter-syntax
       #
       # filters:
       #   - match_domain: '*.example.com'
       #     type: exclude
       #   - match_ip: 10.0.0.0/8
       #     type: exclude
       #   - match_domain: 'api.datadoghq.com'
       #     type: include
   

3. 구성을 변경한 후 네트워크 경로가 확인되도록 Agent를 재시작합니다.

Agent v7.73+가 필요합니다.

Helm을 사용하여 Kubernetes와 함께 Network Path를 활성화하려면 values.yaml 파일에 다음 내용을 추가하세요. 참고: Helm chart v3.124.0+가 필요합니다. 자세한 정보는 Datadog Helm Chart 문서와 Kubernetes 및 Integrations에 대한 문서를 참조하세요.

datadog:
  networkPath:
    connectionsMonitoring:
      enabled: true
  ## Set to true to enable the Traceroute Module of the System Probe
  traceroute:
    enabled: true

  ## @param collector - custom object - optional
  ## Configuration related to Network Path Collector.
  #
  collector:
    ## @param workers - integer - optional - default: 4
    ## @env DD_WORKERS - integer - optional - default: 4
    ## The `workers` refers to the number of concurrent workers available for network path execution.
    #
    # workers: 4
    
    ## @param pathtest_interval - integer - optional - default: 35m
    ## @env DD_NETWORK_PATH_COLLECTOR_PATHTEST_INTERVAL - integer - optional - default: 30m
    ## The `pathtest_interval` refers to the traceroute run interval for monitored connections.
    #
    # pathtest_interval: 30m

    ## @param pathtest_ttl - integer - optional - default: 35m
    ## @env DD_NETWORK_PATH_COLLECTOR_PATHTEST_TTL - integer - optional - default: 35m
    ## The `pathtest_ttl` refers to the duration (time-to-live) a connection will be monitored when it's not seen anymore.
    ## The TTL is reset each time the connection is seen again.
    #
    # pathtest_ttl: 35m

    ## @param filters - list - optional
    ## Include or exclude specific domains or IP ranges from dynamic monitoring.
    ## Filters are applied sequentially, with later filters taking precedence.
    ## See the "Filter syntax" section for details and examples: https://docs.datadoghq.com/network_monitoring/network_path/setup/#filter-syntax
    #
    # filters:
    #   - match_domain: '*.example.com'
    #     type: exclude
    #   - match_ip: 10.0.0.0/8
    #     type: exclude
    #   - match_domain: 'api.datadoghq.com'
    #     type: include

1. 다음 내용을 추가하여 /etc/datadog-agent/system-probe.yaml에서 system-probe 트레이스라우트 모듈을 활성화합니다.

   traceroute:
     enabled: true
   

2. /etc/datadog-agent/datadog.yaml에서 NetFlow용 동적 테스트를 활성화합니다.

   network_path:
     netflow_monitoring:
       enabled: true
     collector:
       monitor_ip_without_domain: true
   

   monitor_ip_without_domain: true는 필수 사항입니다. NetFlow용 동적 테스트가 관찰된 대상 IP 주소를 대상으로 하고 Network Path 컬렉터가 기본적으로 IP 전용 대상을 건너뛰기 때문입니다.

3. 이 구성 변경을 수행한 후 Agent를 재시작합니다.

1. 다음 내용을 추가하여 %ProgramData%\Datadog\system-probe.yaml에서 system-probe 트레이스라우트 모듈을 활성화합니다.

   traceroute:
     enabled: true
   

2. %ProgramData%\Datadog\datadog.yaml에서 NetFlow용 동적 테스트를 활성화합니다.

   network_path:
     netflow_monitoring:
       enabled: true
     collector:
       monitor_ip_without_domain: true
   

   monitor_ip_without_domain: true는 필수 사항입니다. NetFlow용 동적 테스트가 관찰된 대상 IP 주소를 대상으로 하고 Network Path 컬렉터가 기본적으로 IP 전용 대상을 건너뛰기 때문입니다.

3. 이 구성 변경을 수행한 후 Agent를 재시작합니다.