Docs
Discovery AgentBackendsPktvisorHandlers

Netprobe

Handler type: netprobe

Example of policy with input netprobe and handler NETPROBE

handlers:
  modules:
    default_netprobe:
      type: netprobe
      metric_groups:
        enable:
          - counters
          - quantiles
          - histograms
input:
  input_type: netprobe
  tap: default_netprobe
  config:
    targets:
      primary_site:
        target: www.example.com
      secondary_site:
        target: www.example.net
kind: collection

Metrics Group

Metric GroupDefault
quantilesdisabled
countersenabled
histogramsenabled
http_response_phasesdisabled

Filters

  • No filters available.

Configurations

The netprobe handler accepts recorded_stream, xact_ttl_secs and xact_ttl_ms. recorded_stream is presence-based, so setting it to false still enables it; omit the key to disable.

What is probed, including the required targets map, is configured on the netprobe input instead. See Netprobe input for the test types, their settings and the HTTP response checks.

Netprobe settings describe the probe rather than the host the agent runs on, so they are often worth setting on the policy's input rather than on the tap. A policy input may override any of the tap's netprobe settings; see Input in a policy.

handlers:
  modules:
    default_netprobe:
      type: netprobe
      metric_groups:
        enable:
          - counters
          - quantiles
          - histograms
input:
  input_type: netprobe
  tap: default_netprobe
  config:
    targets:
      primary_site:
        target: www.example.com
      secondary_site:
        target: www.example.net
    test_type: ping
    interval_msec: 2500
    timeout_msec: 2000
    packets_per_test: 5
    packets_interval_msec: 20
    packet_payload_size: 56
kind: collection

Network

Previous Page

Packet capture

Next Page

On this page

Example of policy with input netprobe and handler NETPROBEMetrics GroupFiltersConfigurations