LOG show to much info ver 7.14.3

My logs show to much info. Only last 20 minutes are there and all 1000 slots are full. Basicaly every few seconds new info is added. I never dealed with system/logging so i dont want to make things worse.

Can you provide me with info how:

  1. Make logging like it used to be in version 7.13.3 and older? I mean only important data will be shown (signal lose, dhcp lease change, etc.)
  2. If not possible should i upgrade to 7.15RC if there is it change how info behave or move back to 7:13.3? I want to avoid any unexpected problems by downgrade (like remote wireguards suicide)
  3. Easies setup to store log info in USB? Seems like it is time to store all info to troubleshoot

picture of what info is logged
Mikrotik LOG problem.png

show your logging settings

Simply add !debug to your personalized log rule.


That’s not true, for sure.
The default rules do not make “debug” logs, so someone, probably you, added “routing” to the logs, without the foresight of also putting !debug.

I'm not saying your statement is incorrect in this specific case but remember early 7.14 (I think) where all of a sudden wireguard and DHCP debug info appeared in log files without anyone touching those settings ?
So it can appear on its own, if it's a bug.

You have a point, one friend helped me with Wireguard flood so called him and he stated "I simply added !wireguard in logging". Based on baragoon suggestion i did export and discovered: /system logging add topics=!wireguard

after i remove it, debug info will stop but back to home vpn flood will emerge.
So i added !debug and !wireguard in expectation it will stop both. > /system logging add topics=!wireguard add topics=!debug

Well debug is still there so it is kinda pointless...


When roll to back to original (removing !wireguard and !debug)...

Seems like removing back to home connection is only way to deal with this, there is no way to change dynamic setup of this service.

I should stayed on 7.13.3 where everything worked normally. This new behavior is so weird for SOHO users.
Well... at last i learned something new today.

you must alter the original info adding in that !wireguard, not create another log with only !wireguard…

If you create !wireguard entry, all except wireguard are logged, so debug, calc, and other frills are logged.

paste that on terminal to revert logging system to default, with info/wiregard logging disabled:
/system logging action
remove [find where default=no]
set 0 memory-lines=1000 memory-stop-on-full=no name=memory target=memory
set 1 disk-file-count=2 disk-file-name=/log disk-lines-per-file=1000 disk-stop-on-full=no name=disk target=disk
set 2 name=echo remember=yes target=echo
set 3 bsd-syslog=no name=remote remote=0.0.0.0 remote-port=514 src-address=0.0.0.0 syslog-facility=daemon syslog-severity=auto syslog-time-format=bsd-syslog target=remote

/system logging
remove [find where default=no]
set 0 action=memory disabled=no prefix=“” topics=info,!wireguard
set 1 action=memory disabled=no prefix=“” topics=error
set 2 action=memory disabled=no prefix=“” topics=warning
set 3 action=echo disabled=no prefix=“” topics=critical

Thanks a lot! It is exactly what i wanted. I put there the winbox way how to do it for another SOHO users.
Also worth noting is it is NOT possible via wireguard app on phone because it is lacking ability to put “!” before wireguard.
This is the way.png