AXIS SENTINEL WATCHTOWERCore system
Sentinel knows when it has stopped seeing.
Loss of visibility is itself a security event.
Watchtower holds an expectation of what every registered deployment should report and compares it with what actually arrives. Silence is not assumed to be health: a source that goes quiet becomes a finding, and Watchtower reports on its own health as a separate fact.

- 01ObserveContinuous telemetry from every service and edge you connect. (Watchtower operates here)
- 02VerifyTelemetry checked at the gateway before it is trusted.
- 03DetectAnomaly, policy violation, and absent signal alike. (Watchtower operates here)
- 04ProtectPolicy enforced at the identity and tenant boundary.
- 05PreserveEvidence written down before it can be lost.
- 06RecoverContinuity coordinated, state restored, result verified.
Recover returns to Observe
Watchtower observes what arrives and detects what does not.
A second photograph
The city, read as structure.
The tower and the ridge are the same view. The buildings are drawn as structure. The two photographs are shown apart, because they are not the same pixels.

The grammar of a signal
Steady, uneven, gone. The absence is the finding.
Watchtower does not wait for a source to report a problem, because a source that has stopped cannot. It holds an expectation for every source and reads the shape of what arrives against it.
You cannot protect what you cannot see. A sensor that stops talking is itself a signal.

Every source owes Watchtower a signal at a fixed rhythm, so each source is a rail with a slot for every beat it owes, running from the past toward now. A beat that arrives lights its slot and sends up a filament of light. A beat that does not arrive leaves a hollow ring where it should have been. A monolithic wall stands at now, with one slit for every source: a slit holds light while that source reports and is dark where it has gone quiet. The four states are steady, uneven, stopped, and in sequence, where related sources stop one after another. Reading that last pattern as a possible suppression is a design direction, not built today.
Steady. Every source owes a beat at a fixed rhythm, and every slot is lit all the way to now.
- SteadySteady. Every source owes a beat at a fixed rhythm, and every slot is lit all the way to now.
- UnevenUneven. One source still reports, but late and in fits. Some slots light, some do not.
- StoppedStopped. Its beats end partway along the rail. The slots that should follow stay dark, and the wall of light has a gap.
- In sequenceIn sequence. Related sources stop one after another, a staircase of dark slots. Reading that as a pattern is a design direction, not built today.
- Full coverage
Expected telemetry is arriving on its rhythm.
- Degraded observation
Signals late or partial. The picture is incomplete and marked so.
- Blind spot
Expected telemetry has stopped. Not knowing is the finding.
- Possible suppression
Related sources going dark in a pattern, rather than as an ordinary outage.
- Arrived on time
- Arrived late
- Expected, not received
The coverage view
Whether Sentinel can still see what it is responsible for.
Every registered deployment is expected to report on a regular rhythm. Command shows when each was last seen, how long it may stay quiet, and why a source changed state.

