Skip to content
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

Merged
merged 1 commit into from
Jan 25, 2019

Conversation

jsoriano
Copy link
Member

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.

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.
@jsoriano jsoriano added module discuss Issue needs further discussion. review Filebeat Filebeat labels Jan 25, 2019
@jsoriano jsoriano self-assigned this Jan 25, 2019
@jsoriano jsoriano requested a review from a team as a code owner January 25, 2019 11:04
@elasticmachine
Copy link
Collaborator

Pinging @elastic/secops

}
}
, {"remove":
{"field": "suricata.eve.flow.end"
Copy link
Member Author

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",
Copy link
Member Author

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.

Copy link
Contributor

@ruflin ruflin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Gets our CI back to green which is most important at the moment.

@adriansr @cwurm Can you please follow up here. If I remember correctly the plan is to introduce alias for the ECS duplicated fields?

@jsoriano
Copy link
Member Author

jsoriano commented Jan 25, 2019

Ok, merging by now to get CI green.

@jsoriano jsoriano merged commit 302acf5 into elastic:master Jan 25, 2019
@jsoriano jsoriano deleted the suricata-date-formats branch January 25, 2019 12:11
@adriansr
Copy link
Contributor

@ruflin yes, my plan was to start today with the aliases 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Issue needs further discussion. Filebeat Filebeat module review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants