Interface SchedulerDiagnosticsRecord

Cumulative counters for one (approved job alias, operation) pair of one scheduler source (M98k).

count counts settled observations, never currently active calls. On a fire record it is local timer fires observed; started the fires that entered local dispatch (fire slot claimed AND the handler mutex acquired); contended the fires skipped because the fire slot was claimed by another replica, or the registration-time delay slot was not this replica's, or the overlap mutex was held elsewhere; lockFailed the fires skipped because a lock operation rejected during the skip-decision; succeeded/failed the dispatches that settled fulfilled or rejected-after-their-final-attempt; lastLatenessMs the last fire's max(0, actualStart - intendedFire) in wall-clock milliseconds — a skipped local fire is never a globally missed execution, so no missed counter exists; retryAttempts is nonapplicable and 0.

On an attempt record count is settled handler attempts; started the handler invocations begun; succeeded/failed the settled outcomes; retryAttempts the attempts numbered above 1; contended and lockFailed are nonapplicable and 0; lastLatenessMs is nonapplicable and 0 — lateness is a property of the fire, reported there only.

Every counter saturates independently at Number.MAX_SAFE_INTEGER and is a finite non-negative safe integer; durations are integer milliseconds on the runtime's monotonic clock; lastDurationMs is null exactly when no settled observation of this tuple has carried a duration in the current retention window. Cumulative within the retention window: an expired record is cleared and starts from zero. No job name, cron expression, payload, lock key or token, or thrown value is ever carried; the record's alias is the application-approved job alias — never the raw name.