Probes Config

# Value can either be a static value or can be derived from target's labels. # To get value from target's labels, use target.labels.<target's label key> # as value.

# Whether to log metrics or not.

# Probe name. It should be unique across all probes.

# Interval between two probe runs in milliseconds. # Only one of "interval" and "inteval_msec" should be defined. # Default interval is 2s.

# Interval between two probe runs in string format, e.g. 10s. # Only one of "interval" and "inteval_msec" should be defined. # Default interval is 2s.

# Timeout for each probe in milliseconds # Only one of "timeout" and "timeout_msec" should be defined. # Default timeout is 1s.

# Timeout for each probe in string format, e.g. 10s. # Only one of "timeout" and "timeout_msec" should be defined. # Default timeout is 1s.

# Targets for the probe

# Latency distribution. If specified, latency is stored as a distribution.

# Latency unit. Any string that's parseable by time.ParseDuration. # Valid values: "ns", "us" (or "µs"), "ms", "s", "m", "h".

# Latency metric name. You may want to change the latency metric name, if: # you're using latency_distribution for some probes, and regular metric for # other probes, and you want to differentiate between the two. # For example: # probe { # name: "web1_latency" # latency_distribution: {...} # latency_metric_name: "latency_dist" # ... # } # probe { # name: "app1" # ... # }

# Validators for this probe. Validators are run on the data returned by the # probe. See https://cloudprober.org/docs/how-to/validators/ for more info.

# How often to export stats. Probes usually run at a higher frequency (e.g. # every second); stats from individual probes are aggregated within # cloudprober until exported. In most cases, users don't need to change the # default. # # By default this field is set in the following way: # For all probes except UDP: # stats_export_interval=max(interval, 10s) # For UDP: # stats_export_interval=max(2*max(interval, timeout), 10s)

# Additional labels to add to the probe results. Label's value can either be # static or can be derived from target's labels. # # Example: # additional_label { # key: "app" # value: "@target.label.app@" # } # (More detailed example at: examples/additional_label/cloudprober.cfg)

# (Experimental) If set, test is inversed, i.e. we count it as success if # target doesn't respond. This is useful, for example, that your firewall is # working as expected. # # This is currently implemented only by PING and TCP probes. # Note: This field is currently experimental, and may change in future.

# Alerts configuration. If specified, cloudprober will generate alerts on # probe failures. You can specify multiple alerts. # Example: # alert { # name: "alert1" # condition {...} # notify { # pagerduty { ...} # } # } # alert { # name: "alert2" # notify { ... } # }

# Which machines this probe should run on. If defined, cloudprober will run # this probe only if machine's hostname matches this value. This is useful # for large deployments, where you may want to use the same prober config # everywhere but run this probe only on a subset of machines.

# Debug options. Currently only used to enable logging metrics.

# Name of the alert. Default is to use the probe name. If you have multiple # alerts for the same probe, you must specify a name for each alert.

# Condition for the alert. Default is to alert on any failure. # Example: # # Alert if 6 out of 10 probes fail. # condition { # failures: 6 # total: 10 # }

# How to notify in case of alert.

# Dashboard URL template. # Default: http://localhost:9313/status?probe=@probe@

# Default: "Cloudprober alert @alert@ for @target@"

# Default: # Cloudprober alert "@alert@" for "@target@": # Failures: @failures@ out of @total@ probes # Failing since: @since@ # Probe: @probe@ # Dashboard: @dashboard_url@ # Playbook: @playbook_url@ # Condition ID: @condition_id@

# How often to repeat notification for the same alert. Default is 1hr. # To disable any kind of notification throttling, set this to 0.

# Email addresses to send the alert to.

# From address in the alert email. # If not set, defaults to the value of smtp_user if smtp_user is set, # otherwise defaults to cloudprober-alert@<hostname>.

# Default: Environment variable SMTP_SERVER

# Default: Environment variable SMTP_USERNAME

# Default: Environment variable SMTP_PASSWORD

# Command to run when alert is fired. In the command line following fields # are substituted: # @alert@: Alert name # @probe@: Probe name # @target@: Target name, or target and port if port is specified. # @target.label.<label>@: Label <label> value, e.g. target.label.role. # @failures@: Count of failures. # @total@: Out of. # @since@: Time since the alert condition started. # @json@: JSON representation of the alert fields. # # For example, if you want to send an email when an alert is fired, you can # use the following command: # command: "/usr/bin/mail -s 'Alert @alert@ fired for @target@' [email protected]"

