I will be honest with y'all, whenever someone coming with add-on sw launched into kernel I get anxiety attack as a platform engineer. This is very fragile matters both for performance as well as security. I see ddosify-alaz leverages prometheus node exporter for metrics collection which is awesome, using ebpf for service mash-map is promising but as I said I would prefer this part to be configurable to be not deployed if sre/platform teams do not want ebpf but only metric exporter capabilities to feed in to DDosify observability platform. Overall: Great Open source sw launch, please make it flexible for configuration. Cheers!
Thank you for providing us with your valuable feedback. At the moment, the metrics and eBPF sections are configurable but not yet documented. However, we are working on adding this information to our documentation as soon as possible. If you wish to disable the eBPF component and use only metrics instead, you can add the environment variable 'EBPF_ENABLED=false' to your alaz.yaml file.
Alaz utilizes minimal resources for both network and resource collection. CPU and Memory resources are limited in the K8s configuration file.
Alaz is still in its early stages of development and it's being improved based on developer feedback. Thanks again for providing us with your valuable input.
