Suppose that workers at your remote offices are experiencing slow and unresponsive network applications. When narrowing the scope of possible causes, you really have only a few options. You can run ping tests all day long to find the cause of the high latency. But how can you test bandwidth availability?
You can send a few files to and from the remote location, but running those tests for a longer period of time will just make work even harder for employees at the remote site. After a few tests, you’re basically left with no choice but to believe that your Internet service provider (ISP) is giving you the level of service for which you’re paying.
In general, having a service level agreement (SLA) with your ISP helps to guarantee better service. But sooner or later you’ll need to know how much bandwidth you’re really getting over those (possibly oversubscribed) ISP lines. In the following example, the NIL Monitor graph shows that providing SLA values is not difficult over night hours and weekends. But much-needed daytime bandwidth evidently drops off.
By using NIL Monitor service management, you can measure maximum throughput without doing endless testing that obstructs your branch’s network connection.
Leave us a comment sharing how you make sure that your ISP is giving you what you pay for.