# Email notification configuration.

# PagerDuty configuration.

# Slack configuration.

# PagerDuty Routing Key. # The routing key is used to determine which service the alerts are sent to # and is generated with the service. The routing key is found under the # service, when the events v2 integration is enabled, under integrations, # in the pagerduty console. # Note: set either routing_key or routing_key_env_var. routing_key # takes precedence over routing_key_env_var.

# The environment variable that is used to contain the pagerduty routing # key.

# PagerDuty API URL. # Used to overwrite the default PagerDuty API URL.

# Webhook URL # The Slack notifications use a webhook URL to send the notifications to # a Slack channel. The webhook URL can be found in the Slack console under # the "Incoming Webhooks" section. # https://api.slack.com/messaging/webhooks # Note: set either webhook_url or webhook_url_env_var. webhook_url # takes precedence over webhook_url_env_var.

# The environment variable that is used to contain the slack webhook URL.

# Domain to use when making DNS queries

# Minimum number of answers expected. Default behavior is to return success # if DNS response status is NOERROR.

# Whether to resolve the target (target is DNS server here) before making # the request. If set to false, we hand over the target directly to the DNS # client. Otherwise, we resolve the target first to an IP address. By # default we resolve first if it's a discovered resource, e.g., a k8s # endpoint.

# Command. For ONCE probes, arguments are processed for the following field # substitutions: # @probe@ Name of the probe # @target@ Hostname of the target # @address@ IP address of the target # # For example, for target ig-us-central1-a, /tools/recreate_vm -vm @target@ # will get converted to: /tools/recreate_vm -vm ig-us-central1-a

# Command environment variables. These are passed on to the external probe # process as environment variables.

# Export output as metrics, where output is the output returned by the # external probe process, over stdout for ONCE probes, and through ProbeReply # for SERVER probes. Cloudprober expects variables to be in the following # format in the output: # var1 value1 (for example: total_errors 589)

# Protoset contains descriptor source protos generated from the *.proto # files. You can use protoc to generate protoset files: # protoc --proto_path=. --descriptor_set_out=myservice.protoset \ # --include_imports my/custom/server/service.proto

# Request data (in JSON format) for the call_service_method request.

# Optional oauth config. For GOOGLE_DEFAULT_CREDENTIALS, use: # oauth_config: { bearer_token { gce_service_account: "default" } }

# If alts_config is provided, gRPC client uses ALTS for authentication and # encryption. For default alts configs, use: # alts_config: {}

# If TLSConfig is specified, it's used for authentication. # Note that only one of ALTSConfig and TLSConfig can be enabled at a time.

# if insecure_transport is set to true, TLS will not be used.

# Blob size for ECHO, READ, and WRITE methods.

# For HEALTH_CHECK, name of the service to health check.

# For HEALTH_CHECK, ignore status. By default, HEALTH_CHECK test passes # only if response-status is SERVING. Setting the following option makes # HEALTH_CHECK pass regardless of the response-status.

# Request definition for the GENERIC method.

# If connect_timeout is not specified, reuse probe timeout.

# URI scheme allows gRPC to use different resolvers # Example URI scheme: "google-c2p:///" # See https://github.com/grpc/grpc/blob/master/doc/naming.md for more details

# If provided, ALTS verifies that peer is using one of the given service # accounts.

# Handshaker service address. Default is to use the local metadata server. # For most of the ALTS use cases, default address should be okay.

# Relative URL (to append to all targets). Must begin with '/'

# Port for HTTP requests. If not specfied, port is selected in the following # order: # - If port is provided by the targets (e.g. kubernetes endpoint or # service), that port is used. # - 80 for HTTP and 443 for HTTPS.

# Whether to resolve the target before making the request. If set to false, # we hand over the target and relative_url directly to the golang's HTTP # module, Otherwise, we resolve the target first to an IP address and # make a request using that while passing target name as Host header. # By default we resolve first if it's a discovered resource, e.g., a k8s # endpoint.

# Export response (body) count as a metric

# HTTP request headers # It is recommended to use "header" instead of "headers" for new configs. # header { # key: "Authorization" # value: "Bearer {{env "AUTH_TOKEN"}}" # }

