Solution / Import and sync monitoring

Monitor Data Imports and Synchronization Jobs

Separate missing execution evidence from stale input, stalled progress and application-level data validation.

Solution pattern; progress semantics remain application-defined

Why import jobs can look healthy while being wrong

An import or synchronization worker may remain alive while waiting on one record, retrying stale input or failing to advance its cursor. A final heartbeat alone can miss that class of failure.

Use a meaningful progress marker

The application can report a last processed batch, cursor, sequence or source watermark. The marker must have a stable meaning and should move during active processing. A marker that is allowed to remain unchanged needs explicit idle semantics.

Separate the evidence

  • Heartbeat Monitor: did the worker report?
  • Dead Man Monitor: did an expected report disappear?
  • Dead Hand Monitor: did active progress become stale?
  • Application validation: are the destination records correct?

HeartbeatHook does not inspect imported records or declare data correctness. It provides a communication and evidence contract around application-defined signals.

Explore stuck-process monitoring