Timestamp Gap Budget Audit
Audit strictly increasing timestamp gaps against an inclusive caller maximum; no automatic missing-sample imputation.
Description
Audit strictly increasing timestamp gaps against an inclusive caller maximum; no automatic missing-sample imputation.
Large gaps between observations can violate a sampling budget even when timestamps remain ordered. A gap audit identifies the adjacent pairs that need attention.
When to use this tool
Audit strictly increasing timestamp gaps against an inclusive caller maximum; no automatic missing-sample imputation.
- Prepare the supplied times, maximumGap fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter times, maximumGap. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.gaps. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require strictly increasing times and a nonnegative maximumGap. Return every adjacent gap with its duration, earlier sample index and exceedsBudget flag, which is true only when the gap is strictly larger than maximumGap.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| times | times. | List of finite numbers; bounded by the operation |
| maximumGap | maximum gap. | Finite number; zero or greater |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.gaps | The gaps list in the ordering and representation described above. |
{
"input": {
"times": [
0,
1,
4
],
"maximumGap": 2
},
"output": {
"result": {
"gaps": [
{
"afterIndex": 0,
"duration": 1,
"exceedsBudget": false
},
{
"afterIndex": 1,
"duration": 3,
"exceedsBudget": true
}
]
}
}
}Limitations and assumptions
- A gap equal to the maximum passes. The audit neither inserts missing observations nor determines why a gap occurred; times and budget must use the same unit.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. Nonfinite results and excessively large serialized outputs are rejected.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Choose a sampling model before combining results. Earlier-sample hold, linear interpolation and index-only differences answer different questions; event cooldown, debounce and rolling limits also use different acceptance rules.
References
Similar or alternative tools
- Consecutive Threshold Streaks
Tabulate sampled consecutive threshold streaks with explicit at-or-above versus strictly-below convention; no between-sample duration inference.
- Counter Reset Segmenter
Segment a nonnegative sampled counter at decreases interpreted as reset candidates; resets and wraps cannot be distinguished from values alone.