# Request body. This field works similar to the curl's data flag. If there # are multiple "body" fields, we combine their values with a '&' in between. # # Also, we try to guess the content-type header based on the data: # 1) If data appears to be a valid json, we automatically set the # content-type header to "application/json". # 2) If the final data string appears to be a valid query string, we # set content-type to "application/x-www-form-urlencoded". Content type # header can still be overridden using the header field above. # Example: # body: "grant_type=client_credentials" # body: "scope=transferMoney" # body: "clientId=aweseomeClient" # body: "clientSecret=noSecret"

# Enable HTTP keep-alive. If set to true, underlying connection is reused # for further probes. Default is to close the connection after every request.

# OAuth Config

# Disable HTTP2 # Golang HTTP client automatically enables HTTP/2 if server supports it. This # option disables that behavior to enforce HTTP/1.1 for testing purpose.

# Disable TLS certificate validation. If set to true, any certificate # presented by the server for any host name will be accepted # Deprecation: This option is now subsumed by the tls_config below. To # disable cert validation use: # tls_config { # disable_cert_validation: true # }

# TLS config

# Proxy URL, e.g. http://myproxy:3128

# User agent. Default user agent is Go's default user agent.

# Maximum idle connections to keep alive

# The maximum amount of redirects the HTTP client will follow. # To disable redirects, use max_redirects: 0.

# Interval between targets.

# Requests per probe. # Number of HTTP requests per probe. Requests are executed concurrently and # each HTTP re contributes to probe results. For example, if you run two # requests per probe, "total" counter will be incremented by 2.

# How long to wait between two requests to the same target. Only relevant # if requests_per_probe is also configured. # # This value should be less than (interval - timeout) / requests_per_probe. # This is to ensure that all requests are executed within one probe interval # and all of them get sufficient time. For example, if probe interval is 2s, # timeout is 1s, and requests_per_probe is 10, requests_interval_msec # should be less than 10ms.

# Packets per probe

# How long to wait between two packets to the same target

# Resolve targets after these many probes

# Ping payload size in bytes. It cannot be smaller than 8, number of bytes # required for the nanoseconds timestamp.

# Use datagram socket for ICMP. # This option enables unprivileged pings (that is, you don't require root # privilege to send ICMP packets). Note that most of the Linux distributions # don't allow unprivileged pings by default. To enable unprivileged pings on # some Linux distributions, you may need to run the following command: # # sudo sysctl -w net.ipv4.ping_group_range="0 <large valid group id>" # # net.ipv4.ping_group_range system setting takes two integers that specify # the group id range that is allowed to execute the unprivileged pings. Note # that the same setting (with ipv4 in the path) applies to IPv6 as well. # # Note: This option is not supported on Windows and is automatically # disabled there.

# Disable integrity checks. To detect data courruption in the network, we # craft the outgoing ICMP packet payload in a certain format and verify that # the reply payload matches the same format.

# Do not allow OS-level fragmentation, only works on Linux systems.

# Port for TCP requests. If not specfied, and port is provided by the # targets (e.g. kubernetes endpoint or service), that port is used.

# Whether to resolve the target before making the request. If set to false, # we hand over the target golang's net.Dial module, Otherwise, we resolve # the target first to an IP address and make a request using that. By # default we resolve first if it's a discovered resource, e.g., a k8s # endpoint.

# Interval between targets.

# Port to send UDP Ping to (UDP Echo). If running with the UDP server that # comes with cloudprober, it should be same as # ProberConfig.udp_echo_server_port.

# Number of sending side ports to use.

# message max to account for MTU.

# Payload size

# Changes the exported monitoring streams to be per port: # 1. Changes the streams names to total-per-port, success-per-port etc. # 2. Adds src_port and dst_port as stream labels. # Note that the field name is experimental and may change in the future.

# Whether to use all transmit ports per probe, per target. # Default is to probe each target once per probe and round-robin through the # source ports. # Setting this field to true changes the behavior to send traffic from all # ports to all targets in each probe. # For example, if num_tx_ports is set to 16, in every probe cycle, we'll send # 16 packets to every target (1 per tx port). # Note that setting this field to true will increase the probe traffic.

# maxTargets is the maximum number of targets supported by this probe type. # If there are more targets, they are pruned from the list to bring targets # list under maxTargets. A large number of targets has impact on resource # consumption.

# Port to listen.

# Number of packets sent in a single probe.

