HELP for not LOG some value

RouterOS General
1

Hello everybody

I have a script to check and possibly update my freedns account every 5 minutes.

I would like the value not to be logged memory info fetch:file “update… etc etc” .

I would not have this value in LOG, everything else… It’s possible?

Thanks
log_freedns.JPG

2

Can anyone help me?
Thanks in advance, sorry for my bad english.

3

Firstly, there is a “Scripting” category for these posts, you should rather posts in that category.

Post your script here using the code tags so we can have a look

4

Ops, sorry for the error… Sorry, I thought the post was inherent in the “general” category rather than “script”

this is my script:

/system script
add name=fetch_new owner=admin policy=\
    ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon source="/\
    tool fetch host=\"freedns.afraid.org\" url=\"https://freedns.afraid.org/dy\
    namic/update.php\\\?WVA*******************************************NTY=\"\r\
    \n\r\
    \n"

add interval=5m name=fetch_new on-event=fetch_new policy=\
    ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon \
    start-date=feb/05/2018 start-time=17:10:00

Thank you so mutch…

5

I thought maybe it was added to log via script, in this case, it is not.

Maybe try adding “not script” i.e. !script to the default “info” topic under system logging

6

Thanks for replay and for the help.

I’ve disable ALL info memory logging, but in this case I’ve stop to logging ALL Info…

I don’t understand if is the correct way…

Thank you.
cattura777.JPG

7

Example shows that fetch is logged under topic info. If you want to hide such messages, then you simply have to disable info topic. There is no other way.

Lets say, if we use as an example L2TP logs, then part of them is logged under info,l2tp topic. Then you can under logging rules change topic from info to info,!l2tp and then all info logs except l2tp ones will be saved.

8

It would be best when MikroTik would assign some more specific topic to this (and some other) log message.
E.g. when it would not be logged as info but as info,fetch it would be easy to block this log by adding !fetch on the info topic log, and still log other info.
Maybe do a scan of all logging and setup some more topics like this or even better add a unique topic (message code) to each and every message in the system.

9

++

The proper solution is more granular logging options, not disabling pretty much ALL logging (since info contains tons of other information) just because fetch is noisy every time you run it. It makes scripting scheduling with fetch a PITA.