Timestamps falls back in time while sequence numbers increases.

[emvarunp]

Summary

We are observing a case where observations with monotonically increasing sequence numbers have timestamps that go backwards in time. Worth noting that IgnoreTimestamps is set to true on this agent, so assuming all timestamps are being generated by the agent rather than forwarded from an adapter.

---

Observed behavior

Sequence numbers increase without interruption, but timestamps jump backwards by hours at certain points in the stream. The attached screenshot shows this for a single data item (Execution).

Example from the attached data:

Sequence    Timestamp   Value
1222952232  14:43:04    ACTIVE
1222954278  10:18:18    STOPPED     ← goes back ~4h 25m
1222959352  11:06:57    READY
1222959353  11:06:58    STOPPED
1222960215  11:07:11    ACTIVE

Sequence is strictly increasing. Timestamps are not.

---

Environment

• Agent version: 2.7.0.11
• Schema version: 2.4
• IgnoreTimestamps: true
• DataItem type: Execution (category: EVENT)

---

[wsobel]

What was the source agent that is being replicated? Please attach the source Device.xml and any logs from both agents if possible.

[wsobel]

I think this issue is fixed in the upcoming version 2.7.0.12. Once the pull request is merged, it can be tested. The behavior was incorrect on reconnect to a continuing stream, and it caused earlier data to be replayed from the source agent. The problem has now been resolved and tested. It needs more verification to validate in production.