- What it measures
- The share of monitored devices — switches, access points, modules and circuits — that answered the last polling cycle. Every site is polled every 60 seconds.
- Amber at
- Below 99.5% — one or more devices missed two consecutive polls.
- Red at
- Below 97% — a site or a group of devices has dropped off the network.
- NOC response
- The NOC runs a ping sweep and checks the last circuit telemetry, then escalates to the on-call engineer inside the 15-minute SLA.
The board our engineers watch — every gauge and every line explained.
This is the live view the PortGuard NOC works from. On-site modules and your existing equipment stream telemetry every 60 seconds; gauges sweep with the fleet's current state, and the feed below them records every event the system sees. Clients get the same board scoped to their own sites inside the portal.
60 seconds
24 / 7 / 365
15 minutes
Exportable
Six numbers that describe the whole network
Each card shows the live gauge plus exactly what it measures, where amber and red thresholds sit, and what the NOC does the moment a threshold is crossed. Thresholds are tuned per site from your own baseline — these are the fleet defaults.
- What it measures
- CPU, memory and thermal headroom across PortGuard modules and managed switches, weighted across the whole fleet.
- Amber at
- Any device above 70% load sustained for 10 minutes.
- Red at
- Any device above 90% load, or reporting thermal warnings.
- NOC response
- Engineers identify the top process or interface, shed load or schedule a controlled reboot inside a maintenance window.
- What it measures
- How recently each wireless access point last checked in. A missing heartbeat is the earliest sign of a power, cabling or controller fault.
- Amber at
- Any AP silent for more than 5 minutes.
- Red at
- Any AP silent for more than 15 minutes — treated as offline.
- NOC response
- The NOC cycles the PoE port remotely and re-associates the AP; if it stays down, a field engineer is dispatched.
- What it measures
- Traffic on each site's internet uplinks as a percentage of circuit capacity, sampled continuously from the module and switch counters.
- Amber at
- Above 70% of capacity for 15 minutes.
- Red at
- Above 90% of capacity — users will feel saturation.
- NOC response
- Flow analysis finds the top talkers, QoS is reviewed, and a carrier bandwidth ticket is opened if the trend holds.
- What it measures
- Round-trip time from client networks to their core and to monitored destinations, taken as the median across probes each minute.
- Amber at
- Above 50 ms sustained.
- Red at
- Above 120 ms, or rising packet loss on the same path.
- NOC response
- A path trace isolates the hop — carrier, core or last-mile — and traffic is failed over to the healthy circuit where one exists.
- What it measures
- Power-over-Ethernet draw on managed switches against their total budget, before phones, cameras and access points start dropping.
- Amber at
- Any switch above 80% of its PoE budget.
- Red at
- Above 95% — the next powered device may fail to boot.
- NOC response
- A per-port audit rebalances loads across switches, and a power upgrade is scoped if growth keeps the switch in the red zone.
Every event, in order, as it happens
The feed is the NOC's running log: every poll result, threshold crossing, failover and recovery lands here with a timestamp, the site it belongs to, and a severity. Critical rows page an engineer immediately; warnings accumulate into tickets.
Recovery or healthy confirmation — logged for the record, no action needed.
Routine system activity: polls, backups, staged updates, maintenance windows.
A threshold is crossed. The NOC investigates and opens a ticket before users notice.
Service is impacted or lost. An engineer is paged immediately under the 15-minute SLA.
What each color means, and who moves
Everything inside its baseline. The board keeps polling, backups keep running, and the monthly report accumulates quietly in the background.
A threshold is crossed but service is still up. The NOC investigates the cause, opens a ticket, and fixes it proactively — most ambers never become tickets you see.
Service is degraded or down. An engineer is paged within the 15-minute SLA, works the documented runbook, and a root-cause write-up follows the incident.
Thresholds are never vendor defaults: before alerting goes live we capture two weeks of your network's normal behavior and set amber and red lines around it. That is why the NOC pages you about real problems, not noise.
Want this board watching your network?
See how the operations layer is instrumented, monitored and staffed — or scope a deployment with the guided inquiry.