Monitor TCP connectivity and response time for any host and port.
The TCP check is included in the Datadog Agent package, so you don’t need to install anything else on any host from which you will probe TCP ports. Though many metrics-oriented checks are best run on the same host(s) as the monitored service, you’ll probably want to run this check from hosts that do not run the monitored TCP services, i.e. to test remote connectivity.
To configure this check for an Agent running on a host:
init_config: instances: - name: SSH check host: jumphost.example.com # or an IPv4/IPv6 address port: 22 collect_response_time: true # to collect network.tcp.response_time. Default is false.
name(Required) - Name of the service. This will be included as a tag:
instance:<name>. Note: This tag will have any spaces and dashes converted to underscores.
host(Required) - Host to be checked. This will be included as a tag:
port(Required) - Port to be checked. This will be included as a tag:
timeout(Optional) - Timeout for the check. Defaults to 10 seconds.
collect_response_time(Optional) - Defaults to false. If this is not set to true, no response time metric will be collected. If it is set to true, the metric returned is
tags(Optional) - Tags to be assigned to the metric.
Restart the Agent to start sending TCP service checks and response times to Datadog.
For containerized environments, see the Autodiscovery Integration Templates for guidance on applying the parameters below.
|blank or |
Run the Agent’s
status subcommand and look for
tcp_check under the Checks section.
|The response time of a given host and TCP port, tagged with url, e.g. 'url:192.168.1.100:22'.|
Shown as second
|Value of 1 if the agent can successfully establish a connection to the URL, 0 otherwise|
The TCP check does not include any events.
Returns CRITICAL if the Agent cannot establish an TCP connection to the URL. Returns OK if the connection is successful.
Statuses: ok, critical
Need help? Contact Datadog support.