Intermittent Sampling¶
Sample periodically or irregularly to detect intermittent states that continuous monitoring cannot afford or guarantee.
Essence¶
Intermittent Sampling is the pattern of making fleeting conditions observable without watching everything all the time. It is useful when a state, failure, behavior, symptom, or environmental condition appears briefly and then disappears before ordinary inspection can see it. The intervention is not merely “check sometimes.” It is a sampling design: decide what counts, when and where to look, how long to observe, how to record context, and what response follows when a sample is positive.
The core insight is that partial observation can be powerful when the observation windows are deliberately chosen. A sparse sample can outperform a large amount of unfocused monitoring if it is timed near likely episodes, randomized against gaming, placed at informative sentinel points, or escalated during burst windows.
Compression statement¶
When a condition appears intermittently and continuous monitoring is costly, sample strategically to catch enough occurrences for diagnosis or control.
Canonical formula: intermittent condition + insufficient continuous observability + bounded sampling windows + capture criteria + follow-up response -> usable evidence without full-time monitoring
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
The relevant event or state appears in bursts or intermittent episodes, making ordinary observation miss it.
What this problem means
The structural problem is a mismatch between **episode duration** and **observation availability**. The event exists, but not long enough or predictably enough for the normal observation rhythm to catch it. Reports accumulate without proof, failures vanish before inspection, and the system confuses “not seen” with “not real.”
This pattern often appears when bursts, rare events, compliance lapses, symptoms, or defects are real but irregular. The organization may overreact by monitoring everything continuously, or underreact by dismissing reports because scheduled reviews show normal conditions. Intermittent Sampling creates a middle path: bounded observation designed around the intermittent nature of the target.
Applicability expression4 distinct conditions
groundedpartly groundedopen
4 conditions, all required.
4Required in every casenumbered 1–4
These hold no matter which pattern applies.
Sparse target bursts · grounded
The target state appears in sparse, irregular bursts separated by near-baseline periods.
The source archetype describes the situation as follows: The target state appears briefly, irregularly, or in bursts. The normalized requirement above isolates the load-bearing portion used in this condition set.
primeIntermittency— Irregular bursts.
Costly continuous monitoring · open
Continuous monitoring is too costly, noisy, intrusive, risky, or unavailable.
Use this archetype when the system repeatedly says, “The problem happens, but never when we are looking.” It fits situations where continuous monitoring is too expensive, intrusive, noisy, or technically impossible, yet waiting for normal review misses the condition. The narrower requirement in this condition set is: Continuous monitoring is too costly, noisy, intrusive, risky, or unavailable.
Late anecdotal evidence · 2 cases · 0 matched
Existing evidence of the target state is anecdotal or arrives too late.
The source archetype describes the situation as follows: Existing evidence is anecdotal or delayed. The normalized requirement above isolates the load-bearing portion used in this condition set.
Observation-reactive event · grounded
Predictable observation may alter the intermittent event being measured.
The source archetype describes the situation as follows: The event may be influenced by predictable observation. The normalized requirement above isolates the load-bearing portion used in this condition set.
domainHeisenbug— Name the software defect whose failure vanishes under observation because attaching a debugger, adding a print, or disabling optimization perturbs the timing window or interleaving it rides on — so disappearance-under-observation is the diagnostic tell, not evidence the bug is gone.
context guardThe debugging observation occurs on a predictable investigation schedule.
suppliesThe occurrence or timing of observation is predictable.
How this was matched — 4 requirements, all needed
Predictable observation can perturb an intermittent target event.
All of
- roleA target event occurs intermittently and is being measured.
- roleThe occurrence or timing of observation is predictable.
- modalityThe predictable observation may alter the target event.
- causalityAny alteration would be caused by the predictable observation.
Other requirements and context (1)
Why these sit outside the expression
Application gate — it governs whether applying the archetype is appropriate or material, rather than defining the structural problem itself.
Application gateA follow-up action depends on confirming the intermittent condition.
Coverage
2 of 4 conditions grounded · 2 open.
When to Use This Archetype¶
Use this archetype when the system repeatedly says, “The problem happens, but never when we are looking.” It fits situations where continuous monitoring is too expensive, intrusive, noisy, or technically impossible, yet waiting for normal review misses the condition. It also fits when evidence is anecdotal and decisions require more disciplined capture.
Do not use it when the condition is stable and easy to observe, when a one-time diagnostic test can reproduce the issue, or when misses are catastrophic enough that sparse observation is unacceptable. In those cases, continuous monitoring, fail-safe design, direct testing, or prevention may be more appropriate.
Structural Problem¶
The structural problem is a mismatch between episode duration and observation availability. The event exists, but not long enough or predictably enough for the normal observation rhythm to catch it. Reports accumulate without proof, failures vanish before inspection, and the system confuses “not seen” with “not real.”
This pattern often appears when bursts, rare events, compliance lapses, symptoms, or defects are real but irregular. The organization may overreact by monitoring everything continuously, or underreact by dismissing reports because scheduled reviews show normal conditions. Intermittent Sampling creates a middle path: bounded observation designed around the intermittent nature of the target.
Intervention Logic¶
The intervention begins by defining the sampling target. A vague concern such as “quality is inconsistent” becomes a more observable target such as “surface defect visible during the first hour after tool change.” The system then chooses a sampling strategy: scheduled, randomized, triggered, sentinel-based, rotating, or burst-window focused.
Each sample needs a window, a detection threshold, and a record. A sample that says only “checked” is weak. A useful sample records when observation was open, what was seen, what context surrounded it, whether the threshold was crossed, and what follow-up happened. The design is then tuned by reviewing false negatives, false positives, coverage gaps, and whether positive detections actually changed action.
Key Components¶
Intermittent Sampling makes fleeting conditions observable without watching everything all the time by designing observation moments around the intermittent nature of the target. The Sampling Target names the elusive state being sought — a failure mode, behavior, symptom, defect, spike, or lapse — so the work does not collapse into a generic inspection ritual. The Sampling Window defines when observation is active and how long it lasts; a window must be long enough to catch the state but bounded enough to preserve the point of sampling rather than drifting into continuous monitoring. The Sampling Schedule or Trigger determines how those windows open — on a planned interval, randomly, after warning signals, or at high-risk moments — translating a hypothesis about intermittency into actual observation chances. The Coverage Model prevents false confidence by clarifying what the sampling plan can and cannot see and whether the samples are representative enough for the decisions they inform.
The remaining components convert observation into evidence and action. The Detection Threshold separates signal from noise and sets the balance between false positives and false negatives, defining what counts as a positive sample. The Event Log preserves sampled observations along with timing, context, and useful non-detections; without a log, intermittent evidence remains anecdotal and disappears between windows. The Follow-up Response specifies what happens after detection — confirm, escalate, diagnose, increase sampling, repair, or change the sampling design — and is what makes intermittent sampling an archetype rather than a measurement habit. Several Optional Components strengthen the design where gaming, blind spots, or risk shifts would otherwise erode it: a randomization rule when predictable sampling would be gamed, a sentinel probe when a few observation points can reveal a wider condition, context metadata to capture load and configuration around each sample, a sampling escalation rule that increases density when risk rises, and a false-negative review that asks what the plan missed and how to improve it.
| Component | Description |
|---|---|
| Sampling Target ↗ | The sampling target names the intermittent state being sought. It can be a failure mode, behavior, symptom, defect, spike, lapse, or environmental condition. A clear target prevents the sample from becoming a generic inspection ritual. |
| Sampling Window ↗ | The sampling window defines when observation is active and how long it lasts. Window length matters because an intermittent event may be visible for seconds, minutes, hours, or a brief phase of a process. The window should be long enough to catch the state but bounded enough to preserve the point of sampling. |
| Sampling Schedule or Trigger ↗ | The schedule or trigger determines how sample windows open. Some samples happen on a planned interval, some randomly, some after warning signals, and some at high-risk moments. This component is where the intervention translates a hypothesis about intermittency into actual observation chances. |
| Coverage Model ↗ | The coverage model explains what the sampling plan can and cannot see. It may be statistical, heuristic, or practical. Its purpose is to prevent false confidence by clarifying whether samples are representative enough for the decisions being made. |
| Detection Threshold ↗ | The detection threshold defines what counts as a positive sample. It separates signal from noise and determines the balance between false positives and false negatives. A threshold can be a number, a categorical criterion, a behavioral marker, or a procedural condition. |
| Event Log ↗ | The event log preserves sampled observations. It records both detections and useful non-detections, plus timing, context, and follow-up. Without a log, intermittent evidence remains anecdotal and disappears between sample windows. |
| Follow-up Response ↗ | The follow-up response specifies what happens after detection. The response might confirm, escalate, diagnose, increase sampling, repair, intervene, or change the sampling design. Sampling becomes an archetype-level solution only when captured evidence changes action. |
Common Mechanisms¶
9 catalogued mechanisms: 8 documented across 5 implementation forms; 1 awaits an authored page and reviewed form classification.
The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.
Assessment, Review & Assurance · 1 mechanism
- Spot Check — A short, bounded inspection of selected cases or moments used to catch intermittent defects, lapses, or state changes without monitoring everything continuously.
Control, Automation & Runtime · 1 mechanism
- Burst Capture Logging — Temporary or conditional logging that increases observational density around suspected bursts so short-lived episodes leave usable evidence.
Experiment, Test & Rehearsal · 1 mechanism
- Canary Probe — A lightweight probe placed in a system to periodically or conditionally reveal whether an intermittent failure, exposure, or degradation is occurring.
Monitoring, Sensing & Alerting · 4 mechanisms
- Diagnostic Sampling — A targeted measurement method used when an intermittent condition is suspected but cannot be observed continuously or reproduced reliably.
- Sample Review Dashboard — A dashboard that summarizes sample frequency, detections, misses, coverage gaps, and follow-up status so the sampling regime can be tuned.
- Sentinel Survey — A recurring or opportunistic survey of selected sentinels that provides signal about intermittent experiences, symptoms, or behaviors in a larger population.
- Temporary Sensor Deployment — A time-limited or condition-triggered instrument that samples a location, device, process, or environment when permanent instrumentation is too costly.
Protocol, Workflow & Routine · 1 mechanism
- Rotating Inspection — A rotating schedule that samples different sites, teams, units, or subsystems over time to broaden coverage without inspecting all of them at once.
Not Yet Form-Classified · 1 mechanism
- Randomized Audit — A sampling procedure that chooses cases or times unpredictably to reduce bias, gaming, and systematic blind spots.
Parameter / Tuning Dimensions¶
The main tuning dimensions are sample frequency, window length, target specificity, trigger sensitivity, threshold strictness, randomness, sentinel placement, context depth, escalation criteria, and review interval. Each dimension changes a tradeoff.
Higher frequency improves capture probability but increases burden. Longer windows improve capture but approach continuous monitoring. Lower thresholds catch more episodes but create false positives. Randomness improves anti-gaming and coverage but can be harder to coordinate. Rich context improves diagnosis but raises privacy, complexity, or storage costs.
Invariants to Preserve¶
The first invariant is representativeness: the samples must be good enough for the action they inform. The second is bounded burden: the system should know when intermittent sampling is cheaper or safer than continuous monitoring and when it has crossed that line. The third is actionability: positive samples must trigger a defined response. The fourth is uncertainty honesty: sparse sampling must never pretend to be complete coverage.
Target Outcomes¶
A successful design catches more intermittent episodes with usable context. It reduces reliance on anecdotes, lowers the cost of observation compared with full monitoring, and improves response timing. It should also improve over time as false negatives, false positives, and coverage gaps are reviewed.
The target outcome is not perfect knowledge. The target is enough well-designed evidence to support better diagnosis, preparation, governance, or control.
Tradeoffs¶
Intermittent Sampling trades completeness for feasibility. It accepts that some events will be missed in exchange for lower cost, lower burden, or less intrusive observation. It also trades predictability against gaming: planned windows are easier to staff, but randomized windows may reveal more truth. It trades sensitivity against follow-up load: permissive thresholds catch more episodes but may overwhelm response capacity.
Ethically, sampling can become surveillance when people are the target. The design should minimize unnecessary data collection, distribute burden fairly, and make the purpose and governance of sampling clear where disclosure does not defeat the method.
Failure Modes¶
A common failure mode is the systematic miss pattern, where sampling always happens at the wrong time. The mitigation is to review misses, vary windows, add triggers, or randomize timing.
Another failure mode is false reassurance. Sparse non-detections can be misread as proof that no problem exists. The mitigation is to report coverage limits and known blind spots.
A third failure mode is sampling theater. The system performs checks to show diligence, but no one defines thresholds, records context, or responds to detections. The mitigation is to tie each sample to a follow-up decision.
A fourth failure mode is over-sampling creep, where bounded sampling expands into continuous monitoring without governance. The mitigation is to define observation budgets, sunset rules, escalation criteria, and privacy review.
Neighbor Distinctions¶
Intermittent Sampling is distinct from Observability Instrumentation because it is about bounded observation windows for transient conditions, not measurement infrastructure in general.
It is distinct from Statistical Sampling because the central problem is catching intermittent visibility, not estimating a population parameter. Statistical validity may matter, but it is not the whole archetype.
It is distinct from Intermittent Failure Capture because failure capture preserves detailed state during rare failure episodes. Intermittent Sampling may only detect that an episode occurred or provide screening evidence.
It is distinct from Perturbation Testing because perturbation testing induces a condition. Intermittent Sampling observes naturally occurring episodes.
It is distinct from Periodic Review and Reset because review-and-reset corrects drift; intermittent sampling primarily creates evidence about transient states.
Cross-Domain Examples¶
In cloud reliability, a team may enable detailed traces only after warning-level latency spikes. This catches transient failure states without paying the cost of continuous deep tracing.
In manufacturing, rotating spot checks during different shift phases can reveal sporadic defects that final inspection misses.
In clinical care, a symptom diary can capture episodic dizziness, pain, mood, or side effects that are absent during appointments.
In compliance, randomized audits can reveal intermittent lapses that predictable reviews would miss.
In environmental monitoring, temporary sensors can sample noise, emissions, or flow during suspected peak windows instead of permanently instrumenting every possible location.
Non-Examples¶
A permanently installed sensor measuring a stable condition is continuous monitoring, not Intermittent Sampling. A quarterly review that resets goals is Periodic Review and Reset. A controlled stress test that intentionally creates a failure condition is Perturbation Testing. A dashboard that merely visualizes already collected data is a mechanism, not this archetype.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (3)
- Intermittency: Irregular bursts.
- Observability: Infer internal state externally.
- Sampling (Representativeness): Representative subset selection.
Also references 14 related abstractions
- Adaptive Capacity: Ability to change.
- Approximation: Good-enough representation.
- Confidence Intervals: Range of plausible values.
- Data Integrity: Accuracy and consistency preserved.
- Feedback: Outputs influence inputs.
- Foreseeing (Prediction): Predict future states.
- Hypothesis Testing (Null vs. Alternative): Null vs alternative evaluation.
- Pattern Recognition: Identify regularities.
- Periodicity: Regular cycles.
- Randomness: Model unpredictability.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Scheduled Intermittent Sampling · temporal variant · recognized
Sampling at planned intervals to make intermittent states visible without continuous monitoring.
- Distinct from parent: The parent includes any strategic intermittent observation; this variant specifically uses planned timing.
- Use when: {'condition': 'Episodes are not easily triggered but occur often enough that a recurring window may catch them.'}; {'condition': 'The cost of continuous observation is too high but predictable sampling will not create unacceptable gaming.'}.
- Typical domains: maintenance, education, compliance, operations
- Common mechanisms: Spot Check, Rotating Inspection
Randomized Intermittent Sampling · implementation variant · recognized
Sampling at unpredictable times or cases to reduce bias, gaming, and patterned misses.
- Distinct from parent: The parent does not require randomization; this variant makes randomization central.
- Use when: {'condition': 'Predictable checks would change behavior or allow the target condition to hide.'}; {'condition': 'Regular sampling aligns badly with the intermittent pattern.'}.
- Typical domains: compliance, security, quality control, field inspection
- Common mechanisms: Randomized Audit
Triggered Intermittent Sampling · temporal variant · recognized
Opening a sample window when a proxy signal suggests the intermittent state is likely to appear.
- Distinct from parent: The parent can use fixed or random sampling; this variant is conditional on a signal.
- Use when: {'condition': 'There is a weak but useful leading indicator of the episode.'}; {'condition': 'Sampling all the time is too costly, but sampling after a trigger is cheap enough.'}.
- Typical domains: software operations, medicine, manufacturing, environmental monitoring
- Common mechanisms: Canary Probe, Temporary Sensor Deployment
Sentinel Sampling · scale variant · recognized
Sampling selected sentinel locations, actors, devices, or cases that are likely to reveal intermittent states earlier or more cheaply than broad coverage.
- Distinct from parent: The parent can sample any population; this variant deliberately chooses sentinel points.
- Use when: {'condition': 'Full coverage is impossible but some points are especially informative.'}; {'condition': 'The intermittent state tends to show first in exposed, sensitive, central, or high-signal locations.'}.
- Typical domains: public health, infrastructure, education, community monitoring
- Common mechanisms: Sentinel Survey
Burst-Window Sampling · risk or failure variant · candidate
Sampling densely during suspected burst windows and sparsely outside them.
- Distinct from parent: The parent may sample at any bounded rhythm; this variant concentrates observation around bursts.
- Use when: {'condition': 'The target condition clusters in bursts rather than appearing uniformly.'}; {'condition': 'The system can identify likely burst periods from load, season, event, or early-warning signals.'}.
- Typical domains: cloud operations, customer support, disaster response, retail
- Common mechanisms: Burst Capture Logging
Near names: Spot Sampling, Intermittent Audit, Event Sampling, Diagnostic Sampling, Random Inspection, Burst Capture Sampling.
Editorial Notes¶
Problem Classification¶
Classification: Observability, Measurement & Feedback Gaps → Temporal Sampling, Decay & Transition Resolution
Problem kernel: sampling cadence misses burst-like states
Rationale: Observation windows are too sparse or poorly synchronized with intermittent episodes to resolve the event.
Independent corroboration: The earliest necessary condition in the frozen evidence is: The relevant event or state appears in bursts or intermittent episodes, making ordinary observation miss it. That is a temporal sampling decay and transition resolution problem because Observation cadence or anchoring does not match state dynamics, so brief events, decaying effects, accumulated drift, and approaching transitions are missed.
Review outcome: Independent reviewer agreement; high confidence.