When scheduling a monitoring check, the async interval calculates the duration since the last monitor check.  Internally we use process.hrtime() to calculate the time of execution, which should be monotonically increasing and guarantee that the time since the last monitor check is always calculated to be positive.  However, as a result of this comment and recent AWS lambda issues (issues in environments where timers / clocks may behave strangely), we would like to add a mechanism to log/record this error if it ever occurs.

Implementation could vary, but options could include logging a process warning, connecting the interval into SDAM and logging a SDAM failure, or something else entirely.

An additional optional but nice-to-have acceptance criteria would be to enhance the monitor with useful logging capabilities, so that if we encounter issues from users going forward, we have logging capabilities available.