Manual:System/Log: Difference between revisions

From MikroTik Wiki
Jump to navigation Jump to search
← Older edit
 
(19 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{Versions|v3, v4}}
{{Versions|v3, v4 +}}


<h2>Summary</h2>
==Summary==


<p>
<p>
Line 8: Line 8:
</p>
</p>


<h2>Log messages</h2>
==Log messages==


<p><b>Sub-menu level:</b> <code> /log </code>
<p id="shbox"><b>Sub-menu level:</b> <code> /log </code>
</p>
<br />
<br />
</p>
<p>
<p>
All messages stored in routers local memory can be printed from <code>/log</code> menu. Each entry contains time and date when event occurred, topics that this message belongs to and message itself.
All messages stored in routers local memory can be printed from <code>/log</code> menu. Each entry contains time and date when event occurred, topics that this message belongs to and message itself.
Line 34: Line 33:
</p>
</p>


<b>Note</b> that print command accepts several parameters that allows to detect new log entries, print only necessary messages and so on. For more information about parameters refer to [[Scripting#print_parameters | scripting manual]]
{{ Note | print command accepts several parameters that allows to detect new log entries, print only necessary messages and so on. For more information about parameters refer to [[Scripting#print_parameters | scripting manual]] }}
 
For example following command will print all log messages where one of the topics is info and will detect new log entries until Ctrl+C is pressed
For example following command will print all log messages where one of the topics is info and will detect new log entries until Ctrl+C is pressed
<pre>
<pre>
Line 53: Line 53:
</pre>
</pre>


<h2>Logging configuration</h2>
==Logging configuration==


<p><b>Sub-menu level:</b> <code> /system logging </code>
<p id="shbox"><b>Sub-menu level:</b> <code> /system logging </code>
</p>
<br />
<br />
</p>


<p>
<p>
<table class="styled_table">
<table class="styled_table">
<tr>
<tr>
Line 75: Line 74:
</tr>
</tr>
<tr>
<tr>
     <td><var><b>topics</b></var> (<em>account, async, backup, bgp, calc, critical, ddns, debug, dhcp, e-mail, error, event, firewall, gsm, hotspot, igmp-proxy, info, ipsec, iscsi, isdn, l2tp, ldp, manager, mme, mpls, ntp, ospf, ovpn, packet, pim, ppp, pppoe, pptp, radius, radvd, raw, read, rip, route, rsvp, script, sertcp, state, store, system, telephony, tftp, timer, ups, warning, watchdog, web-proxy, wireless, write</em>; Default: <b>info</b>)</td>
     <td><var><b>topics</b></var> (<em>account, bfd, caps, ddns, dns, error, gsm, info, iscsi, l2tp, manager, ntp, packet, pppoe, radvd, rip, script, smb, sstp, system, timer, vrrp, web-proxy, async, bgp, certificate, debug, dot1x, dude, event, hotspot, interface, isdn, ldp, mme, ospf, pim, pptp, raw, route, sertcp, snmp, state, telephony, upnp, warning, wireless, backup, calc, critical, dhcp, e-mail, firewall, igmp-proxy, ipsec, kvm, lte, mpls, ovpn, ppp, radius, read, rsvp, simulator, ssh, store, tftp, ups, watchdog, write</em>; Default: <b>info</b>)</td>
     <td> log all messages that falls into specified topic or list of topics. <br />
     <td> log all messages that falls into specified topic or list of topics. <br />
<b>'!'</b> character can be used before topic to exclude messages falling under this topic. For example, we want to log [[ Time | NTP]] debug info without too much details: <br />
<b>'!'</b> character can be used before topic to exclude messages falling under this topic. For example, we want to log [[ Time | NTP]] debug info without too much details: <br />
Line 84: Line 83:
</p>
</p>


<h3>Actions</h3>
===Actions===
<p><b>Sub-menu level:</b> <code> /system logging action</code>
<p id="shbox"><b>Sub-menu level:</b> <code> /system logging action</code>
</p>
<br />
<br />
</p>
 
<p>
<p>
<table class="styled_table">
<table class="styled_table">
Line 113: Line 113:
     <td><var><b>disk-stop-on-full</b></var> (<em>yes|no</em>; Default: <b>no</b>)</td>
     <td><var><b>disk-stop-on-full</b></var> (<em>yes|no</em>; Default: <b>no</b>)</td>
     <td>whether to stop to save log messages to disk after the specified disk-lines-per-file and disk-file-count number is reached, applicable only if action=disk</td>
     <td>whether to stop to save log messages to disk after the specified disk-lines-per-file and disk-file-count number is reached, applicable only if action=disk</td>
</tr>
<tr>
    <td><var><b>email-start-tls</b></var> (<em>yes | no</em>; Default: <b>no</b>)</td>
    <td>Whether to use tls when sending email, applicable only if action=email</td>
</tr>
</tr>
<tr>
<tr>
Line 135: Line 139:
</tr>
</tr>
<tr>
<tr>
     <td><var><b>remote</b></var> (<em>IP Address[:Port]</em>; Default: <b>0.0.0.0:514</b>)</td>
     <td><var><b>remote</b></var> (<em>IP/IPv6 Address[:Port]</em>; Default: <b>0.0.0.0:514</b>)</td>
     <td>remote logging server's IP address and UDP port, applicable if action=remote</td>
     <td>remote logging server's IP/IPv6 address and UDP port, applicable if action=remote</td>
</tr>
</tr>
<tr>
<tr>
Line 175: Line 179:
</tr>
</tr>
</table>
</table>
Note: default actions can not be deleted or renamed.
</p>
</p>
{{Note | default actions can not be deleted or renamed. }}


 
==Topics==
<h2>Topics</h2>
<p>
<p>
Each log entry have topic which describes the origin of log message. There can be more than one topic assigned to log message. For example, OSPF debug logs have four different topics: route, ospf, debug and raw.
Each log entry have topic which describes the origin of log message. There can be more than one topic assigned to log message. For example, OSPF debug logs have four different topics: route, ospf, debug and raw.
Line 229: Line 231:


</table>
</table>


Topics used by various RouterOS facilities
Topics used by various RouterOS facilities
<table class="styled_table">
<table class="styled_table">
<tr>
<tr>
Line 246: Line 250:
<tr>
<tr>
     <td><var><b>backup</b></var></td>
     <td><var><b>backup</b></var></td>
     <td>Log messages generated by [[Configuration_Management#System_Backup | backup]] creation facility.</td>
     <td>Log messages generated by [[Manual:Configuration_Management#System_Backup | backup]] creation facility.</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>bfd</b></var></td>
     <td><var><b>bfd</b></var></td>
     <td>Log messages generated by [[BFD]] protocol</td>
     <td>Log messages generated by [[Manual:Routing/BFD]] protocol</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>bgp</b></var></td>
     <td><var><b>bgp</b></var></td>
     <td>Log messages generated by [[BGP]] protocol</td>
     <td>Log messages generated by [[Manual:Routing/BGP]] protocol</td>
</tr>
</tr>
<tr>
<tr>
Line 260: Line 264:
     <td>Routing calculation log messages.</td>
     <td>Routing calculation log messages.</td>
</tr>
</tr>
 
<tr>
    <td><var><b>caps</b></var></td>
    <td>CAPsMAN wireless device management</td>
</tr>
<tr>
    <td><var><b>certificate</b></var></td>
    <td>Security [[Manual:System/Certificates|certificate]]</td>
</tr>
<tr>
    <td><var><b>dns</b></var></td>
    <td>Name server lookup related information</td>
</tr>
<tr>
<tr>
     <td><var><b>ddns</b></var></td>
     <td><var><b>ddns</b></var></td>
     <td>Log messages generated by [[Dynamic DNS]] tool</td>
     <td>Log messages generated by [[Manual:Tools/Dynamic DNS]] tool</td>
</tr>
<tr>
    <td><var><b>dude</b></var></td>
    <td>Messages related to the Dude server package [[Manual:The_Dude]] tool</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>dhcp</b></var></td>
     <td><var><b>dhcp</b></var></td>
     <td>DHCP [[DHCP_Client | client]], [[DHCP_Server | server]] and [[DHCP_Relay | relay]] log messages</td>
     <td>DHCP [[Manual:IP/DHCP_Client | client]], [[Manual:IP/DHCP_Server | server]] and [[Manual:IP/DHCP_Relay | relay]] log messages</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>e-mail</b></var></td>
     <td><var><b>e-mail</b></var></td>
     <td>Messages generated by [[e-mail]] tool.</td>
     <td>Messages generated by [[Manual:Tools/email]] tool.</td>
</tr>
</tr>
<tr>
<tr>
Line 280: Line 298:
<tr>
<tr>
     <td><var><b>firewall</b></var></td>
     <td><var><b>firewall</b></var></td>
     <td>Firewall log messages generated when <b>action=log</b> is set in [[firewall]] rule</td>
     <td>Firewall log messages generated when <b>action=log</b> is set in [[Manual:IP/Firewall | firewall]] rule</td>
</tr>
</tr>
<tr>
<tr>
Line 288: Line 306:
<tr>
<tr>
     <td><var><b>hotspot</b></var></td>
     <td><var><b>hotspot</b></var></td>
     <td>[[Hotspot]] related log entries</td>
     <td>[[Manual:IP/Hotspot | Hotspot]] related log entries</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>igmp-proxy</b></var></td>
     <td><var><b>igmp-proxy</b></var></td>
     <td>[[IGMP-Proxy]] related log entries</td>
     <td>[[Manual:Routing/IGMP-Proxy | IGMP Proxy]] related log entries</td>
</tr>
</tr>


<tr>
<tr>
     <td><var><b>ipsec</b></var></td>
     <td><var><b>ipsec</b></var></td>
     <td>[[IpSec]] log entries</td>
     <td>[[Manual:IP/IPsec | IPSec]] log entries</td>
</tr>
</tr>
<tr>
<tr>
Line 306: Line 324:
     <td><var><b>isdn</b></var></td>
     <td><var><b>isdn</b></var></td>
     <td></td>
     <td></td>
</tr>
<tr>
    <td><var><b>interface</b></var></td>
    <td></td>
</tr>
<tr>
    <td><var><b>kvm</b></var></td>
    <td>Messages related to the KVM virtual machine functionality</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>l2tp</b></var></td>
     <td><var><b>l2tp</b></var></td>
     <td> Log entries generated by [[l2tp]] client and server</td>
     <td> Log entries generated by [[Manual:Interface/L2TP]] client and server</td>
</tr>
<tr>
    <td><var><b>lte</b></var></td>
    <td>Messasges related to the LTE/4G modem configuration</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>ldp</b></var></td>
     <td><var><b>ldp</b></var></td>
     <td>[[LDP]] protocol related messages</td>
     <td>[[Manual:MPLS/LDP]] protocol related messages</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>manager</b></var></td>
     <td><var><b>manager</b></var></td>
     <td>[[User manager]] log messages.</td>
     <td>[[Manual:User_Manager]] log messages.</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>mme</b></var></td>
     <td><var><b>mme</b></var></td>
     <td>[[MME]] routing protocol messages</td>
     <td>[[Manual:Routing/MME | MME]] routing protocol messages</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>mpls</b></var></td>
     <td><var><b>mpls</b></var></td>
     <td>[[MPLS]] messages</td>
     <td>[[Manual:MPLS | MPLS]] messages</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>ntp</b></var></td>
     <td><var><b>ntp</b></var></td>
     <td>[[Time | sNTP]] client generated log entries</td>
     <td>[[Manual:System/Time | sNTP]] client generated log entries</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>ospf</b></var></td>
     <td><var><b>ospf</b></var></td>
     <td>[[OSPF]] routing protocol messages</td>
     <td>[[Manual:Routing/OSPF]] routing protocol messages</td>
</tr>
</tr>
<tr>
<tr>
Line 342: Line 372:
<tr>
<tr>
     <td><var><b>pim</b></var></td>
     <td><var><b>pim</b></var></td>
     <td>[[Multicast | Multicast PIM-SM]] related messages</td>
     <td>[[Manual:Routing/Multicast | Multicast PIM-SM]] related messages</td>
</tr>
</tr>
<tr>
<tr>
Line 350: Line 380:
<tr>
<tr>
     <td><var><b>pppoe</b></var></td>
     <td><var><b>pppoe</b></var></td>
     <td>[[PPPoE]] server/client related messages</td>
     <td>[[Manual:Interface/PPPoE | PPPoE]] server/client related messages</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>pptp</b></var></td>
     <td><var><b>pptp</b></var></td>
     <td>[[PPTP]] server/client related messages</td>
     <td>[[Manual:Interface/PPTP | PPTP]] server/client related messages</td>
</tr>
</tr>
<tr>
<tr>
Line 370: Line 400:
<tr>
<tr>
     <td><var><b>rip</b></var></td>
     <td><var><b>rip</b></var></td>
     <td>[[RIP]] routing protocol messages</td>
     <td>[[Manual:Routing/RIP | RIP]] routing protocol messages</td>
</tr>
</tr>
<tr>
<tr>
Line 399: Line 429:
     <td><var><b>store</b></var></td>
     <td><var><b>store</b></var></td>
     <td>Log entries generated by [[Store]] facility</td>
     <td>Log entries generated by [[Store]] facility</td>
</tr>
<tr>
    <td><var><b>smb</b></var></td>
    <td>Messages related to the [[Manual:IP/SMB|SMB]] file sharing system</td>
</tr>
<tr>
    <td><var><b>snmp</b></var></td>
    <td>Messages related to [[Manual:SNMP|Simple network management protocol (SNMP)]] configuration</td>
</tr>
</tr>
<tr>
<tr>
Line 406: Line 444:
<tr>
<tr>
     <td><var><b>telephony</b></var></td>
     <td><var><b>telephony</b></var></td>
     <td></td>
     <td><em>Obsolete! Previously used by the IP telephony package</em></td>
</tr>
</tr>
<tr>
<tr>
Line 425: Line 463:
     <td>Messages generated by UPS monitoring tool</td>
     <td>Messages generated by UPS monitoring tool</td>
</tr>
</tr>
 
<tr>
    <td><var><b>vrrp</b></var></td>
    <td>Messages generated [[Manual:Interface/VRRP|VRRP]]</td>
</tr>
<tr>
<tr>
     <td><var><b>watchdog</b></var></td>
     <td><var><b>watchdog</b></var></td>
Line 436: Line 477:
<tr>
<tr>
     <td><var><b>wireless</b></var></td>
     <td><var><b>wireless</b></var></td>
     <td>[[Wireless]] log entries.</td>
     <td>[[M:Interface/Wireless]] log entries.</td>
</tr>
</tr>
<tr>
<tr>
Line 454: Line 495:
and then make everything log using this new action:
and then make everything log using this new action:


  /system logging action=file
  /system logging add action=file


You can log only errors there by issuing command:
You can log only errors there by issuing command:


  /system logging topics=error action=file  
  /system logging add topics=error action=file  


This will log into files '''log.0.txt''' and '''log.1.txt'''.  
This will log into files '''log.0.txt''' and '''log.1.txt'''.  
Line 468: Line 509:
  /system logging action add name=usb target=disk disk-file-name=usb1/log
  /system logging action add name=usb target=disk disk-file-name=usb1/log


[[Category:Manual]]
{{Note | Logging entries from files will be stored back in the memory after reboot.}}
[[Category:Unfinished]]
 
== Examples ==
 
=== Webproxy logging ===
 
These two screenshots will show you how to configure the RouterOS logging facility to send Webrpoxy logs to a remote syslog server, in this example, located at 192.168.100.12. The syslog server can be any software that supports receiving syslogs, for example Kiwi syslog.
 
* [[Image:Logging2.png]]
Add a new logging action, with "remote" and the IP of the remote server. Call it whatever you like
 
* [[Image:Logging1.png]]
Then add a new logging rule with the topic "webproxy" and then newly created action. Note that you must have webproxy running on this router already, for this to work. To test, you can temporary change the action to "memory" and see the "log" window if the webproxy visited websites are logged. If it works, change it back to your new remote action
 
''Note: it's a good idea to add another topic in the same rule: '''!debug'''. This would be to ensure you don't get any debug stuff, only the visited sites.''
 
=== Rsyslog ===
 
It is possible to send all logs to a remote syslog server, one example of a syslog server is Rsyslog. Below you can find configuration example that is relevant to RouterOS:
<pre>
/system logging action
set [find name=remote] remote=10.0.0.1
/system logging
add action=remote topics=info
add action=remote topics=critical
add action=remote topics=error
add action=remote topics=warning
</pre>
 
With this configuration all logs will be present on the device and on the remote syslog server. Below you can find configuration lines that are relevant to a Rsyslog server (only lines that should be changed from the default values):
<pre>
#/etc/rsyslog.conf
$ModLoad imudp
$UDPServerAddress 10.0.0.1
$UDPServerRun 514
$AllowedSender UDP, 10.0.0.0/24 127.0.0.1
 
$template Router1Log, "/var/log/MikroTik/router1.log"
:fromhost-ip, isequal, "10.0.0.2" -?Router1Log
& stop
</pre>
 
For security reasons you should only allow Rsyslog to listen to a certain address, this limits the instance to a single interface. You should also specify only certain IP addresses that are allowed to send their logs to the particular syslog server.
 
{{ Note | Never rely on a single security measure, you should also implement proper Firewall on the machine running Rsyslog, to limit access to the server. }}
 
[[Category:Manual|L]]
[[Category:Monitoring|L]]

Latest revision as of 13:06, 15 July 2020

Applies to RouterOS: v3, v4 +

Summary


RouterOS is capable of logging various system events and status information. Logs can be saved in routers memory (RAM), disk, file, sent by email or even sent to remote syslog server (RFC 3164).

Log messages

Sub-menu level: /log


All messages stored in routers local memory can be printed from /log menu. Each entry contains time and date when event occurred, topics that this message belongs to and message itself. 

[admin@ZalaisKapots] /log> print 
jan/02/1970 02:00:09 system,info router rebooted 
sep/15 09:54:33 system,info,account user admin logged in from 10.1.101.212 via winbox 
sep/15 12:33:18 system,info item added by admin 
sep/15 12:34:26 system,info mangle rule added by admin 
sep/15 12:34:29 system,info mangle rule moved by admin 
sep/15 12:35:34 system,info mangle rule changed by admin 
sep/15 12:42:14 system,info,account user admin logged in from 10.1.101.212 via telnet 
sep/15 12:42:55 system,info,account user admin logged out from 10.1.101.212 via telnet 
01:01:58 firewall,info input: in:ether1 out:(none), src-mac 00:21:29:6d:82:07, proto UDP, 
                          10.1.101.1:520->10.1.101.255:520, len 452

If logs are printed at the same date when log entry was added, then only time will be shown. In example above you can see that second message was added on sep/15 current year (year is not added) and the last message was added today so only the time is displayed.

Note: print command accepts several parameters that allows to detect new log entries, print only necessary messages and so on. For more information about parameters refer to scripting manual


For example following command will print all log messages where one of the topics is info and will detect new log entries until Ctrl+C is pressed 

[admin@ZalaisKapots] /log > print follow where topics~".info"
12:52:24 script,info hello from script
-- Ctrl-C to quit.


If print is in follow mode you can hit 'space' on keyboard to insert separator: 

[admin@ZalaisKapots] /log > print follow where topics~".info"
12:52:24 script,info hello from script

 = = =   = = =   = = =      = = =   = = =   = = =      = = =   = = =   = = =

-- Ctrl-C to quit.

Logging configuration

Sub-menu level: /system logging


Property Description
action (name; Default: memory) specifies one of the system default actions or user specified action listed in actions menu
prefix (string; Default: ) prefix added at the beginning of log messages
topics (account, bfd, caps, ddns, dns, error, gsm, info, iscsi, l2tp, manager, ntp, packet, pppoe, radvd, rip, script, smb, sstp, system, timer, vrrp, web-proxy, async, bgp, certificate, debug, dot1x, dude, event, hotspot, interface, isdn, ldp, mme, ospf, pim, pptp, raw, route, sertcp, snmp, state, telephony, upnp, warning, wireless, backup, calc, critical, dhcp, e-mail, firewall, igmp-proxy, ipsec, kvm, lte, mpls, ovpn, ppp, radius, read, rsvp, simulator, ssh, store, tftp, ups, watchdog, write; Default: info) log all messages that falls into specified topic or list of topics.

'!' character can be used before topic to exclude messages falling under this topic. For example, we want to log NTP debug info without too much details:

/system logging add topics=ntp,debug,!packet

Actions

Sub-menu level: /system logging action


Property Description
bsd-syslog (yes|no; Default: ) whether to use bsd-syslog as defined in RFC 3164
disk-file-count (integer [1..65535]; Default: 2) specifies number of files used to store log messages, applicable only if action=disk
disk-file-name (string; Default: log) name of the file used to store log messages, applicable only if action=disk
disk-lines-per-file (integer [1..65535]; Default: 100) specifies maximum size of file in lines, applicable only if action=disk
disk-stop-on-full (yes|no; Default: no) whether to stop to save log messages to disk after the specified disk-lines-per-file and disk-file-count number is reached, applicable only if action=disk
email-start-tls (yes | no; Default: no) Whether to use tls when sending email, applicable only if action=email
email-to (string; Default: ) email address where logs are sent, applicable only if action=email
memory-lines (integer [1..65535]; Default: 100) number of records in local memory buffer, applicable only if action=memory
memory-stop-on-full (yes|no; Default: no) whether to stop to save log messages in local buffer after the specified memory-lines number is reached
name (string; Default: ) name of an action
remember (yes|no; Default: ) whether to keep log messages, which have not yet been displayed in console, applicable if action=echo
remote (IP/IPv6 Address[:Port]; Default: 0.0.0.0:514) remote logging server's IP/IPv6 address and UDP port, applicable if action=remote
src-address (IP address; Default: 0.0.0.0) source address used when sending packets to remote server
syslog-facility (auth, authpriv, cron, daemon, ftp, kern, local0, local1, local2, local3, local4, local5, local6, local7, lpr, mail, news, ntp, syslog, user, uucp; Default: daemon)
syslog-severity (alert, auto, critical, debug, emergency, error, info, notice, warning; Default: auto) Severity level indicator defined in RFC 3164:
  • Emergency: system is unusable
  • Alert: action must be taken immediately
  • Critical: critical conditions
  • Error: error conditions
  • Warning: warning conditions
  • Notice: normal but significant condition
  • Informational: informational messages
  • Debug: debug-level messages
target (disk, echo, email, memory, remote; Default: memory) storage facility or target of log messages
  • disk - logs are saved to the hard drive more>>
  • echo - logs are displayed on the console screen
  • email - logs are sent by email
  • memory - logs are stored in local memory buffer
  • remote - logs are sent to remote host

Note: default actions can not be deleted or renamed.


Topics

Each log entry have topic which describes the origin of log message. There can be more than one topic assigned to log message. For example, OSPF debug logs have four different topics: route, ospf, debug and raw. 

11:11:43 route,ospf,debug SEND: Hello Packet 10.255.255.1 -> 224.0.0.5 on lo0 
11:11:43 route,ospf,debug,raw PACKET: 
11:11:43 route,ospf,debug,raw     02 01 00 2C 0A FF FF 03 00 00 00 00 E7 9B 00 00 
11:11:43 route,ospf,debug,raw     00 00 00 00 00 00 00 00 FF FF FF FF 00 0A 02 01 
11:11:43 route,ospf,debug,raw     00 00 00 28 0A FF FF 01 00 00 00 00


List of Facility independent topics

Topic Description
critical Log entries marked as critical, these log entries are printed to console each time you log in.
debug Debug log entries
error Error messages
info Informative log entry
packet Log entry that shows contents from received/sent packet
raw Log entry that shows raw contents of received/sent packet
warning Warning message.


Topics used by various RouterOS facilities

Topic Description
account Log messages generated by accounting facility.
async Log messages generated by asynchronous devices
backup Log messages generated by backup creation facility.
bfd Log messages generated by Manual:Routing/BFD protocol
bgp Log messages generated by Manual:Routing/BGP protocol
calc Routing calculation log messages.
caps CAPsMAN wireless device management
certificate Security certificate
dns Name server lookup related information
ddns Log messages generated by Manual:Tools/Dynamic DNS tool
dude Messages related to the Dude server package Manual:The_Dude tool
dhcp DHCP client, server and relay log messages
e-mail Messages generated by Manual:Tools/email tool.
event Log message generated at routing event. For example, new route have been installed in routing table.
firewall Firewall log messages generated when action=log is set in firewall rule
gsm Log messages generated by GSM devices
hotspot Hotspot related log entries
igmp-proxy IGMP Proxy related log entries
ipsec IPSec log entries
iscsi
isdn
interface
kvm Messages related to the KVM virtual machine functionality
l2tp Log entries generated by Manual:Interface/L2TP client and server
lte Messasges related to the LTE/4G modem configuration
ldp Manual:MPLS/LDP protocol related messages
manager Manual:User_Manager log messages.
mme MME routing protocol messages
mpls MPLS messages
ntp sNTP client generated log entries
ospf Manual:Routing/OSPF routing protocol messages
ovpn OpenVPN tunnel messages
pim Multicast PIM-SM related messages
ppp ppp facility messages
pppoe PPPoE server/client related messages
pptp PPTP server/client related messages
radius Log entries generated by RADIUS Client
radvd IPv6 radv deamon log messages.
read SMS tool messages
rip RIP routing protocol messages
route Routing facility log entries
rsvp Resource Reservation Protocol generated messages.
script Log entries generated from scripts
sertcp Log messages related to facility responsible for "/ports remote-access"
simulator
state DHCP Client and routing state messages.
store Log entries generated by Store facility
smb Messages related to the SMB file sharing system
snmp Messages related to Simple network management protocol (SNMP) configuration
system Generic system messages
telephony Obsolete! Previously used by the IP telephony package
tftp TFTP server generated messages
timer Log messages that are related to timers used in RouterOS. For example bgp keepalive logs 
12:41:40 route,bgp,debug,timer KeepaliveTimer expired 
12:41:40 route,bgp,debug,timer     RemoteAddress=2001:470:1f09:131::1
ups Messages generated by UPS monitoring tool
vrrp Messages generated VRRP
watchdog Watchdog generated log entries
web-proxy Log messages generated by web proxy
wireless M:Interface/Wireless log entries.
write SMS tool messages.

Logging to file

To log everything to file, add new log action: 

/system logging action add name=file target=disk disk-file-name=log

and then make everything log using this new action: 

/system logging add action=file

You can log only errors there by issuing command: 

/system logging add topics=error action=file

This will log into files log.0.txt and log.1.txt.

You can specify maximum size of file in lines by specifying disk-lines-per-file. <file>.0.txt is active file were new logs are going to be appended and once it size will reach maximum it will become <file>.1.txt, and new empty <file>.0.txt will be created.

You can log into USB flashes or into MicroSD/CF (on Routerboards) by specifying it's directory name before file name. For example, if you have accessible usb flash as usb1 directory under /files, you should issue following command: 

/system logging action add name=usb target=disk disk-file-name=usb1/log

Note: Logging entries from files will be stored back in the memory after reboot.


Examples

Webproxy logging

These two screenshots will show you how to configure the RouterOS logging facility to send Webrpoxy logs to a remote syslog server, in this example, located at 192.168.100.12. The syslog server can be any software that supports receiving syslogs, for example Kiwi syslog.

Add a new logging action, with "remote" and the IP of the remote server. Call it whatever you like

Then add a new logging rule with the topic "webproxy" and then newly created action. Note that you must have webproxy running on this router already, for this to work. To test, you can temporary change the action to "memory" and see the "log" window if the webproxy visited websites are logged. If it works, change it back to your new remote action

Note: it's a good idea to add another topic in the same rule: !debug. This would be to ensure you don't get any debug stuff, only the visited sites.

Rsyslog

It is possible to send all logs to a remote syslog server, one example of a syslog server is Rsyslog. Below you can find configuration example that is relevant to RouterOS: 

/system logging action
set [find name=remote] remote=10.0.0.1
/system logging
add action=remote topics=info
add action=remote topics=critical
add action=remote topics=error
add action=remote topics=warning

With this configuration all logs will be present on the device and on the remote syslog server. Below you can find configuration lines that are relevant to a Rsyslog server (only lines that should be changed from the default values): 

#/etc/rsyslog.conf
$ModLoad imudp
$UDPServerAddress 10.0.0.1
$UDPServerRun 514
$AllowedSender UDP, 10.0.0.0/24 127.0.0.1

$template Router1Log, "/var/log/MikroTik/router1.log"
:fromhost-ip, isequal, "10.0.0.2" -?Router1Log
& stop

For security reasons you should only allow Rsyslog to listen to a certain address, this limits the instance to a single interface. You should also specify only certain IP addresses that are allowed to send their logs to the particular syslog server.

Note: Never rely on a single security measure, you should also implement proper Firewall on the machine running Rsyslog, to limit access to the server.


Retrieved from "https://wiki.mikrotik.com/index.php?title=Manual:System/Log&oldid=34121"