Whether to stop to save log messages in local buffer after the specified memory-lines number is reached Memory-stop-on-full ( yes|no Default: no) Number of records in local memory buffer, applicable only if action=memory Whether to use tls when sending email, applicable only if action=emailĮmail address where logs are sent, applicable only if action=email 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 Specifies maximum size of file in lines, applicable only if action=disk Name of the file used to store log messages, applicable only if action=diskĭisk-lines-per-file ( integer Default: 100) Specifies number of files used to store log messages, applicable only if action=disk Whether to use bsd-syslog as defined in RFC 3164ĭisk-file-count ( integer Default: 2) system logging add topics=ntp,debug,!packet For example, we want to log NTP debug info without too much details: ![]() '!' character can be used before topic to exclude messages falling under this topic. Log all messages that falls into specified topic or list of topics. ![]() 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) Prefix added at the beginning of log messages Specifies one of the system default actions or user specified action listed in actions menu If print is in follow mode you can hit 'space' on keyboard to insert /log > print follow where topics~".info" For more information about parameters refer to scripting manualįor 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 /log > print follow where topics~".info" Note: print command accepts several parameters that allows to detect new log entries, print only necessary messages and so on. 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. If logs are printed at the same date when log entry was added, then only time will be shown. Sep/15 12:42:14 system,info,account user admin logged in from 10.1.101.212 via telnet ![]() Sep/15 12:35:34 system,info mangle rule changed by admin Sep/15 12:34:29 system,info mangle rule moved by admin Sep/15 12:34:26 system,info mangle rule added by admin Sep/15 12:33:18 system,info item added by admin Sep/15 09:54:33 system,info,account user admin logged in from 10.1.101.212 via winbox Each entry contains time and date when event occurred, topics that this message belongs to and message /log> print Logs can be saved in routers memory (RAM), disk, file, sent by email or even sent to remote syslog server (RFC 3164).Īll messages stored in routers local memory can be printed from /log menu. RouterOS is capable of logging various system events and status information.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |