You can find the User Manual for Network Logger Pro under the application’s “Help” menu in the menu bar at the top of the screen.
For technical support, email:
Frequently Asked Questions (FAQ):
Q #1: “What are the system requirements for Network Logger Pro?”
A: Currently Network Logger Pro requires OSX 10.7 “Lion” as a minimum and has been verified to work with macOS 10.12 “Sierra.”
Q #2: “We have recently moved to a new internet provider and are finding recurring, but inconsistent internet service periods “randomly” (it seems) – we lose our connection for 1 to 4 minutes and then it magically restores itself. We’ve had the ISP replace the router/modem, check the line on their end, etc. I’m looking for an Internet Monitoring tool that I can run for a day or two that will continuously check the connection (to the primary DNS server?) and log “outages” so that I can “prove” to the ISP that it’s occurring, and when /how long outages occur. … Will your tool meet our needs, or do you know of a tool that will fulfill these needs?”
A: Yes, logging outages over arbitrary periods is one of Network Logger Pro’s features.
Q #3: “Does Network Logger Pro use a lot of CPU time?”
A: Since Network Logger Pro is designed to run for weeks or months at a time, a lot of care has gone into designing it to use very little CPU time. That way your machine stays cool and has almost all of it’s power available for other tasks. Typical usage with the default settings is about 5% of one core. It will use less on newer machines.
Q #4: “Since using your Network Logging Pro I am getting reports from the 3rd party monitoring company that your application is trying to contact a number of web sites for an unknown reason. Can you explain why this is happening?”
A: That traffic is generated by a feature called Automatic Connection Testing, which does connection outage logging. You can see that activity in the ACT Activity window, under the Window menu. It’s not pulling data down, it’s seeing if it can reach the servers via ping and http header requests. If you want to turn it off you can do so in the Preferences by setting the Automatic Connection Testing Interval to Off. In that case if you still want outage logging you’ll have to set up your own URL Monitor from the File menu. More details on doing this can be found in the User Manual under the Help menu in Network Logger.
Q #5: “Why doesn’t my URL work in the Server Monitor?”
A: Make sure your URLs is not malformed, meaning they contain spaces or other characters that don’t conform to the URL standard. If your URL works in a browser, simply copy it from the browser’s URL field and paste it into Network Logger Pro.
Q #6: “My internet drops out quite often but usually only for a few seconds, would your logger note these short periods?”
A: Yes, but it would be unusual to have actual disconnects that behave like that. Usually when you see that kind of behavior, either network bandwidth is fully utilized momentarily or a server is very busy, neither is really an outage but the former can cause some services to disconnect, like VPN, FTP, or IRC, because too many packets are dropped. It can happen however, if you have a loose physical connection or broken wire that gets wiggled or blown by the wind or periodic water that causes a short or noise on the line.
Q #7: “I’m having ISP network dropouts so I’ve been monitoring my system with your software. Can you please help me understand why or how the software is not indicating dropouts in the history graph? For example, when I have a dropout noted on my network connection log, there is not a corresponding drop in the peaks on the history graph for that timeframe. I’ve been at my computer during some of these dropouts and can confirm that my network was indeed down at the time noted in the log.”
A: During an internet connection outage, there is still a small amount of traffic on the local LAN in your house or office, even if it’s just the handshaking between things like your Mac and a router or printer. I notice that all the graphs in your screenshot are measuring on the kilobits per second scale and on the low end of that, all below 100kbps, which is the amount of bandwidth this background handshaking generates. On most internet connections, user generated traffic is in the megabits per second scale, on that scale you would see the gaps you were expecting if there was nearby megabit level internet traffic on either side of your outages on the graph. Even in that case, you would see this handshaking traffic as a fuzzy floor running through the red outage sections, it would just be very low on the graph in comparison. Other traffic on your LAN, like copying a file between two Macs, can produce megabit scale traffic on the graph even during an internet connection outage.