Skip to content

Fix typo in README regarding performance page #426

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.

Sign up for GitHub

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

Closed
KaSaNaa wants to merge 2 commits into from
Closed

Fix typo in README regarding performance page #426

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1c0c796
Fix typo in README regarding performance page
KaSaNaa Sep 19, 2025
f8f5cf8
Add user story for KaSaNaa using GoFlow2
KaSaNaa Sep 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@ For instance, to create 4 parallel sockets of sFlow and one of NetFlow, you can
$ ./goflow2 -listen 'sflow://:6343?count=4,netflow://:2055'
```

More information about workers and resource usage is avaialble on the [Performance page](/docs/performance.md).
More information about workers and resource usage is available on the [Performance page](/docs/performance.md).

### Docker

Expand Down Expand Up @@ -240,6 +240,11 @@ There are assumptions on how many records and list items a sample can have (eg:
## User stories

Are you using GoFlow2 in production at scale? Add yourself here!
### [KaSaNaa](https://github.com/KaSaNaa)
<img src="https://github.com/KaSaNaa.png" height=50 width=50/>

- We run a large distributed network where visibility into traffic patterns is critical. Traditional NetFlow collectors struggled to keep up with the volume and lacked flexibility in exporting the data to modern analytics pipelines. We adopted GoFlow2 as our flow collector because it integrates natively with Kafka and outputs flows in JSON, making it easy to feed into ClickHouse for high-performance analytics.
- At peak, our infrastructure ingests millions of flow records per second across multiple data centers. GoFlow2’s lightweight design and parallel worker model allow us to scale horizontally with little overhead. We configured multiple Kafka partitions to match GoFlow2 workers, ensuring balanced throughput without bottlenecks.

### Contributions

Expand Down