Network Checks Overview

Uptrends designed its HTTP(S) monitors to check the availability and speed of your website, but when you need to check other non-web, networked devices from outside your firewall, you need a Network Check. Uptrends will notify your team when it encounters an error with your provided URL or IP address, and depending on the error, you will receive a traceroute to assist you in fixing the problem. With Network Checks, you have two options: ping or connect.

Ping

When you select the Ping Network Check, Uptrends' checkpoints use ICMP (Internet Control Message Protocol) to send an echo request. Uptrends gathers and reports response times and issues alerts for any errors found in the reply.

Note: You must have ICMP enabled on the device to avoid needless alerts; also in the event of heavy network traffic, sometimes devices ignore ICMP requests.

Connect

When you select a Connect Network Check, Uptrends will attempt to connect to the port number you designate. You can provide any port number; for example, to make a SSH (Secure Shell) connection to a Linux box you would indicate port 22.

Features

Both the Ping and Connect provide you with many options for your monitoring.

Interval

Although the default setting for interval is five minutes, you can adjust the interval from one minute up to once an hour.

Note: Your check interval is the time between the end of one check and the start of the next. Learn more

IP version

IPv4 has long been the standard, but the new version IPv6 is quickly gaining acceptance. Most of the Uptrends checkpoints support IPv6, and we continue to add more.

Note: We recommended that you set up checks to monitor both IPv4 and IPv6. The two versions handle routing differently, so tests could fail on one version while the other succeeds.

Performance

Slow connects or pings may indicate other network or hardware issues. Using the Error conditions tab, you can set performance limits to notify you when your network experiences performance problems.

Traceroute

Uptrends performs traceroute diagnostics in several cases:

As part of a monitor check, when the monitor suspects a connectivity/networking issue. For example, when an HTTPS monitor tries to contact the web server, but no TCP connection can be created to the server’s IP address, a traceroute will be performed as a way to collect some extra diagnostics about the connectivity between Uptrends' checkpoint location and your server.
When you use the free traceroute tool to perform an explicit traceroute on one of Uptrends' checkpoint servers.

It’s important to understand what type of traffic to expect when these traceroutes are performed. Traceroute implementations behave differently on different platforms: some implementation use UDP packets, some use TCP packets, and some use ICMP (ping) echo requests. The traceroutes that Uptrends executes are always performed on Windows servers, which use ICMP packets. Therefore, using Uptrends to perform traceroutes to your networking environment will only work if your network allows ICMP packets. No TCP or UDP traffic is involved.