# Value can either be a static value or can be derived from target's labels. # To get value from target's labels, use target.labels.<target's label key> # as value.

# Whether to log metrics or not.

# Probe name. It should be unique across all probes.

# Interval between two probe runs in milliseconds. # Only one of "interval" and "inteval_msec" should be defined. # Default interval is 2s.

# Interval between two probe runs in string format, e.g. 10s. # Only one of "interval" and "inteval_msec" should be defined. # Default interval is 2s.

# Timeout for each probe in milliseconds # Only one of "timeout" and "timeout_msec" should be defined. # Default timeout is 1s.

# Timeout for each probe in string format, e.g. 10s. # Only one of "timeout" and "timeout_msec" should be defined. # Default timeout is 1s.

# Targets for the probe

# Latency distribution. If specified, latency is stored as a distribution.

# Latency unit. Any string that's parseable by time.ParseDuration. # Valid values: "ns", "us" (or "µs"), "ms", "s", "m", "h".

# Latency metric name. You may want to change the latency metric name, if: # you're using latency_distribution for some probes, and regular metric for # other probes, and you want to differentiate between the two. # For example: # probe { # name: "web1_latency" # latency_distribution: {...} # latency_metric_name: "latency_dist" # ... # } # probe { # name: "app1" # ... # }

# Validators for this probe. Validators are run on the data returned by the # probe. See https://cloudprober.org/docs/how-to/validators/ for more info.

# How often to export stats. Probes usually run at a higher frequency (e.g. # every second); stats from individual probes are aggregated within # cloudprober until exported. In most cases, users don't need to change the # default. # # By default this field is set in the following way: # For all probes except UDP: # stats_export_interval=max(interval, 10s) # For UDP: # stats_export_interval=max(2*max(interval, timeout), 10s)

# Additional labels to add to the probe results. Label's value can either be # static or can be derived from target's labels. # # Example: # additional_label { # key: "app" # value: "@target.label.app@" # } # (More detailed example at: examples/additional_label/cloudprober.cfg)

# (Experimental) If set, test is inversed, i.e. we count it as success if # target doesn't respond. This is useful, for example, that your firewall is # working as expected. # # This is currently implemented only by PING and TCP probes. # Note: This field is currently experimental, and may change in future.

# Alerts configuration. If specified, cloudprober will generate alerts on # probe failures. You can specify multiple alerts. # Example: # alert { # name: "alert1" # condition {...} # notify { # pagerduty { ...} # } # } # alert { # name: "alert2" # notify { ... } # }

# Which machines this probe should run on. If defined, cloudprober will run # this probe only if machine's hostname matches this value. This is useful # for large deployments, where you may want to use the same prober config # everywhere but run this probe only on a subset of machines.

# Debug options. Currently only used to enable logging metrics.

# Name of the alert. Default is to use the probe name. If you have multiple # alerts for the same probe, you must specify a name for each alert.

# Condition for the alert. Default is to alert on any failure. # Example: # # Alert if 6 out of 10 probes fail. # condition { # failures: 6 # total: 10 # }

# How to notify in case of alert.

# Dashboard URL template. # Default: http://localhost:9313/status?probe=@probe@

# Default: "Cloudprober alert @alert@ for @target@"

# Default: # Cloudprober alert "@alert@" for "@target@": # Failures: @failures@ out of @total@ probes # Failing since: @since@ # Probe: @probe@ # Dashboard: @dashboard_url@ # Playbook: @playbook_url@ # Condition ID: @condition_id@

# How often to repeat notification for the same alert. Default is 1hr. # To disable any kind of notification throttling, set this to 0.

# Email addresses to send the alert to.

# From address in the alert email. # If not set, defaults to the value of smtp_user if smtp_user is set, # otherwise defaults to cloudprober-alert@<hostname>.

# Default: Environment variable SMTP_SERVER

# Default: Environment variable SMTP_USERNAME

# Default: Environment variable SMTP_PASSWORD

# Command to run when alert is fired. In the command line following fields # are substituted: # @alert@: Alert name # @probe@: Probe name # @target@: Target name, or target and port if port is specified. # @target.label.<label>@: Label <label> value, e.g. target.label.role. # @failures@: Count of failures. # @total@: Out of. # @since@: Time since the alert condition started. # @json@: JSON representation of the alert fields. # # For example, if you want to send an email when an alert is fired, you can # use the following command: # command: "/usr/bin/mail -s 'Alert @alert@ fired for @target@' [email protected]"

