1322d42549
Previously, the scaler was scaling up and down independently. Because when scaling up/down, Kafka rebalances the topic, temporarily, we get scale down requests and the rate limiter won't stop them as it is independant from the scale up rate limiter. Instead, the rate limit for increase acts as a gracetime where everything is ignored, then between that and the rate limit for decrease, we only consider increasing the number of workers, past that, we scaling down as long as we have a majority of scale down requests (compared to steady ones). Fix #2080 (hopefully)
Akvorado: flow collector, enricher and visualizer · 
This program receives flows (currently NetFlow/IPFIX and sFlow), enriches them with interface names (using SNMP), geo information (using IPinfo.io), and exports them to ClickHouse. It also exposes a web interface to browse the collected data.
Akvorado is developed by Free, a French ISP, and is licensed under the AGPLv3 license.
A demo site using fake data and running the latest stable version is
available on demo.akvorado.net. It is the
direct result of running docker compose up on a fresh checkout but
flow ports are not accessible (you cannot send your own flows). Please,
be gentle with this resource. The demo site also enables you to browse
the documentation for the current version
(the one in docs/ is for the next version).
By default, Akvorado is using IPinfo databases for geolocation data.
A Grafana plugin is available.
Caution
Be sure to always read the changelog before upgrading.
Getting help
The first step is to read the documentation:
- the introduction
- the configuration guide
- the troubleshooting guide
If you still need help, you can use the discussions. Be sure to explain what you tried to solve your problem. Enclose code using triple backticks:
```
# akvorado version | head -2
akvorado v1.11.2
Built with: go1.23.2 X:loopvar
```