...
Moving the clock backwards will cause a gap in data collection and service monitoring. Each up.time monitor logs a timestamp of the last time it ran to determine if (or when) it needs to run again. For example, if a monitor ran at 2 PM and you change clock back to 12 PM, the monitor will not run again until the clock once again reaches 2 PM. This gap is deliberately created to avoid the undesirable alternate result of creating duplicate historical data, which would occur if the monitors were forced to start running immediately after the time change.Note that both
| Note | ||
|---|---|---|
| ||
| Both of these scenarios are temporary issues that occur only during the few hours between the original and new time settings. Note also that changing the time on a target agent system will have no impact on up.time monitoring. |