You can do hotspot, !debug and get everything hotspot but debug. Anything you don't want under hotspot, add as a !topic.
This will only send hotspot (no debug) and not dhcp/user/other topic stuff. /system logging add action=syslog disabled=no prefix="" topics=hotspot,!debug If you don't want it in the log you have to turn off the memory for those topics. Justin On Dec 13, 2013, at 11:56 AM, ralph <[email protected]> wrote: > That's not what I understood. > Supposedly, according to Butch, you can suppress certain messages by using > the ! symbol. > I was hoping for some examples from someone who is actually doing it. > No point in filling up the Syslog server with messages I don't even > need/want. > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Scott Reed > Sent: Friday, December 13, 2013 6:09 AM > To: Mikrotik discussions > Subject: Re: [Mikrotik] Routing log messages to external syslog > > You cannot pick and choose messages. If you do Action Hotspot, you get all > the Hotspot messages. > > On 12/12/2013 11:07 PM, ralph wrote: >> Thanks. >> I have that part- it is the selection of the message sent that doesn't >> seem to work correctly. >> Could you give examples of the cli commands used to send the following >> types of messages and only those? >> No matter how I set it up it sends the wrong thing. >> >> dhcp info dhcp1 assigned 10.5.50.4 to xx:xx:xx:xx:xx:xx >> >> system info account user admin logged in from x.x.x.x via winbox >> >> hotspot info debug jdots1 (10.5.50.6) trying to log in by http-pap >> >> hotspot info debug jdots1 (10.5.50.6) logged in >> >> hotspot info debug jdots1 (10.5.50.6) logged out: idle timeout >> >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Scott Reed >> Sent: Thursday, December 12, 2013 4:35 PM >> To: Mikrotik discussions >> Subject: Re: [Mikrotik] Routing log messages to external syslog >> >> System->Logging >> Actions Tab >> Create new action >> Give it name >> Type is Remote >> Put in the address of your syslog server Put in the source address of >> the router you want syslog to see. >> Depending on your syslog server you may need to select BSD Syslog. >> >> Save that >> >> On the rules tab, create a new rule >> Choose the topic you want, such as hotspot. >> The prefix is sent to the syslog server. >> The action needs to be remote. >> >> Only actions marked remote will go to syslog. >> >> >> >> >> On 12/12/2013 4:25 PM, ralph wrote: >>> I have been working on routing hotspot system logs to a syslog server >>> >>> However the logging commands don't seem to behave like the >>> documentation suggests. Not that the documentation I found is that >>> wonderful to begin with. >>> >>> >>> >>> I'm using Winbox to access the routers. The routers are mostly R450s >>> with a couple 2011 and maybe some old 433 thrown in for good measure. >>> >>> >>> >>> Can someone help me out please? >>> >>> >>> >>> I'd like to send some of the default messages to the syslog box and >>> not have them clutter up the router inbuilt log. >>> >>> >>> >>> Some of the formats I'd like to reroute are below. I'd actually like >>> to have some of them not show in the built in log at all, if possible. >>> >>> >>> >>> dhcp info dhcp1 assigned 10.5.50.4 to xx:xx:xx:xx:xx:xx >>> >>> system info account user admin logged in from x.x.x.x via winbox >>> >>> hotspot info debug jdots1 (10.5.50.6) trying to log in by http-pap >>> >>> hotspot info debug jdots1 (10.5.50.6) logged in >>> >>> hotspot info debug jdots1 (10.5.50.6) logged out: idle timeout >>> >>> >>> >>> >>> >>> I have experimented and even tried enabling logs with the ! in front >>> of them (which I thought should suppress that particular one) but my >>> results are all over the map. >>> >>> >>> >>> >>> >>> Can someone show me the commands (either cli or winbox) to manipulate >> these? >>> I think with that help I may become dangerous enough to do the rest >>> of what I'd like to do. >>> >>> >>> >>> Thanks >>> >>> >>> >>> Ralph >>> >>> >>> >>> >>> >>> >> >> _______________________________________________ >> Mikrotik mailing list >> [email protected] >> http://mail.butchevans.com/mailman/listinfo/mikrotik >> >> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >> RouterOS >> >> >> ----- >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2014.0.4259 / Virus Database: 3658/6913 - Release Date: >> 12/12/13 >> >> > > -- > Scott Reed > Owner > NewWays Networking, LLC > Wireless Networking > Network Design, Installation and Administration Mikrotik Advanced Certified > www.nwwnet.net > (765) 855-1060 (765) 439-4253 Toll-free (855) 231-6239 > > > _______________________________________________ > Mikrotik mailing list > [email protected] > http://mail.butchevans.com/mailman/listinfo/mikrotik > > Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS > > > _______________________________________________ > Mikrotik mailing list > [email protected] > http://mail.butchevans.com/mailman/listinfo/mikrotik > > Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS _______________________________________________ Mikrotik mailing list [email protected] http://mail.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
