Totality watches every network you manage, learns what normal looks like for each one, and tells you what is wrong and why — before the phone rings.
Open your consoleDevices, radios, uplinks, ports, the services between them, and the settings that govern all of it. Every signal below is collected continuously, baselined per site, and scored — so the graph that matters is the one an operator is shown.
Every gateway uplink, every poll — latency, jitter, and loss against that site's own history.
Access points, switches, gateways, sensors, cameras. Absent is a state, not a gap in the graph.
How many clients each radio carries, hour by hour, against the weekday it expects.
RF congestion per radio. Noisy neighbours show up before users complain.
Association, authentication, DHCP, and DNS failures, separated so the cause is visible.
CRC errors, discards, flaps, and PoE draw per port. A dying cable has a signature.
Scope exhaustion is predictable weeks out. Totality does the predicting.
Fabric-level faults that belong to no single device still get named and timed.
Every change to a network's settings is snapshotted and diffed, then placed on the incident timeline.
Vendor events and syslog, normalized and correlated with the metrics they explain.
Devices that fell behind the fleet, and settings that drifted from the template.
Temperature, humidity, door, and power where sensors exist. The closet is part of the network.
Telemetry moves through five stages. Each one produces something the next depends on, and an operator can see where any signal is at any moment.
Telemetry, events, syslog, and configuration from every managed network arrive and are normalized into one model — the same shape whatever vendor produced it.
Totality learns what normal looks like for every signal at every site — by hour, by weekday, by season — so it can tell drift from noise without a human setting thresholds.
Each signal is scored against its own baseline. A busy Monday is not an alarm. A quiet Monday might be.
Related anomalies across devices become one incident with a probable cause, the evidence behind it, a blast radius, and a timeline.
When the fix is known and the guardrails are met, Totality applies it — snapshot first, a person in the loop, reversible by design.
Corona is the operator's agent, present on every console page. Pick a client and ask in plain language. Corona reads the live telemetry, the baselines, the incidents, and the configuration history — and answers from those, citing what it read. When the data does not support an answer, it says so.
Why did the second-floor access points drop clients at 9:40 this morning?
Three access points on the second floor lost their uplink at 09:38 for about four minutes. The switch they share reported a spanning-tree topology change at 09:37, and its uplink port shows a burst of CRC errors in the same window. A configuration change to that switch was applied at 09:37 — a VLAN edit on the uplink port. Client counts recovered by 09:43 and are within the site's weekday baseline now.
Most likely cause: the port change caused a brief loop or re-convergence. The access points themselves look healthy.
Read: 3 device series, 1 switch port series, 2 events, 1 configuration diff. Read-only.
Monitoring tools are ignored when they cry wolf. Totality is built so that every alert is earned, every diagnosis is explainable, and every limit is visible.
There are no global thresholds. A downtown retail floor and a warehouse do not share a definition of busy, so every baseline is per-signal, per-site, and per-time-of-week. Alerts come from deviation, not from a number someone typed.
Three access points losing clients, a switch reporting a topology change, and a burst of uplink errors is one incident, not three pages. Totality groups anomalies that share a cause and names the cause.
Every incident carries the signals that produced it, the baseline they were scored against, and the exact window. An operator can disagree with the diagnosis — and see why Totality reached it.
Coverage and maturity are visible per site. A network with two weeks of history is labelled as such, and Totality will not score seasonally against a baseline it has not earned.
Every change to a network's settings is snapshotted and diffed. When an incident starts ten minutes after a change, the change is on the timeline — the first question answered before it is asked.
Observation never requires write access. Remediation is enabled per client, per action, by your team, and every action Totality takes is recorded with what authorized it.
Whether your team designed a client's network or inherited it, Totality gives every operator the same view of the whole fleet: every site, every device, every incident, and which client it belongs to — from one console, on one credential per platform. Clients see the result, which is a network that stays up.
Organizations, networks, and devices via the Dashboard API, on a read-only key you control. Every organization you manage, one credential, isolated per client inside Totality.
Every console you own through the Site Manager API, with per-site coverage and maturity shown honestly. Owner-key polling, config backup, and the same incident model as Meraki.
Each client is its own tenant — isolated at the database and enforced in the application. Your team sees the whole fleet; nothing crosses between clients.
Automated remediation is only worth having if it is safer than a tired operator at 2 a.m. Totality holds itself to rules it cannot bend.
Each MSP runs its own instance. If you already have one, your console is a click away.