Skip to content
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.

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

fix: fix logger output #79

Merged
merged 4 commits into from
Oct 5, 2023
Merged

fix: fix logger output #79

merged 4 commits into from
Oct 5, 2023

Conversation

tomMoulard
Copy link
Owner

No description provided.

@tomMoulard tomMoulard added the kind/bug/fix a bug fix label Oct 5, 2023
@tomMoulard tomMoulard merged commit e2716ec into main Oct 5, 2023
6 checks passed
@tomMoulard tomMoulard deleted the fix/logger branch October 5, 2023 10:54
@dberardo-com
Copy link

may i ask why the README was completely rewritten from v0.6.6 ? i did find the previous version of the README more informative, also when it came to the log level.

also a question: is it possible to have the information about which IPs have been banned in the INFO log level? i believe DEBUG is too verbose, but INFO is not adding any real value compared to NONE, so perhaps would be better to output only the BAN and UNBAN events in the INFO level as well.

also IMO it would be nice if the plugin was outputting some stats info from times to times, something like "[jail-name] currently 120 IPs banned". Where jail-name would be the name of the ingress / ingressRoute that caused the ban.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug/fix a bug fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants