Merged
Conversation
… and troubleshooting examples
…fication and troubleshooting
…ions for flow log analysis
…and insights on flow log utility for network visibility
…og shipping to DataDog
…s for TCP, UDP, and ICMP connections
…r flow log analysis
…tails, and examples for flow log entries
…rity for peer-to-host and peer-to-subnet connection scenarios
…ta volume measurement
braginini
requested changes
Mar 21, 2025
Comment on lines
+3
to
+9
| NetBird’s **Traffic Events** feature provides a high-level view of traffic flows between network peers and resources. | ||
| It captures connection events on the client (peer) side – for example, when `Peer A` connects to `Peer B` – | ||
| allowing administrators to observe how devices communicate across the NetBird network. | ||
| The primary purpose of flow logging is to help network admins monitor network activity, | ||
| detect unusual or unauthorized connections, and troubleshoot connectivity issues in their NetBird mesh VPN. | ||
| Unlike packet capture, **Traffic Events** record metadata about the traffic (addresses, ports, timestamps, etc.) rather than the contents, | ||
| preserving privacy while still giving useful insight. |
Contributor
There was a problem hiding this comment.
It is not really about the mesh network. The user will have an impression that we support it on for p2p. We need to emphasise both cases: p2p and access to internal resources (maybe even crosslinking to Resources in the networks feature doc). I'd also emphasise more user to resource as this is the most common case for business
braginini
reviewed
Mar 21, 2025
lixmal
reviewed
Mar 21, 2025
| Userspace mode may introduce slightly higher CPU usage or latency since packets are handled in the application layer rather than the kernel, | ||
| but it ensures compatibility across all environments. | ||
|
|
||
| **[CHECK] We need to explain what's the how the Traffic Events differ in kernel mode vs userspace mode.** |
Contributor
There was a problem hiding this comment.
There are a few limitations currently, but I don't know if we need to document them right now. If we don't, I'd remove the whole section
Co-authored-by: Viktor Liu <17948409+lixmal@users.noreply.github.com>
Co-authored-by: Viktor Liu <17948409+lixmal@users.noreply.github.com>
Co-authored-by: Viktor Liu <17948409+lixmal@users.noreply.github.com>
Co-authored-by: Viktor Liu <17948409+lixmal@users.noreply.github.com>
Co-authored-by: Viktor Liu <17948409+lixmal@users.noreply.github.com>
Co-authored-by: Viktor Liu <17948409+lixmal@users.noreply.github.com>
Co-authored-by: Viktor Liu <17948409+lixmal@users.noreply.github.com>
…edundant peer-to-peer log entry explanations
…in NetFlow documentation
…le netflow page from navigation
mlsmaycon
approved these changes
Mar 23, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
No description provided.