But that wouldn't get the buzz and attention of the latest techno fanboy circle jerk.
I agree completely that these things should use open standards first, and possibly support closed/app specific protocols/Apis second, if said app doesn't support an open standard.
But that doesn't work for a lot of devs these days, because it's not an instant popularity contest winner
Thanks! I know there are better protocols out there to handle this sort of thing, but I'm already using Slack and used this protocol because it fit my own needs and it requires less dependencies to fit those needs.
On my very insignificant server, fail2ban has banned around 400 IP addresses in 2016, so far. What actionable information would I have received by having a disruptive notification about it?
I agree, what I do instead is track the number of currently banned with nagios and if it goes over a specific threshold I get a warning. With PNP4Nagios you also get a nice graph over time.
13 comments
[ 2.7 ms ] story [ 41.8 ms ] threadI agree completely that these things should use open standards first, and possibly support closed/app specific protocols/Apis second, if said app doesn't support an open standard.
But that doesn't work for a lot of devs these days, because it's not an instant popularity contest winner
On this topic does anyone know if there is something simple that will tell you if a new IP address logs in or a new process is started?
Surely just feed all logs into Splunk or Logstash or similar? Most monitoring systems have plugins to alert via Slack now.