![the net uptime monitor the net uptime monitor](https://www.codester.com/static/uploads/items/000/004/4744/preview/001.jpg)
![the net uptime monitor the net uptime monitor](https://internetdevels.com/sites/default/files/public/blog_preview/top_7_free_uptime_monitoring_services_8.png)
Each log file is named with the date and time NUM was started so that they will appear in your directory in chronological order. You can choose a different folder in the Settings.Īlso in the Settings, there are two options for the log file:Ī new file is created each time NUM starts. The log files are saved in a folder of your choice the default is your Documents folder. The example shows date and time in US English format your log will use the format for your region. A summary shows the total monitoring time, failure count, total down time, percentage of down time, and the minimum, maximum, and average failure lengths. The log records the start and end time of the monitoring and each failure start time and length. It will open in Notepad or your default text editor, so you can easily edit or print the log.
THE NET UPTIME MONITOR UPDATE
NUM will continue to update the log even while you are viewing it.īecause the log is a plain text file, you can open it outside of the NUM program. The log is displayed in a separate window. You can view the current log at any time by clicking the “View Log” button. NUM keeps a log of results in a text file. In the Settings, you can choose to have a “failure alert” sound play, and/or have the NUM window “pop up”, if a connection failure longer than your minimum setting occurs. The NUM icon is shown in the notification – you can hover over the icon to see the current time since the last failure (“Up Time”) or click the icon to restore the display. NUM disappears into your system tray in the “notifications area”. The current settings for the test interval and the minimum failure length to be logged are shown at the bottom of the display.Ĭlick the minimize button on the NUM window to hide the display. The display also shows the monitored time (how long the monitor has been running), the time since the last logged failure (up time), the start time and length of the last logged failure, and the total count of logged failures since NUM was started. When the length of the failure exceeds your setting for “Log Failure If Longer Than”, NUM plays an alert sound and writes the failure information into its log. If your connection fails, the current fail length is displayed in red. When the response time exceeds the time set for “Wait for Ping Response”, the indicator turns red to show no response from that server. The response time of the last ping is shown. The indicator “light” flashes yellow when the ping is sent and shows green for a successful response. The display shows the names and IP addresses of each server. You can set how long a failure must be before NUM alerts you to it and records the failure in its failure log.Ĭonnection is down, one previous failure… A very short failure of a second or so is not likely to affect your use of the net and isn’t of any real concern. NUM can detect failures as short as a couple of seconds in length, but you can decide how long a failure must be before it really counts. Only when all three servers fail to respond does NUM determine that your connection is down.īy using three servers, NUM ensures that the problem isn’t just with the server or with some connection on the way to that server, or that the server isn’t momentarily slow or congested. If any of the servers respond, then your connection must be working. If the server doesn’t respond, NUM immediately tries the next server, then the next. NUM pings one server at a time if the server responds, NUM waits the test interval, then pings the next server. By default, NUM waits 200 milliseconds (2/10 of a second) for the server to respond – at least 3 times as long as a typical broadband internet connection should take. (See “What’s a Ping?” below for an explanation.) Each server is pinged in turn at an interval that you can set – normally five seconds. Net Uptime Monitor (NUM) uses the “Ping” command to test the response from three public servers operated by Google, Level 3, and OpenDNS. This failure log will help your provider troubleshoot the problem – after it helps you convince them it’s not your imagination! Net Uptime Monitor is designed to be as simple as possible and accomplish this one purpose accurately and thoroughly with the least effort from you. The Net Uptime Monitor alerts you to failures in your internet connection and documents the exact time and length of those failures. But all too often the response is “Well, it’s working fine now!”
![the net uptime monitor the net uptime monitor](https://elmah.io/images/frontpage/error-logging-o.png)
Is your internet connection unreliable? You’ve probably called your internet provider’s support line and maybe they were able to help you, maybe they even sent out a tech to look at it.