# Email notification configuration.

# PagerDuty configuration.

# Slack configuration.

# PagerDuty Routing Key. # The routing key is used to determine which service the alerts are sent to # and is generated with the service. The routing key is found under the # service, when the events v2 integration is enabled, under integrations, # in the pagerduty console. # Note: set either routing_key or routing_key_env_var. routing_key # takes precedence over routing_key_env_var.

# The environment variable that is used to contain the pagerduty routing # key.

# PagerDuty API URL. # Used to overwrite the default PagerDuty API URL.

# Webhook URL # The Slack notifications use a webhook URL to send the notifications to # a Slack channel. The webhook URL can be found in the Slack console under # the "Incoming Webhooks" section. # https://api.slack.com/messaging/webhooks # Note: set either webhook_url or webhook_url_env_var. webhook_url # takes precedence over webhook_url_env_var.

# The environment variable that is used to contain the slack webhook URL.

# Domain to use when making DNS queries

# Minimum number of answers expected. Default behavior is to return success # if DNS response status is NOERROR.

# Whether to resolve the target (target is DNS server here) before making # the request. If set to false, we hand over the target directly to the DNS # client. Otherwise, we resolve the target first to an IP address. By # default we resolve first if it's a discovered resource, e.g., a k8s # endpoint.

# Command. For ONCE probes, arguments are processed for the following field # substitutions: # @probe@ Name of the probe # @target@ Hostname of the target # @address@ IP address of the target # # For example, for target ig-us-central1-a, /tools/recreate_vm -vm @target@ # will get converted to: /tools/recreate_vm -vm ig-us-central1-a

# Command environment variables. These are passed on to the external probe # process as environment variables.

# Export output as metrics, where output is the output returned by the # external probe process, over stdout for ONCE probes, and through ProbeReply # for SERVER probes. Cloudprober expects variables to be in the following # format in the output: # var1 value1 (for example: total_errors 589)

# Protoset contains descriptor source protos generated from the *.proto # files. You can use protoc to generate protoset files: # protoc --proto_path=. --descriptor_set_out=myservice.protoset \ # --include_imports my/custom/server/service.proto

# Request data (in JSON format) for the call_service_method request.

# Optional oauth config. For GOOGLE_DEFAULT_CREDENTIALS, use: # oauth_config: { bearer_token { gce_service_account: "default" } }

# If alts_config is provided, gRPC client uses ALTS for authentication and # encryption. For default alts configs, use: # alts_config: {}

# If TLSConfig is specified, it's used for authentication. # Note that only one of ALTSConfig and TLSConfig can be enabled at a time.

# if insecure_transport is set to true, TLS will not be used.

# Blob size for ECHO, READ, and WRITE methods.

# For HEALTH_CHECK, name of the service to health check.

# For HEALTH_CHECK, ignore status. By default, HEALTH_CHECK test passes # only if response-status is SERVING. Setting the following option makes # HEALTH_CHECK pass regardless of the response-status.

# Request definition for the GENERIC method.

# If connect_timeout is not specified, reuse probe timeout.

# URI scheme allows gRPC to use different resolvers # Example URI scheme: "google-c2p:///" # See https://github.com/grpc/grpc/blob/master/doc/naming.md for more details

# If provided, ALTS verifies that peer is using one of the given service # accounts.

# Handshaker service address. Default is to use the local metadata server. # For most of the ALTS use cases, default address should be okay.

# Relative URL (to append to all targets). Must begin with '/'

# Port for HTTP requests. If not specfied, port is selected in the following # order: # - If port is provided by the targets (e.g. kubernetes endpoint or # service), that port is used. # - 80 for HTTP and 443 for HTTPS.

# Whether to resolve the target before making the request. If set to false, # we hand over the target and relative_url directly to the golang's HTTP # module, Otherwise, we resolve the target first to an IP address and # make a request using that while passing target name as Host header. # By default we resolve first if it's a discovered resource, e.g., a k8s # endpoint.

# Export response (body) count as a metric

# HTTP request headers # It is recommended to use "header" instead of "headers" for new configs. # header { # key: "Authorization" # value: "Bearer {{env "AUTH_TOKEN"}}" # }

