AGPLv3 if that interests you: https://github.com/ddosify/alaz/blob/v0.1.3/LICENSE
Does the AGPL prevent anyone from running this on their own server for themselves (or not, since the source is provided by ddosify)?
Show HN: Alaz: Open-Source, Self-Hosted, eBPF-Based K8s Monitoring
11–20 of 28 posts
Re: Show HN: Alaz: Open-Source, Self-Hosted, eBPF-Based K8s Monitoring
#12Re: Show HN: Alaz: Open-Source, Self-Hosted, eBPF-Based K8s Monitoring
#13[flagged]
Re: Show HN: Alaz: Open-Source, Self-Hosted, eBPF-Based K8s Monitoring
#14Re: Show HN: Alaz: Open-Source, Self-Hosted, eBPF-Based K8s Monitoring
#15Re: Show HN: Alaz: Open-Source, Self-Hosted, eBPF-Based K8s Monitoring
#16Re: Show HN: Alaz: Open-Source, Self-Hosted, eBPF-Based K8s Monitoring
#17The eBPF-mode of innovation is pretty exciting, truly a fresh lens to building software. I'm also following Akita Software - the company building an eBPF paradigm of monitoring.
Re: Show HN: Alaz: Open-Source, Self-Hosted, eBPF-Based K8s Monitoring
#18Re: Show HN: Alaz: Open-Source, Self-Hosted, eBPF-Based K8s Monitoring
#19I know eBPF is the latest coolest thing on the block, but sometimes I just don't get it.
There have been database and system tools to detect zombie services and underperforming queries since time immemorial.
If people do not have the technical competence (or are frankly, just too lazy) to make use of the tools available to them already, why is some random eBPF tool suddenly going to fix it ?
Re: Show HN: Alaz: Open-Source, Self-Hosted, eBPF-Based K8s Monitoring
#20> Detect zombie services and underperforming SQL queries I know eBPF is the latest coolest thing on the block, but sometimes I just don't get it. There have been database and system tools to detect zombie services and underperforming queries since time immemorial. If people do not have the technical competence (or are frankly, just too lazy) to make use of the tools available to them already, why is some random eBPF…
as you mentioned "there have been......tools", there is always a tool best suited for a specific job, but it doesn't mean you need all the capabilities of that tool all the time. Too many tools lead to huge fragmentation inside the organisation to support multitude of tools
So why not have something one layer below your stack (kernel level) which can do good enough job to monitor almost everything you have. Its not only about if eBPF is cool, it is just reducing the fragmentation by going level below and extracting more info with a single suite of tools.