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

Zeek log files that have been renamed and are in the process of moving not caught correctly by Logstash #121

Closed
mmguero opened this issue Oct 20, 2022 · 0 comments
Assignees
Labels
bug Something isn't working logstash Relating to Malcolm's use of Logstash regression It worked at one point...

Comments

@mmguero
Copy link
Collaborator

mmguero commented Oct 20, 2022

Thanks to @rsatrio, see cisagov#221.

Sometimes Zeek renames a file before moving it, and Filebeat/Logstash can catch it before it's moved but after it's renamed. These files have a datestamp in them, which used to be like conn.2020-01-16-14-00-00.log but has at some point more recently been changed to conn.2020_01_16_14_00_00.log. I've updated the parsing to handle both (see mmguero-dev@c8f7303). It should now handle _ (underscore), - (dash), : (colon) or `` (no character) as separators for the date.

@mmguero mmguero added bug Something isn't working logstash Relating to Malcolm's use of Logstash regression It worked at one point... labels Oct 20, 2022
@mmguero mmguero self-assigned this Oct 20, 2022
@mmguero mmguero added this to Malcolm Oct 20, 2022
@mmguero mmguero closed this as completed Oct 20, 2022
@mmguero mmguero moved this to Done in Malcolm Oct 20, 2022
@mmguero mmguero moved this from Done to Released in Malcolm Nov 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working logstash Relating to Malcolm's use of Logstash regression It worked at one point...
Projects
Status: Released
Development

No branches or pull requests

1 participant