MikroTik Responded to My Events Script Concept
mikrotik-events-script-new-abroach
mikrotik-events-script-new-abroach
One of the things I am most proud of in my journey with MikroTik is seeing an idea I proposed earlier — the Events Script concept — become increasingly aligned with the capabilities being introduced into RouterOS.
The concept is straightforward: instead of relying on scheduled scripts that run periodically, scripts can be triggered automatically when a specific event occurs.
Starting with RouterOS v7.25, MikroTik introduced a new logging target:
/system logging action
target=script
This allows log events to be directed to a script, enabling an event-driven workflow:
Log Event → Script → Action
This is very close to the core idea behind the Events Script approach I have been developing.
What makes this particularly interesting to me is not just the addition of:
target=script
but what it enables: moving RouterOS toward a more event-driven automation model, rather than relying primarily on scheduled scripts.
It is always rewarding to see an idea evolve from a concept into something that can be implemented within RouterOS.
Thank you to the MikroTik team for continuously improving RouterOS and for listening to the needs and ideas of its community and developers.
I believe this new capability will open the door to many powerful automation possibilities in MikroTik.