Skip to content

Sentinel Site Monitoring

Monitoring panel — instantiates Vulnerability Hotspot Mapping and Hardening

Watches a few carefully chosen high-risk sites continuously, so a hotspot turning active — or risk migrating to a new one — is caught early.

A hotspot map is a snapshot; risk moves. Sentinel Site Monitoring is the standing early-warning layer: a small panel of deliberately chosen indicator sites — the most exposed, the most representative, the fastest to turn — watched continuously so a hotspot going critical is seen while it is still cheap to act, and so risk migrating to a new location after a fix is caught before it becomes the next incident. Its defining move is to trade coverage for latency: deep, live watch on a chosen few rather than shallow, lagging watch on everything. That is what separates it from rolling recalibration, which periodically re-scores the whole map instead of continuously watching a few sites.

Example

A public-health agency cannot test every mosquito pool in the state for an arbovirus, so it runs sentinel surveillance: a dozen sites — the historically hottest wetlands plus a few representative suburbs — with caged sentinel flocks and traps checked weekly. When one sentinel site turns positive, it is an early signal for the surrounding region long before human cases appear, triggering targeted spraying and public warnings there. The panel also watches for migration: after aggressive control at last year's hotspot, monitoring a ring of new candidate sites catches the virus resurfacing two counties over — risk that moved rather than vanished. A few sites watched closely buy weeks of lead time that testing everywhere, slowly, never could.

How it works

  • Choose sites for signal, not coverage. Pick the few sites that lead the system — most exposed, most representative, or fastest to turn — so their state forecasts the rest rather than merely sampling it.
  • Watch continuously against thresholds. Instrument the panel with live indicators and pre-set trip levels that fire an alert, not a quarterly report nobody reads in time.
  • Watch the ring, not just the center. Include sites where risk would migrate after an intervention, so a displaced hotspot is caught as it emerges instead of after it detonates.

Tuning parameters

  • Site count versus depth — more sentinels widen coverage but dilute the attention each receives; fewer go deeper and faster.
  • Sentinel selection — leading and most-exposed sites versus representative ones; this sets whether the panel warns early or estimates the average.
  • Alert thresholds — how sensitive the trip levels are. Tighter catches more but cries wolf; looser is calm but late.
  • Migration ring — how wide a net of candidate new-hotspot sites to watch after a fix, trading breadth against focus.

When it helps, and when it misleads

Its strength is that it buys lead time and catches risk migration cheaply, turning a static map into a live one without instrumenting the whole system.

Its failure modes are about the sample. Sentinels are a biased sample by construction — the chosen sites can stop representing the system as it changes, so the panel stays quiet while risk builds off-panel. And a fixed panel invites watching where the light is — monitoring the convenient sites rather than the informative ones. The discipline is to periodically re-justify each sentinel against the recalibrated map, and to treat a quiet panel as reassurance only while its coverage is still valid.

How it implements the components

Sentinel Site Monitoring fills the live-detection components — the ones that watch continuously rather than measure, rank, or fix:

  • sentinel_monitoring_panel — it is the chosen panel of indicator sites, their live instrumentation, and their alert thresholds.
  • spillover_and_risk_migration_watch — it explicitly watches for risk relocating after an intervention, not just the original hotspot going active.

It does not re-score or re-rank the full map on a cadence (maintenance_and_recalibration_cadence, Rolling Hotspot Recalibration) and it does not fire the act-now trigger for a fix window (readiness_window_trigger, Targeted Hardening Sprint).