...
| Term | Description |
|---|---|
| Member Organization | Name of organization |
| Device A / Z | Hostname of the WiscNet devices on either side of your uplink |
| Interface A / Z | Router interface names |
| Bandwidth | Capacity of link in mbps |
| Site Code | Code used to help correlate graphs to Member Organization |
| Transport Provider | Who you may be using as a transport provider |
| Transport Provider ID A / Z | Circuit ID from the transport provider |
| WiscNet Circuit ID | Internal WiscNet identifier for your circuit |
Circuit Graphs
| Term | Description | Example Graph |
|---|
| bps |
Bits per second.
|
|
|
| pps | Packets per Second |
 | ||
| Errors | Number of ethernet or CRC errors on the link. Ideally this should be zero and the graph should be pretty boring. If you see errors, contact support to troubleshoot. |
|
| Discards |
| Number of discards on an interface. Discards typically occur when a link is saturated |
|
Device Graphs
These are sensors and indicators on your WiscNet Managed Device (CPE). These graphs will not be visible if you do not have a device.
| Term | Description | Example Graph |
|---|
| Ping Response Time |
| Time in milliseconds it took our monitoring server to ping WiscNet router on premise. Ping is currently sourcing from Eau Claire, WI. |
|
| CPU |
| Processor utilization of device |
| ||
| Optical Monitoring (DOM) | Shows light levels received on fiber optic connections |
|
| Temperature | Internal temperature of device. Some models will have multiple sensors. Y axis changes dynamically. |
|
| Memory |
| Memory utilization of WiscNet router. Some devices may display multiple readings depending on memory pool |
| |
| Uptime |
| Length of time in days since WiscNet router has last rebooted. Always up and to the right. Read the legend to get the time in days. |
| ||
| Status | Status of device over time, calculated as percent. |
|
