-
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
[Filebeat] sync checkpoint module with Fleet integration #31076
[Filebeat] sync checkpoint module with Fleet integration #31076
Conversation
This pull request does not have a backport label. Could you fix it @andrewkroh? 🙏
NOTE: |
b2d6183
to
11a6a6a
Compare
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
The Filebeat module was missing definitions for these four fields. - checkpoint.comment - checkpoint.conn_direction - checkpoint.db_ver - checkpoint.update_status The Filebeat pipeline is setting client and server based on the source and destination. That behavior was kept. Otherwise the pipelines are the same. This commit was used: elastic/integrations@2aee5ee
cfe7fdd
to
81bbaa2
Compare
According to https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk144192, Check Point module field checkpoint.source_object should be mapped as a string type instead of integer. Syncs change from: elastic/beats@a5e6e5b Relates: elastic/beats#25124 Other changes: - use ECS `log.file.path` - add `event.original` mapping - sort fields.yml by field name This was observed while preparing elastic/beats#31076.
The same field is defined in the CEF module which also supports Check Point data.
At this point the failures appear to be caused by to the fact that Beats main branch now requires 8.3.0 ES versions for testing purposes (due to |
/test |
2 similar comments
/test |
/test |
/test |
/test |
@Mergifyio update |
✅ Branch has been successfully updated |
@@ -19,5 +19,5 @@ func init() { | |||
// AssetCheckpoint returns asset data. | |||
// This is the base64 encoded zlib format compressed contents of module/checkpoint. | |||
func AssetCheckpoint() string { |
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.
It would be a great thing to have this embedded using embed and not requiring base64 </random-thoughts>.
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.
Agree.
- add_fields: | ||
target: '' | ||
fields: | ||
ecs.version: 1.12.0 |
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.
What was this?
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.
It added ecs.version to the outgoing event. This is now being set as part of the ingest pipeline with a set
processor.
* Sync Check Point module with Fleet integration The Filebeat module was missing definitions for these four fields. - checkpoint.comment - checkpoint.conn_direction - checkpoint.db_ver - checkpoint.update_status The Filebeat pipeline is setting client and server based on the source and destination. That behavior was kept. Otherwise the pipelines are the same. This commit was used: elastic/integrations@2aee5ee * Add overwrite: true for checkpoint.update_status The same field is defined in the CEF module which also supports Check Point data.
* Sync Check Point module with Fleet integration The Filebeat module was missing definitions for these four fields. - checkpoint.comment - checkpoint.conn_direction - checkpoint.db_ver - checkpoint.update_status The Filebeat pipeline is setting client and server based on the source and destination. That behavior was kept. Otherwise the pipelines are the same. This commit was used: elastic/integrations@2aee5ee * Add overwrite: true for checkpoint.update_status The same field is defined in the CEF module which also supports Check Point data.
* Sync Check Point module with Fleet integration The Filebeat module was missing definitions for these four fields. - checkpoint.comment - checkpoint.conn_direction - checkpoint.db_ver - checkpoint.update_status The Filebeat pipeline is setting client and server based on the source and destination. That behavior was kept. Otherwise the pipelines are the same. This commit was used: elastic/integrations@2aee5ee * Add overwrite: true for checkpoint.update_status The same field is defined in the CEF module which also supports Check Point data.
What does this PR do?
This adds
network.transport
to events derived from the IANA number. It brings in the change related to elastic/integrations#2463.The Filebeat module was missing definitions for these four fields.
On difference between Fleet and Filebeat is that the Filebeat pipeline is setting
client
andserver
based on thesource
anddestination
. That behavior was kept. Another difference isevent.ingested
is required in the Filebeat version of the pipeline. Otherwise the pipelines are the same.This commit was used:
elastic/integrations@2aee5ee
Filebeat had some ~10000 test log lines, but only the first 100 are checked in test_modules.py so I removed 9900 of them.
Why is it important?
Consistency is nice.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Note to reviewers
I think it would be easier to review the diff commit by commit. And turn off whitespace for the pipeline YAML diff.
Related issues