# Request body. This field works similar to the curl's data flag. If there # are multiple "body" fields, we combine their values with a '&' in between. # # Also, we try to guess the content-type header based on the data: # 1) If data appears to be a valid json, we automatically set the # content-type header to "application/json". # 2) If the final data string appears to be a valid query string, we # set content-type to "application/x-www-form-urlencoded". Content type # header can still be overridden using the header field above. # Example: # body: "grant_type=client_credentials" # body: "scope=transferMoney" # body: "clientId=aweseomeClient" # body: "clientSecret=noSecret"

# Enable HTTP keep-alive. If set to true, underlying connection is reused # for further probes. Default is to close the connection after every request.

# OAuth Config

# Disable HTTP2 # Golang HTTP client automatically enables HTTP/2 if server supports it. This # option disables that behavior to enforce HTTP/1.1 for testing purpose.

# Disable TLS certificate validation. If set to true, any certificate # presented by the server for any host name will be accepted # Deprecation: This option is now subsumed by the tls_config below. To # disable cert validation use: # tls_config { # disable_cert_validation: true # }

# TLS config

# Proxy URL, e.g. http://myproxy:3128

# User agent. Default user agent is Go's default user agent.

# Maximum idle connections to keep alive

# The maximum amount of redirects the HTTP client will follow. # To disable redirects, use max_redirects: 0.

# Interval between targets.

# Requests per probe. # Number of HTTP requests per probe. Requests are executed concurrently and # each HTTP re contributes to probe results. For example, if you run two # requests per probe, "total" counter will be incremented by 2.

# How long to wait between two requests to the same target. Only relevant # if requests_per_probe is also configured. # # This value should be less than (interval - timeout) / requests_per_probe. # This is to ensure that all requests are executed within one probe interval # and all of them get sufficient time. For example, if probe interval is 2s, # timeout is 1s, and requests_per_probe is 10, requests_interval_msec # should be less than 10ms.

# Packets per probe

# How long to wait between two packets to the same target

# Resolve targets after these many probes

# Ping payload size in bytes. It cannot be smaller than 8, number of bytes # required for the nanoseconds timestamp.

# Use datagram socket for ICMP. # This option enables unprivileged pings (that is, you don't require root # privilege to send ICMP packets). Note that most of the Linux distributions # don't allow unprivileged pings by default. To enable unprivileged pings on # some Linux distributions, you may need to run the following command: # # sudo sysctl -w net.ipv4.ping_group_range="0 <large valid group id>" # # net.ipv4.ping_group_range system setting takes two integers that specify # the group id range that is allowed to execute the unprivileged pings. Note # that the same setting (with ipv4 in the path) applies to IPv6 as well. # # Note: This option is not supported on Windows and is automatically # disabled there.

# Disable integrity checks. To detect data courruption in the network, we # craft the outgoing ICMP packet payload in a certain format and verify that # the reply payload matches the same format.

# Do not allow OS-level fragmentation, only works on Linux systems.

# Port for TCP requests. If not specfied, and port is provided by the # targets (e.g. kubernetes endpoint or service), that port is used.

# Whether to resolve the target before making the request. If set to false, # we hand over the target golang's net.Dial module, Otherwise, we resolve # the target first to an IP address and make a request using that. By # default we resolve first if it's a discovered resource, e.g., a k8s # endpoint.

# Interval between targets.

# Port to send UDP Ping to (UDP Echo). If running with the UDP server that # comes with cloudprober, it should be same as # ProberConfig.udp_echo_server_port.

# Number of sending side ports to use.

# message max to account for MTU.

# Payload size

# Changes the exported monitoring streams to be per port: # 1. Changes the streams names to total-per-port, success-per-port etc. # 2. Adds src_port and dst_port as stream labels. # Note that the field name is experimental and may change in the future.

# Whether to use all transmit ports per probe, per target. # Default is to probe each target once per probe and round-robin through the # source ports. # Setting this field to true changes the behavior to send traffic from all # ports to all targets in each probe. # For example, if num_tx_ports is set to 16, in every probe cycle, we'll send # 16 packets to every target (1 per tx port). # Note that setting this field to true will increase the probe traffic.

# maxTargets is the maximum number of targets supported by this probe type. # If there are more targets, they are pruned from the list to bring targets # list under maxTargets. A large number of targets has impact on resource # consumption.

# Port to listen.

# Number of packets sent in a single probe.