dude 4.0beta3 → click logs on tree (left side) → plus/add button → make new log for a router
dude 4.0beta3 → settings button at the top → Syslog tab → plus/add button → … "
add src address
action = accept
notification = log to syslog
click the little single dot button and set the target log to the log you just made for rb1
"
winbox to router and set up remote sys log
OK this works great but now lets repeat the steps for our next router…
result → when you go add your second router in the settings → syslog and change the target log all the sudden all the rules send all logs to the one you just added.
:/!!!

Am i doing this wrong or is it broken?
The wiki on syslog has you point everything at the syslog that is already in place. I did find how to customize this functionality.
You can set up different log files in the log area.
dude → logs(left tree) → plus/add button → name it appropriately.
Now create your custom notification.
dude → notifications(left tree) → plus/add button → type=log, Target Log=
Now have The Dude send the appropriate incoming syslog data to the correct log file.
dude → settings (button top left) → syslog(tab at top) → plus/add button → src address=<server’s-IP-to-collect-sysData’s-from>, action=accept, notification=
OK their we go now all Sys Log data coming from that server/routers ip is now going to our own custom log file.
Repeat the three steps for your next server/router and now all your logging Dada will be organized.
You can also set up the “Start New File” attribute when making each log. This will create a new file how ever often you like. I set it to one day then set up a cron to archive
.