It was noticed in this PR that the expected @timestamp value has shifted by quite a large amount. It is a known issue that date parsing has changed in newer version of the stack due to a Java update, however, I'm not entirely sure this is related. Specifically, the year, month, and day have all shifted to unexpected values (and it doesn't seem like a locale issue).
Further investigation is required to know why the timestamp has shifted so much.
-"@timestamp": "2021-01-04T12:37:16.428-06:00",
+"@timestamp": "2020-12-27T12:37:16.428-06:00",
Tests will not fail since @timestamp has been marked as dynamic field.
It was noticed in this PR that the expected @timestamp value has shifted by quite a large amount. It is a known issue that date parsing has changed in newer version of the stack due to a Java update, however, I'm not entirely sure this is related. Specifically, the year, month, and day have all shifted to unexpected values (and it doesn't seem like a locale issue).
Further investigation is required to know why the timestamp has shifted so much.
Tests will not fail since
@timestamphas been marked as dynamic field.