Syslog is not updating
As a best practice, always use SSL to listen for syslog messages.However, if you must use UDP, make sure that the syslog server and client are both on a dedicated, secure VLAN to prevent untrusted hosts from sending UDP traffic to the firewall.Sub-menu level: print jan/02/1970 system,info router rebooted sep/15 system,info,account user admin logged in from 10.1.101.212 via winbox sep/15 system,info item added by admin sep/15 system,info mangle rule added by admin sep/15 system,info mangle rule moved by admin sep/15 system,info mangle rule changed by admin sep/15 system,info,account user admin logged in from 10.1.101.212 via telnet sep/15 system,info,account user admin logged out from 10.1.101.212 via telnet firewall,info input: in:ether1 out:(none), src-mac :6d:, proto UDP, 10.1.101.0- 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.To configure the PAN-OS Integrated User-ID agent to create new user mappings based on syslog monitoring, start by defining Syslog Parse profiles.
We need to edit the rsyslog config file "/etc/rsyslog.conf" and enable "imudp" module by uncommenting the same.
Use caution when using UDP to receive syslog messages because it is an unreliable protocol and as such there is no way to verify that a message was sent from a trusted syslog server.
As a best practice, always use SSL to listen for syslog messages when using agentless User Mapping on a firewall.
Router OS 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).