-
Notifications
You must be signed in to change notification settings - Fork 419
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
New network fields #43
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -27,6 +27,22 @@ | |
Host IP address when the source IP address is the proxy. | ||
example: 192.1.1.2 | ||
|
||
- name: session_id | ||
type: keyword | ||
description: > | ||
This is the session ID or connection ID, | ||
a unique identifier for the session /connection. | ||
Bro conn.log uid field gets mapped here. | ||
example: 00beeff00d1234 | ||
|
||
- name: virtual_ip | ||
type: ip | ||
description: > | ||
The virtual IP associated with a session or connection. | ||
Useful when load balancers, firewalls, and routers use a | ||
virtual IP to "advertise" a service. | ||
example: 192.168.1.1 | ||
|
||
# Metrics | ||
- name: inbound.bytes | ||
type: long | ||
|
@@ -48,3 +64,13 @@ | |
description: > | ||
Network outbound packets. | ||
example: 12 | ||
- name: total.bytes | ||
type: long | ||
description: > | ||
Network Total bytes: Usually sum (inbound.bytes, outbound.bytes) | ||
example: 368 | ||
- name: total.packets | ||
type: long | ||
description: > | ||
Network Total packets: Usually sum (inbound.packets, outbound.packets) | ||
example: 24 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would phrase both of these more directly, e.g. "The sum of inbound.packets + outbound.packets", same for bytes. |
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
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.
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.
Reading in this field and the next one about connection, I wonder if we should introduce `connection.* as mentioned in an other thread instead of uptting it under network.
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.
Sorry @ruflin I forgot to reply before closing this PR out for splitting. Are you just talking about a name change i.e. s/network/connection? The network.* field set is intended to pick up flow and connection-based fields, and also network events that are not flow/connection related. I think this requires a bit more thought before making a decision.
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.
I'm actually thinking if we could use a network and a connection prefix. I think a big chunk of the info we have right now in
network
is in the right place, but there a things likeforwarded_ip
which probably fit better into connection and also these fields here.Definitively needs more discussions, just an idea.