Community discussions

MikroTik App
 
iam8up
Member
Member
Topic Author
Posts: 333
Joined: Sun Oct 28, 2007 10:58 pm
Location: Troy, OH
Contact:

Logging to Dude, other syslog server

Mon Oct 18, 2010 9:48 pm

I am initially trying to log some routers to Dude. I will probably migrate to something else that is more robust down the road.

At this point I have an RB that has this configuration:

/system logging action
set memory memory-lines=100 memory-stop-on-full=no name=memory target=memory
set disk disk-file-count=2 disk-file-name=log disk-lines-per-file=100 \
disk-stop-on-full=no name=disk target=disk
set echo name=echo remember=yes target=echo
set remote bsd-syslog=no name=remote remote=10.10.10.10:514 src-address=\
0.0.0.0 syslog-facility=daemon syslog-severity=auto target=remote
/system logging
add action=memory disabled=no prefix="" topics=info
add action=memory disabled=no prefix="" topics=error
add action=memory disabled=no prefix="" topics=warning
add action=echo disabled=no prefix="" topics=critical
add action=remote disabled=no prefix=inxwrlsap- topics=\
info,critical,error,warning


What it appears to me, when I do a :log error test is that no traffic is generated to the Dude server at 10.10.10.10 (that is watching torch). Is there a reason for this?

I am not seeing the logs in the Event log in Dude as I expect and I am troubleshooting as to why that is.
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26381
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Logging to Dude, other syslog server

Tue Oct 19, 2010 10:48 am

It will not appear in Dude event log. You have to configure the Syslog in Dude, and it will appear as a separate section.

Image
 
iam8up
Member
Member
Topic Author
Posts: 333
Joined: Sun Oct 28, 2007 10:58 pm
Location: Troy, OH
Contact:

Re: Logging to Dude, other syslog server

Tue Oct 19, 2010 6:32 pm

I am running 3.6. Mine looks like this.

Image
 
xxiii
Member Candidate
Member Candidate
Posts: 234
Joined: Wed May 31, 2006 12:55 am

Re: Logging to Dude, other syslog server

Tue Oct 19, 2010 6:44 pm

Your line that says:

add action=remote disabled=no prefix=inxwrlsap- topics=\
info,critical,error,warning

Means to log only events that have all four of those topics. You need to put four separate rules.

It is occasionally handy to be able to select multiple topics, for instance if I only want to see debug packets related to bgp, then I would use topics=bgp,debug.

And you can do things like ospf,!raw,!debug if you want to strip out some types of messages without turning off something completely.
 
iam8up
Member
Member
Topic Author
Posts: 333
Joined: Sun Oct 28, 2007 10:58 pm
Location: Troy, OH
Contact:

Re: Logging to Dude, other syslog server

Tue Oct 19, 2010 10:05 pm

Your line that says:

add action=remote disabled=no prefix=inxwrlsap- topics=\
info,critical,error,warning

Means to log only events that have all four of those topics. You need to put four separate rules.

It is occasionally handy to be able to select multiple topics, for instance if I only want to see debug packets related to bgp, then I would use topics=bgp,debug.

And you can do things like ospf,!raw,!debug if you want to strip out some types of messages without turning off something completely.
That makes sense, didn't think of the syntax that way.

Fixed, thank you very much!

Who is online

Users browsing this forum: Majestic-12 [Bot], shahzaddj1 and 116 guests