MikroTik

In the logging actions, you could make a "run script" action (similar to dhcp-client script) that has built-in variables with an array of topics and the message. Then we could choose when and where to send the logs using the RouterOS scripting language. Sending messages to other logging actions would be good, maybe also custom logging topics could help.

I was inspired by a recent reddit post about their prometheus server logging in repeatedly, clogging up the logs, and realized I have the same problem with my provisioning server logging in via ssh to change the snmp location to the dhcp snooping circuit id.

Thanks!

ahh I love when they suggest ways to block the router even more in the event of a DDoS attack... and even if it is misconfigured...

I would also like this.
Hopefully if you don't use the new features, it's would be the same as it is now.