Watchtower
Visibility, by deployment
Last scheduled passThis minuteCurrent
- Registered
- Shown
- Visible
- Shown
- Degraded
- Shown
- Not yet seen
- Shown
- Disabled
- Shown
- Primary sitewww.example · productionOn timeExpected reporting rhythmVisible
- Customer portalportal.example · productionOn timeExpected reporting rhythmVisible
- Checkoutpay.example · productionQuiet too longExpected reporting rhythmDegraded
- Documentationdocs.example · productionOn timeExpected reporting rhythmVisible
- Partner APIapi.example · productionQuiet too longExpected reporting rhythmDegraded
- Status pagestatus.example · productionOn timeExpected reporting rhythmVisible
- Stagingstaging.example · stagingNever reportedExpected reporting rhythmNot yet seen
- Campaign micrositepromo.example · productionSwitched offExpected reporting rhythmDisabled
The estate view
Expected against received.
Signals rise from the estate into the observation field. Step through five snapshots, from full coverage to a possible suppression, and watch where the information disappears.
Illustrative demonstration
Expected against received, across an estate
Sources are shown as arriving, late or silent; example-app, then example-edge, then service-b silent.
- Arriving
- Late
- Silent
Step 5 of 5
Possible suppression
A third source in the region goes dark, and the silences form a staircase: one source after another, in sequence. A pattern is not an ordinary outage. Correlating related sources like this is a design direction for Watchtower; the demonstration shows how it would read.
Every expected signal arrives on its rhythm. Twelve of twelve sources report in the latest interval, and each ring segment is whole. This is the baseline the other states are read against.
Two sources are still reporting, but late and unevenly. The picture is incomplete and is marked so: the rhythm turns intermittent and the ring segments break, yet nothing has disappeared.
One source stops. Its signal does not fade or turn red: it is gone, and the ring above it is open. Watchtower raises the silence as a finding and reports the cause as unknown, because from the server a closed page, a broken network and a removed agent look the same.
A second source in the same region falls silent soon after the first. Each is its own finding, because today's evaluator works deployment by deployment. Nothing yet says the two are connected.
A third source in the region goes dark, and the silences form a staircase: one source after another, in sequence. A pattern is not an ordinary outage. Correlating related sources like this is a design direction for Watchtower; the demonstration shows how it would read.
Scripted sources and intervals. Nothing here reads or changes a live system. Today Watchtower evaluates registered deployments by the reports they owe; the wider estate drawn here shows how coverage is meant to read.
Every source, expected against received
- Arrived on time
- Arrived late
- Expected, not received
- Right edge is the latest interval
Showing: Possible suppression
Services
- service-bRegion EU
SilentNo signal while it was expected
Went dark third of the related sources
- service-cRegion US
ArrivingOn its rhythm
- service-aRegion US
ArrivingOn its rhythm
Edge
- example-edgeRegion EU
SilentNo signal while it was expected
Went dark second of the related sources
- example-appRegion EU
SilentNo signal while it was expected
Went dark first of the related sources
- payments-serviceRegion US
ArrivingOn its rhythm
Sites
- site-primaryRegion US
ArrivingOn its rhythm
- site-portalRegion APAC
ArrivingOn its rhythm
Agents
- agent-aRegion APAC
ArrivingOn its rhythm
- agent-bRegion US
ArrivingOn its rhythm
Systems
- identityRegion US
ArrivingOn its rhythm
- buildRegion APAC
ArrivingOn its rhythm
Built today
- The unit watched is a registered deployment, expected to report on a regular rhythm.
- A deployment that stays quiet past the time it was given becomes degraded. One that has never reported is not yet seen, and one its owner switched off is counted apart.
- The same check runs on a schedule and when Command is open, so there are never two answers.
- Only a change writes: a visibility transition with its reason, a server-observed event and a notification. A deployment already degraded does not raise a new event each pass.
- The regular reports are protected from ordinary volume, so a busy estate cannot manufacture a false outage.
- Every pass writes a run record. Only a scheduled pass that finished ok proves the timer is alive.
Design direction, or not built
- Not builtCorrelating several related sources going dark in sequence as one possible suppression. Today each deployment is evaluated on its own.
- Not builtEdge and service telemetry as expected sources in the same picture as deployments.
- Not builtSaying why a source went quiet. Watchtower reports the loss and does not guess the cause.
- Not builtA watchdog for the watchdog, and alerting or paging routes. The health fact is a read, and nothing polls it on a timer.
Watchtower health
The watcher reports whether it is running.
A monitor that has stopped and still looks calm is worse than none, because someone is relying on it. Watchtower keeps its own record of every pass, and a stale answer is a fact it reports about itself.
Illustrative demonstration
The watcher watches itself
Scheduled passes
Console reads
- Last scheduled success
- Outside the staleness window
- Most recent run
- A console read, status ok
- Health fact
- Stale
Step 5 of 5
Command is told plainly
A stale answer is reported as one plain sentence: Sentinel has not checked recently. It is never reported as your sites being degraded, because nothing has checked. An estate that looks calm because nothing is looking is the failure this exists to expose.
A scheduled check runs the evaluator, whether or not anyone has Command open. Every pass writes a run record with its trigger, status, duration and any error. That record is the watcher's own proof of life.
Opening Command runs the same evaluator lazily, so the answer on screen is current. It is recorded as a read pass, and it is never counted as evidence that the scheduler is alive.
The timer stops. Reads carry on while an operator refreshes the page, and the last run now looks recent, but the scheduled lane has gone quiet. Only a scheduled pass counts, so a refresh cannot hide it.
No scheduled pass has completed inside the staleness window. The health fact turns stale. It is a fact about the watcher, separate from every deployment's visibility, and the two are never folded together.
A stale answer is reported as one plain sentence: Sentinel has not checked recently. It is never reported as your sites being degraded, because nothing has checked. An estate that looks calm because nothing is looking is the failure this exists to expose.
Scripted minutes. Nothing here reads or changes a live system. The pass, the run record and the staleness window follow the scheduled check and Command's health read; the marks on the ruler are illustrative.
Signal path
What enters it, and what leaves.
Signals in
- Agent signals, on a reserved budget
- Telemetry arrival per deployment
- The registry of deployments expected to report
- Its own scheduled run history
Watchtower
OBSERVE / DETECT
Outputs
- Visibility per deployment: visible, degraded, not yet seen or disabled
- Server-observed events when visibility is lost
- Every visibility transition, with its reason
- Watchtower health: last scheduled pass, status and staleness
Ten questions
Watchtower, answered.
The questions every Sentinel system must answer, in the same order on every system page.
Watchtower is Sentinel's visibility system. It compares the telemetry each deployment should send with what arrives, and treats silence as a finding rather than as health.
Whether Sentinel can still see what it is responsible for.
- Signals from every registered deployment
- When each deployment was last seen
- Transitions between visible, degraded and not yet seen
- Whether its own scheduled passes are running
Agent signals, charged to a reserved budget so ordinary volume cannot starve them, the arrival of telemetry, and the record of its own runs.
Whether each deployment is visible, degraded or not yet seen, and whether its own last scheduled pass is recent enough for that answer to be current.
- A deployment that has never reported is not yet seen, not degraded.
- A deployment switched off by its owner is counted apart from one that went quiet.
Raise loss of visibility as a server-observed event, record every transition, keep checking on a schedule whether or not anyone has Command open, and report when it has itself not checked recently.
It cannot say why a source went quiet. A closed page, a broken network and a removed agent look identical from the server, so Watchtower reports the loss and does not speculate.
- A console read never counts as proof that the scheduler is alive.
Design directionCorrelating several related sources going dark in sequence as possible suppression is a design direction for Watchtower; today's evaluator works deployment by deployment.
Visibility per deployment, the transitions and their reasons, and Watchtower health: the last scheduled success, the last status and whether it is stale.
Watchtower reads the signals First Light admits and its transitions become Evidence. Presence shows a page's own connection while Watchtower holds the server's view, and the two are deliberately never merged. Range proves a lost signal degrades visibility.
If Watchtower stops, Command does not show a calm estate: with no recent scheduled pass the API marks the answer stale, and the wording reserved for it is that Sentinel has not checked recently. A lost signal is reported as lost visibility, never folded into healthy.
Every pass writes a run record with its trigger, status, duration and any error. Only scheduled passes count as proof of life, so a page refresh cannot mask a stopped timer.
- A public health endpoint answers only whether the application reaches its database, and writes nothing.
Relations
Where it connects.
- First Light Receives fromSignals and telemetry arrival
- Evidence Sends toVisibility transitions as server-observed records
- Presence Exchanges withKept apart: the page's own view and the server's view
- Guard Sends toConfirmation that telemetry continues after containment
- Range Receives fromProof that a lost signal degrades visibility
- Command Sends toVisibility state and Watchtower's own health
- Sends to
- Receives from
- Exchanges with
- Outside Sentinel
Failure and health
When it fails, it says so.
In operation
Full coverage
- Signals arrive on their expected rhythm
- A scheduled pass every minute
When it fails or loses visibility
Blind spot
- Silence raised as a server-observed event
- The cause is reported as unknown, not guessed
- If Watchtower stops: the answer is marked stale ("Sentinel has not checked recently" is the reserved wording)
Watchtower states
- Full coverage (lit: in operation)Expected telemetry is arriving on its rhythm.
- Degraded observationSignals late or partial. The picture is incomplete and marked so.
- Blind spot (lit: on failure)Expected telemetry has stopped. Not knowing is the finding.
- Possible suppressionRelated sources going dark in a pattern, rather than as an ordinary outage.
How its own health is verified
- A run record for every pass
- Only scheduled passes prove the timer is alive
- Range: a lost signal must degrade visibility
The Sentinel system family
Ten systems, one institution.
Put Sentinel on guard
Choose the protection level built for where your company is today.
