How old is the latest report?
A matching identity can be stale even when its contents remain unchanged.
Research note · November 14, 2026Research question
When should a latest-known match stop being presented as current?
Method
- Choose a reporting interval and an explicit maximum acceptable age for a bounded test. Record why that age is appropriate for the workflow rather than treating a universal timeout as correct.
- Stop reports while leaving the stored identity unchanged. Advance the observation clock and check that the result distinguishes a historical match from a fresh observation.
- Introduce collector delay and clock skew separately. Preserve event time and collection time so network latency is not silently mistaken for runtime age.
Records to retain
- Expected reporting cadence
- Event and collector times
- Freshness-policy revision
- Age and availability state
Source basis
The OpenTelemetry log model includes Timestamp and ObservedTimestamp because event creation and collection need not coincide. That distinction is useful when deciding whether an otherwise valid report is recent enough to act on.
Interpretation & limits
A recent timestamp is not proof that the underlying claim is truthful. Clock synchronization and report authenticity are separate questions. No freshness threshold is established for Contour by this note.
Next experiments
- Evaluate stale, delayed and future-dated reports separately.
- Choose workflow-specific thresholds before testing operator responses.
References
Technical reference
Implementation details supporting this note, drawn directly from the maintained documentation. These are technical references, not additional papers or new experimental results. Expand a topic to inspect its method, fields and limits.