-
Notifications
You must be signed in to change notification settings - Fork 444
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
[Network Packet Capture] Convert Dashboards to lens, add pipeline errors and format_versions #6117
[Network Packet Capture] Convert Dashboards to lens, add pipeline errors and format_versions #6117
Conversation
Initial Draft added everything except dashboards, next commits will add them in, will keep it in draft for now |
🌐 Coverage report
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
This does not include data views yet, to fix field collisions with Cloud Securiry Posture, will look into that before merging. |
@@ -3,6 +3,11 @@ type: logs | |||
streams: | |||
- input: packet | |||
vars: | |||
- name: interface |
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.
This will be removed before merge, its to help with people testing, see PR description.
While we would have wanted this to be included, apparently packetbeat do not support different interfaces for different protocols, but it does work with pcaps.
@@ -3,6 +3,11 @@ type: logs | |||
streams: | |||
- input: packet | |||
vars: | |||
- name: interface |
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.
This will be removed before merge, its to help with people testing, see PR description.
While we would have wanted this to be included, apparently packetbeat do not support different interfaces for different protocols, but it does work with pcaps.
@@ -3,6 +3,11 @@ type: logs | |||
streams: | |||
- input: packet | |||
vars: | |||
- name: interface |
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.
This will be removed before merge, its to help with people testing, see PR description.
While we would have wanted this to be included, apparently packetbeat do not support different interfaces for different protocols, but it does work with pcaps.
@@ -3,6 +3,11 @@ type: logs | |||
streams: | |||
- input: packet | |||
vars: | |||
- name: interface |
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.
This will be removed before merge, its to help with people testing, see PR description.
While we would have wanted this to be included, apparently packetbeat do not support different interfaces for different protocols, but it does work with pcaps.
@@ -6,6 +6,11 @@ streams: | |||
description: Track Network Flows | |||
template_path: flow.yml.hbs | |||
vars: | |||
- name: interface |
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.
This will be removed before merge, its to help with people testing, see PR description.
While we would have wanted this to be included, apparently packetbeat do not support different interfaces for different protocols, but it does work with pcaps.
@@ -3,6 +3,11 @@ type: logs | |||
streams: | |||
- input: packet | |||
vars: | |||
- name: interface |
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.
This will be removed before merge, its to help with people testing, see PR description.
While we would have wanted this to be included, apparently packetbeat do not support different interfaces for different protocols, but it does work with pcaps.
@@ -3,6 +3,11 @@ type: logs | |||
streams: | |||
- input: packet | |||
vars: | |||
- name: interface |
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.
This will be removed before merge, its to help with people testing, see PR description.
While we would have wanted this to be included, apparently packetbeat do not support different interfaces for different protocols, but it does work with pcaps.
@@ -3,6 +3,11 @@ type: logs | |||
streams: | |||
- input: packet | |||
vars: | |||
- name: interface |
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.
This will be removed before merge, its to help with people testing, see PR description.
While we would have wanted this to be included, apparently packetbeat do not support different interfaces for different protocols, but it does work with pcaps.
@@ -3,6 +3,11 @@ type: logs | |||
streams: | |||
- input: packet | |||
vars: | |||
- name: interface |
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.
This will be removed before merge, its to help with people testing, see PR description.
While we would have wanted this to be included, apparently packetbeat do not support different interfaces for different protocols, but it does work with pcaps.
@@ -3,6 +3,11 @@ type: logs | |||
streams: | |||
- input: packet | |||
vars: | |||
- name: interface |
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.
This will be removed before merge, its to help with people testing, see PR description.
While we would have wanted this to be included, apparently packetbeat do not support different interfaces for different protocols, but it does work with pcaps.
Added new and better screenshots, Tests are most likely failing due to the test specific commit I added in, it will go back to green once its removed (once people have had the oppertunity to test) |
Seems like some of the filters even references dataviews, will have to re-add all filters to remove any reference to |
Package network_traffic - 1.16.0 containing this change is available at https://epr.elastic.co/search?package=network_traffic |
What does this PR do?
This is part of a bigger cleanup that relates to https://github.com/elastic/security-team/issues/5910.
The tasks, when applicable was:
Dashboard changes:
Checklist
changelog.yml
file.Testing
Use commit 70d11d1 for testing
I have temporarily added interface options to each datastream to help with testing, it will be removed before merging. The steps to test this is:
_dev/deploy/docker/pcaps/*
folder to~/.elastic-package/tmp/service_logs/*
One note, is that since we have to use a direct reference to the pcap files, if you want to ingest more test-data, you would have to manually update the agent policy, and change the path to another pcap, save, wait for the ingest to finish, then change it again etc.
EDIT: Updated step 1, to make it more specific.
Test policy:
Related issues
Screenshots (Somewhat limited due to test data available, but working fine).
Overview
Mysql:
NFS:
PGSQL:
Thrift:
Cassandra:
DHCP:
DNS:
HTTP:
MongoDB: