What is Walking Synthetic Monitoring?
Walking synthetic monitoring is the practice of measuring application-layer network performance — DNS resolution, TCP connection, TLS handshake, time-to-first-byte — from a client device while physically moving through the space where users actually work, sampling continuously and recording the context (position, time, and what the operator sees) for every measurement.
It combines two disciplines that have never met:
- Synthetic monitoring, born in the web world: scripted probes that measure a service the way a real client would, at regular intervals — but always from fixed points (a datacenter, a branch-office sensor).
- Wi-Fi site surveying, born in the RF world: walking a building to map radio coverage — but blind to everything above the radio.
Walking synthetic monitoring takes the probe from the first discipline and the walking from the second. The result is a map of what users actually experience, sampled where they actually stand.
The problem it solves
Every IT team knows the ticket: “the Wi-Fi is slow here.” The classic response is an RF survey, and the classic outcome is a green heatmap: -58 dBm everywhere, SNR fine, channels clean. Case closed — except users keep complaining.
That's because the radio is only the first hop. Between an operator's scan gun and a “line confirmed” on screen there's a DHCP lease, a DNS resolution, a TCP handshake, a TLS negotiation — often through an internal proxy — and a backend response. Any of those can eat two seconds in a specific corner of the building (an overloaded resolver for one VLAN, a misrouted subnet, a roaming event that resets TCP sessions mid-aisle) while the RF stays perfect.
A fixed sensor won't catch it either, unless it happens to sit in that corner. A speed test won't catch it: one number, one moment, one place. The failure is spatial and layered — so the measurement must be spatial and layered too.
The method
A walking synthetic monitoring session has four defining properties:
1. Per-sample application probes. At every step, the client fires a complete request against a meaningful endpoint (your WMS, your ERP health-check, an internal service) and decomposes the timing: DNS, TCP, TLS, TTFB. Not a ping — a real protocol exchange, the thing users actually do.
2. Spatial continuity. Samples are taken continuously along the walk, not at a handful of chosen spots. Degradation patterns emerge as you cross cell boundaries, enter metal-shelved aisles, ride elevators.
3. Synchronized context. Each sample carries its moment: timestamp, position, and ideally a video frame of what the surveyor saw. A measurement you can't place and can't replay is an anecdote; one you can scrub on a timeline is evidence.
4. A reproducible verdict. The output isn't a pile of CSVs but a deterministic judgement — graded, thresholded, explainable — so two surveys of the same site are comparable, and a before/after of a remediation actually proves something.
What it is not
It's not an RF site survey: it doesn't replace spectrum analysis, predictive AP placement or heatmap design — those remain the territory of tools like Ekahau and Hamina, and a well-designed network needs them. It's not fixed-sensor monitoring (Aruba UXI-style): sensors watch one point forever; walking monitoring covers the whole space, on demand, with no per-point hardware. And it's not a speed test: it measures protocol phases, not a single throughput number.
The honest framing: walking synthetic monitoring complements RF surveying. Design the radio with an RF tool; verify the experience by walking it.
Where it applies
- Warehouses and logistics — scanner terminals roaming between cells under throttling, WMS timeouts at aisle ends
- Acceptance testing — proving a new or remediated network meets application-level targets, with evidence
- Multi-site IT — periodic walked baselines of branch offices, comparable over time
- Disputes and audits — when “the network was fine” needs to be demonstrable, not asserted
- Continuous sentinel monitoring — the same probe methodology from a fixed low-cost device between walks
Why the term exists
We coined “walking synthetic monitoring” at Radaria because the thing we built didn't fit any existing box: survey tools measured the wrong layer, synthetic monitoring stood still, and “Wi-Fi diagnostics” had come to mean screenshots of signal bars. Naming the method matters more than naming the product: any tool that probes the application layer per-sample, continuously, in motion, with synchronized context and a reproducible verdict, is doing walking synthetic monitoring — and networks will be better for it.
Radaria happens to be the first implementation: Android app on any device, EU cloud, synchronized video replay, A–F verdict with AI explanation in five languages. See how it works or try it free.
Further reading