It makes far more sense to have this under `Use Cases`, IMO.
It's the kind of information a user would like to have upfront and not as an afterthought. Furthermore, comparisons between the two options are typically made far sooner in other projects.
May also consider changing the dir that the `.md` file is in, which also change the URL to `/selfhosted/` from to possibly `how-to`, though that's probably beyond the scope of what I can pull off from my cellphone in bed. :- ) Edits of course welcome re that.
* update slack url and twitter
use a dedicated url for slack, allowing update in a single place
rename Twitter references to X
* rollback Install NetBird title in navigation menu
* Update NavigationDocs.jsx to be more clear about installing the NetBird client
I've seen several people get very confused about setting up NetBird in terms of self-hosting when this is the first thing they see on the docs. Reminds me of the problem with 'Plex Media Server' versus 'Plex' with a lot of people installing the server on their computer instead of the client software.
* Update installation.mdx
* Update getting-started.mdx
* fix: drop the note about requiring Access Policy for to the Routing Peer
* feat: add network selection commands note
* feat: DNS debugging updates
* feat: add note about changing accounts for the machine/client
* Add Network Flow Logs documentation and navigation entry
* Enhance Network Flow Logs documentation with updated retention policy and troubleshooting examples
* Enhance NetFlow documentation with detailed examples for traffic verification and troubleshooting
* Update section title in NetFlow documentation for clarity
* Enhance NetFlow documentation with additional examples and clarifications for flow log analysis
* Enhance NetFlow documentation with detailed troubleshooting guidance and insights on flow log utility for network visibility
* Enhance NetFlow documentation with updates on log retention policy, log shipping to DataDog
* Update NetFlow documentation to clarify use cases and enhance examples for TCP, UDP, and ICMP connections
* Enhance NetFlow documentation with new examples and clarifications for flow log analysis
* Enhance NetFlow documentation with improved formatting, additional details, and examples for flow log entries
* Enhance NetFlow documentation with additional images and improved clarity for peer-to-host and peer-to-subnet connection scenarios
* Update NetFlow documentation to include flow direction and clarify data volume measurement
* fix doc
* Update src/pages/how-to/netflow.mdx
Co-authored-by: Viktor Liu <17948409+lixmal@users.noreply.github.com>
* Update src/pages/how-to/netflow.mdx
Co-authored-by: Viktor Liu <17948409+lixmal@users.noreply.github.com>
* Update src/pages/how-to/netflow.mdx
Co-authored-by: Viktor Liu <17948409+lixmal@users.noreply.github.com>
* Update src/pages/how-to/netflow.mdx
Co-authored-by: Viktor Liu <17948409+lixmal@users.noreply.github.com>
* Update src/pages/how-to/netflow.mdx
Co-authored-by: Viktor Liu <17948409+lixmal@users.noreply.github.com>
* Update src/pages/how-to/netflow.mdx
Co-authored-by: Viktor Liu <17948409+lixmal@users.noreply.github.com>
* Update src/pages/how-to/netflow.mdx
Co-authored-by: Viktor Liu <17948409+lixmal@users.noreply.github.com>
* Clarify data volume measurement in NetFlow documentation and remove redundant peer-to-peer log entry explanations
* Remove redundant explanations in NetFlow documentation for clarity
* Replace instances of "flow log" with "traffic event" for consistency in NetFlow documentation
* add update image to reflect correct info and added retention info.
* add more information to the traffic events page and temporarily disable netflow page from navigation
* correct wording
---------
Co-authored-by: Viktor Liu <17948409+lixmal@users.noreply.github.com>
Co-authored-by: Maycon Santos <mlsmaycon@gmail.com>
