Feature Request: filter blocklist-import

[hanjo]

Hi,

I'm using blocklist-import. When I set this up, I did not fully understand how it works. Only later I found out, that it works by adding a huge number of decisions (80k+ in my case) to CrowdSec. CrowdSec itself does not seem to bother much, everything seems to be working smoothly. Only catch is that running cscli decisions list will blow your terminal.

When using the manager, the website becomes hard to use, for example: the dasboard takes a long time to load, the alerts are overwhelming and the decisions you can just forget, because there are so many (I'm aware of the "Origin" filter, but that does not allow you to just filter the blocklist-import - and it still requires the backend to process all of those decisions).

It'd be great to have some way of filtering the "blocklist-import" source at the LAPI level, to be able to use the two projects together 🙂

Thanks for looking into this!

[hhftechnology]

I had safe guard for this but I got feedback that we don't need safe guards . So remove them to unlimited entries. Crowdsec container is optimised keeping go code in mind but the problem comes with vite and most users have vps servers under 2gb ram and that creates an issue with the burst of ram needs.

[hanjo]

Yeah, same for me, I think I have 4GB of RAM though, but the issue is still the same. Therefore my suggestion to filter early, i.e. before all of the irrelevant stuff reaches the manager.

[hhftechnology]

@hanjo did the necessary changes. let me know if its works