-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove parsed timestamps from suricata events #10336
Conversation
These dates fail to parse after recent changes in Elasticsearch for date formatting, see elastic/elasticsearch#36363 Information is still stored in parsed ECS fields.
Pinging @elastic/secops |
} | ||
} | ||
, {"remove": | ||
{"field": "suricata.eve.flow.end" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be used for event.end
? @timestamp
is used for that now.
@@ -53,7 +53,6 @@ | |||
"suricata.eve.flow.bytes_toserver": 347, | |||
"suricata.eve.flow.pkts_toclient": 3, | |||
"suricata.eve.flow.pkts_toserver": 4, | |||
"suricata.eve.flow.start": "2018-10-03T14:42:44.613469+0000", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't removed these fields from fields.yml
in case we want to reserve them to be used in the future. Happy to remove them in any case if we decide to go on this way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, merging by now to get CI green. |
@ruflin yes, my plan was to start today with the aliases 👍 |
These timestamps fail to parse after recent changes in Elasticsearch for date
formatting, see elastic/elasticsearch#36363
Information is still stored in parsed ECS fields.