Feature request (:log backwards compatibility)

RouterOS General
1

We have many scripts on 2.8, which send something to syslog.

On 2.8, the syntax is:

:log message=<message>

But on 2.9, it is:

:log <topic> <message>

For backwards compatibility, would it be possable to add an optional message= parameter to 2.9’s :log command?
Which, if invoked, would provide an implicit ?

I’m not complaining about the new logging system, it’s great. Just a minor script compatibility issue.

Our migration from 2.8 to 2.9 is going to take quite some time, and not having to maintain two seperate sets of scripts would be nice.

The only other script compatibility issue I have run into so far is 2.9s lack of :incr and :decr, but :set x ($x + 1) or :set x ($x - 1) seems to work on both, so that is far less bothersome.

Thanks,
–Eric

2

rc4

this new :log command doesn’t seem to work 100%:

[admin@mikroHome] system script> :log info test
[admin@mikroHome] system script> :log error test
[admin@mikroHome] system script> :log warning test
[admin@mikroHome] system script> :log script test
input does not match any value of topic
[admin@mikroHome] system script> :log critical test
input does not match any value of topic

Trying to log to a newly created topic called ‘script’ and it doesn’t recognize it. Also the built-in critical is not recognized.

Sam

3 
/system logging add topics=script action=memory
4

I had already done that… that’s why I reported it as a bug.

[admin@mikroHome] system logging> add topics=script action=memory
[admin@mikroHome] system logging> :log script test
input does not match any value of topic

PS. You are allowed to add many entries with the same topic name, which I don’t think should be allowed.

Sam