A TCP endpoint is a combination of an IP address and a port number that identifies a specific process or service running on a computer or other network device. It is used to establish and manage an end-to-end connection between two applications, typically over the Internet. The TCP protocol provides a reliable, ordered delivery of data between the two endpoints.
The prerequisites for monitoring TCP endpoint is to have Netdata installed on your system.
Netdata auto discovers hundreds of services, and for those it doesn’t turning on manual discovery is a one line configuration. For more information on configuring Netdata for TCP endpoint monitoring please read the collector documentation.
You should now see the TCP endpoint section on the Overview tab in Netdata Cloud already populated with charts about all the metrics you care about.
Netdata has a public demo space (no login required) where you can explore different monitoring use-cases and get a feel for Netdata.
The status metric is used to measure the success rate of TCP connections. It is a boolean metric that indicates whether a connection was successful (value 1) or failed (value 0). This metric is important to monitor because it allows you to identify any issues with the network or application that may be preventing connections from being established. Poor status can lead to decreased performance, increased latency, and even outages.
The state_duration metric is used to measure the amount of time a TCP connection is kept alive. This metric is important to monitor because it allows you to identify any issues with the network or application that may be preventing connections from being closed or disconnected. Poor state duration can lead to increased latency, decreased performance, and even outages.
The latency metric is used to measure the amount of time it takes for a TCP connection to be established. This metric is important to monitor because it allows you to identify any issues with the network or application that may be causing delays in establishing connections. Poor latency can lead to decreased performance, increased latency, and even outages.