Page 1 of 1
Feature request: tool/fetch new property - no-log
Posted: Mon Jun 05, 2017 10:01 am
by bmatic
I did my own ddns no-ip script, which does http fetch of an html file with my public ip address, and I noticed that fetch tool logs every download, so my log is cluttured with unnecessary fetch logs.
So my feature request is that fetch tool have additional property, like for example: no-log.
Re: Feature request: tool/fetch new property - no-log
Posted: Sun Oct 22, 2017 1:08 pm
by emkac
I have the same issue.
Script for no-ip updating is working fine, but this command always create log entry.
/tool fetch mode=http address="checkip.dyndns.org" src-path="/" dst-path="/dyndns.checkip.html"
log_file_fetch.png
Is there any possibility how to disable logging for "fetch"?
OS version:6.39.2
Re: Feature request: tool/fetch new property - no-log
Posted: Sat Apr 07, 2018 1:10 pm
by Boardy
same for me, please add verbose flag...
Re: Feature request: tool/fetch new property - no-log
Posted: Tue Apr 10, 2018 5:18 pm
by ivanfm
will be nice an option to log only on error.
no messages when got and 200 response, but log for connection error or different status code.
Re: Feature request: tool/fetch new property - no-log
Posted: Tue May 08, 2018 9:55 am
by bakadave
seconded!
and logging event in case of error only would be even better
Re: Feature request: tool/fetch new property - no-log
Posted: Thu Aug 16, 2018 10:09 pm
by JAza
+1.
My script needs to /tool fetch a url as an https 'get' for update the ddns service.
There is no actual file but the fetch creates a 2 byte file in the name of the url query. The file is named "?=xxx" where xxx is a mixed random string (the update token).
This file is difficult to deal with due to the '?' in the name and sometimes my script fails to delete it (mystery...).
Since I can't rename it and I can't download to my windows box a file with a ? in the name I have no idea what the 2 bytes in it are but I know I would rather be able to not create teh file in first place as I never parse it or use it so it's completely unnecessary clutter and it clutters my logs on every run.
Re: Feature request: tool/fetch new property - no-log
Posted: Thu Dec 19, 2019 10:53 pm
by eliasbats
+1
nice request
Re: Feature request: tool/fetch new property - no-log
Posted: Sat Dec 21, 2019 4:30 pm
by gotsprings
I got around this by using resolve.
I resolve my public IP address. And make that a local variable. Then I compare that variable to what I pick off IP cloud or route pref-source.
This cuts down on sending unnecessary traffic to my name server provider. And NOTHING GETS WRITTEN TO MY LOG UNTIL... I send an update to the name server.
If you provide a copy of your script...
Maybe I could show you where to plug in local variables. but here are my pieces... YOU WILL NEED TO ADD THE WORD "WAN" to your public facing interface.
i.e. ether1-WAN
Pick IP From Route
:global Stat [/ip route get [find gateway=ether1-WAN] pref-src]
Pick IP from Address
:global OnEtherSub [/ip address get [find interface~"WAN"] address]
:global OnEther [:pick $OnEtherSub 0 [:find $OnEtherSub "/"]]
Pick IP from DHCP-Client
:global OnEtherSub [/ip dhcp-client get [find interface~"WAN"] address]
:global OnEther [:pick $OnEtherSub 0 [:find $OnEtherSub "/"]]
Get Public IP from IP Cloud
:global ipCloud [/ip cloud get public-address]
Resolve your current DNS name
:global RESOLVED [:resolve something.whatever.com]
Once you have those 2 things...
Compare them.
If not = then run the part of the script that sends the update to your service.
Then you will only have a log entry when they need and do updates.
(Figured this out a few years back and have been using it since.)
Re: Feature request: tool/fetch new property - no-log
Posted: Fri Feb 21, 2020 5:26 am
by jgraue
+1
nice request
+1 for the request. im also getting log messages on each POST.
Re: Feature request: tool/fetch new property - no-log
Posted: Sun Jun 28, 2020 1:09 am
by dke
+1 for the request
Re: Feature request: tool/fetch new property - no-log
Posted: Fri Jul 17, 2020 3:26 pm
by robo9
I can't wait for this feature.
It should be easy to implement.
Fetch is used in multiple ways and should not overload logs.
Re: Feature request: tool/fetch new property - no-log
Posted: Sat Jul 18, 2020 12:17 am
by changeip
im not seeing fetch hit the logs on my scripts. whats the topics involved with the logging? maybe you have those enabled and so they are logging.
Re: Feature request: tool/fetch new property - no-log
Posted: Fri Oct 23, 2020 11:43 am
by leonix
+1
fetch should get a own log topic "fetch", so we can just disable it:
/system logging add topics=!fetch
Leo.
Re: Feature request: tool/fetch new property - no-log
Posted: Sun Oct 25, 2020 7:20 am
by furaihan
+1 i need this
Re: Feature request: tool/fetch new property - no-log
Posted: Wed Sep 01, 2021 8:27 pm
by alemoia
i really hope this can be implemented soon
Re: Feature request: tool/fetch new property - no-log
Posted: Thu Sep 02, 2021 5:05 am
by gotsprings
I explained how to get around this 2 years ago.
Read the post and pick your fix.
Re: Feature request: tool/fetch new property - no-log
Posted: Fri Nov 11, 2022 5:21 pm
by howdey57
Please can you provide a link to your "no fetch log entry" post.
Thanks
Re: Feature request: tool/fetch new property - no-log
Posted: Fri Nov 11, 2022 6:49 pm
by rextended
It's too hard scroll back???
or just turn off the logs, so there is no problem with the logs...