-
Bug
-
Resolution: Done
-
Critical
-
netobserv-1.11-candidate
-
None
-
False
-
-
None
-
None
-
None
-
None
-
NetObserv - Sprint 283
-
None
-
None
-
None
Description of problem:
Enabling Xlat feature causing flowlogs agent with past timestamp and eventually rejected by Loki (here using 0-click loki 2.9.0)
time=2026-01-20T20:16:54Z level=info component=client error=server returned HTTP status 400 Bad Request (400): 13 errors like: entry for stream '{K8S_FlowLayer="infra", app="netobserv-flowcollector"}' has timestamp too old: 2026-01-20T14:06:33Z, oldest acceptable timestamp is: 2026-01-20T20:01:54Z fields.level=error fields.msg=final error sending batch host=loki:3100 module=export/loki status=400
time=2026-01-20T20:16:57Z level=info component=client error=server returned HTTP status 400 Bad Request (400): 4 errors like: entry for stream '{K8S_FlowLayer="infra", app="netobserv-flowcollector"}' has timestamp too old: 2026-01-20T14:24:13Z, oldest acceptable timestamp is: 2026-01-20T20:01:57Z; 9 errors like: entry for stream '{K8S_FlowLayer="infra", app="netobserv-flowcollector"}' has timestamp too old: 2026-01-20T14:13:35Z, oldest acceptable timestamp is: 2026-01-20T20:01:57Z fields.level=error fields.msg=final error sending batch host=loki:3100 module=export/loki status=400
Steps to Reproduce:
1. Deploy 0-click loki with grafana/loki:2.9.0 image 2. Deploy 1.11 NOO and Flowcollector with Xlat enabled 3.
Actual results:
Flows are dropped as Loki rejects them from past timestamp
Expected results:
Flows should not have past timestamp