Modify zeek's logstash pipeline to drop event from logs name that con… #221
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tain date like conn.2020_01_16_14_00_00.log
|
Thanks! It looks like at some point Zeek changed from using dashes underscores. I'm going to cherry-pick your change into my upstream development fork rather than merging it here directly, I'll reference this PR number for documentation. |
mmguero
added a commit
to mmguero-dev/Malcolm
that referenced
this pull request
Oct 20, 2022
…tain date like conn.2020_01_16_14_00_00.log Thanks to @rsatrio, see cisagov#221. Will be included in v6.4.1 release.
|
Closing this pull request as I've pulled your change into my upstream development repo (see mmguero-dev/Malcolm@c8f7303). It should now handle |
|
See idaholab#121 |
mmguero
added a commit
to idaholab/Malcolm
that referenced
this pull request
Nov 3, 2022
…tain date like conn.2020_01_16_14_00_00.log Thanks to @rsatrio, see cisagov#221. Will be included in v6.4.1 release.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Zeek sometimes generate logs like conn.2020_01_16_14_00_00.log. It will makes a lot of mess because it will generate custom field also like [zeek][conn.2020_01_16_14_00_00][column10] and so on. The current logstash pipeline configuration has handled it for logs name like conn.2020-01-16-14-00-00.log.
🗣 Description
Adding the if condition in Zeek's logstash pipeline to drop log with name pattern like conn.2020_01_16_14_00_00.log.
💭 Motivation and context
Because right now if the log name pattern like "conn.2020_01_16_14_00_00.log" occured, it will messed up the field name in Opensearch
🧪 Testing
Build the logstash container locally without failed. And when it integrate with Zeek, the logs still ingest properly.
✅ Pre-approval checklist
✅ Pre-merge checklist
✅ Post-merge checklist