A TCP monitor will open a TCP socket on the specified port to check that a connection can be established and content can be read from the socket. A custom string can be sent with the connection prior to the read operation. This guide will walk you through creating a TCP monitor.
Creating a Monitor
- Navigate to the Monitoring subsection of the portal
- Click on the "Create Monitor" button
- Below is the "Create Monitor" page in its entirety
Name: This is the vanity name for the monitor you will see in your Monitoring overview page. Set this to whatever you like and it doesn't necessarily need to be relevant to the monitored site, though that's recommended.
Protocol: HTTP(S) or TCP. Since we're creating a TCP monitor, use TCP.
Host: The URL or IP that will be monitored.
Port: The port the monitor will attempt to create a TCP connection on.
IP version: Whether the monitor will try to resolve the URL using IPv4 or IPv6.
Locations: Which locations you wish to have the URL/IP monitored from. Each location chosen will send its own request to your chosen URL/IP and will have its own monitoring data available. You can find a full list of locations here.
Frequency: This option is currently not selectable. In the future, this option will determine how often the monitor will send out requests. The default and only option is 5 minutes.
Timeout: How long the monitor will attempt to make a connection with the monitored URL/IP. If the timeout is reached, the site is considered down for the location that reached the timeout. There's a hard cap of 20 seconds for timeouts, the default timeout is 10 seconds.
Socket message: A data string to send when opening the socket.
Now that you understand each option you can go ahead and create your monitor.
Viewing Monitor Results
Here you can see connection data for your monitor including response times, and a breakdown of what constitutes that response time. If you want more information about Monitoring metrics on this page, you can refer to our article.
Your monitor has now been created and the chosen TCP port on your resource is being monitored. We will create one alert by default, but feel free to add more alerts if you have specific monitoring requirements. You can add alerts from the alerting tab (be sure to read our Alerting Best Practices):