WE have ran the dude 4.0b3 for quite some time to monitor our network. We recently deployed a VM with CHR 6.39.2 and have migrated the Dude to this instance and have de-commissioned the old 4.0b3 server. One thing that I notice is in the 6.39.2 instance, there is only one log file built in now. Before there used to be 4 log files (syslog, event, etc., etc.) it also appears that I have no way to add any custom log files, or to adjust the retention settings of the log files. Does anyone have any information on how I can fix this,.

Thanks

apiel1,

As you, we also have same issue with Dude v6.

I have contacted Mikrotik support about this. Their reply was that they have plans to improve syslog, but how and when I don't know.

Thank you!

At least something... At the moment you can save in system logging the dude event into separate file to get the dude log saved.
I am also waiting for returning the syslog functionality known in 4b3 to 6.x.

Thanks for the replies. I will eagerly await these enhancements in V6

At the moment, we also send all Dude v6 logs to remote syslog server where we have separate display for them and colorise them with corresponding rules.

Thank you!

It would be nice not to have to do this. The logging at the moment within the dude is very unmanageable.

I join others for separate files syslog facility.. Logs cannot be saved now after reboot as well

maxkrok,

As a workaround, to save logs into a file on ROS, we can: Thank you!

I don't see a retention policy ether. Was this remove on the new version and when can we get it back?

manuelm,

What do you mean by retention policy?

In Dude v6 a ROS logging system is used and we can't configure multiple logs with their policy.

One workaround is described above.

Thank you!

Waiting for the "old style" syslog...

Me too.

I also need this. Hope it comes out soon

+1 for the old Syslog settings, and bring back the little Flags as in 6.36.4 ... Please.

Why is this thread marked, "Solved"? As far as I can tell, dude logging is still a mess.