Skip to content

fix(replay): restamp fortinet date and time - #204

Merged
catinspace-au merged 1 commit into
mainfrom
fix/replay-restamp-fortinet
Nov 21, 2026
Merged

catinspace-au merged 1 commit into
mainfrom
fix/replay-restamp-fortinet

Conversation

@catinspace-au

Copy link
Copy Markdown
Contributor

The demo freshness tile showed fortinet events as 25 days old. The demo replayer kept the captured date= and time= fields. The fortinet transform uses those fields to set @timestamp.

restamp() sets both fields to the UTC send time. wrap() calls restamp() on every line. Lines without those fields pass through. The committed fixtures stay as captured.

Done when the demo pack shows fortinet events from today.

The replayer sent the body's date= and time= fields as captured. The fortinet transform takes @timestamp from those fields, so replayed events kept their capture time.

restamp() sets both fields to the UTC send time. wrap() calls restamp() on every line before adding the syslog header. A line without the fields is unchanged. The committed fixtures stay as captured.
@catinspace-au
catinspace-au merged commit fda7c9a into main Nov 21, 2026
28 checks passed
@catinspace-au
catinspace-au deleted the fix/replay-restamp-fortinet branch November 21, 2026 03:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant