Add Filebeat Top-N Flows dashboard #10180
Merged
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
This is dashboard for investigating the Top-N network flows. The search pattern is set to look at `event.action: network_flow` which is what the Filebeat netflow input uses. There are controls for selecting the flow direction (if provided by the netflow exporter) and the flow locality (public = at least one side is a public IP, or private = both sides are private IPs). The domain column in the tables will only be populated if the data is enriched with source.domain or destination.domain. Like if a reverse or passive DNS enrichment is performed.
|
Pinging @elastic/secops |
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.
This is dashboard for investigating the Top-N network flows. The search pattern is set to
look at
event.action: network_flowwhich is what the Filebeat netflow input uses. Thereare controls for selecting the flow direction (if provided by the netflow exporter) and the
flow locality (public = at least one side is a public IP, or private = both sides are private IPs).
The domain column in the tables will only be populated if the data is enriched with
source.domain or destination.domain. Like if a reverse or passive DNS enrichment is
performed.
(Flow data simulated via softflowd and a pcap file so the flow durations are all 0.)