- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
03-31-2015 07:01 AM
<190>Mar 31 08:52:56 XXXX-firewall-name 1,2015/03/31 08:52:55,001606005137,TRAFFIC,end,1,2015/03/31 08:52:55,source_ip,,destination_ip,trust-untrust-web-services,,,paloalto-wildfire-cloud,vsys1,trust,untrust,ethernet1/1,ethernet1/3,Log_Forward,2015/03/31 08:52:55,57030,1,42349,443,45974,443,0x400053,tcp,allow,2319,1200,1119,20,2015/03/31 08:50:26,
120,business-and-economy,0,113995574,0x0,XXXXXXXXX.255.255,SG,0,11,9,tcp-rst-from-client
03-31-2015 09:27 AM
The log you show is a traffic log. The URL is logged in the Threat log I believe. Below is an excerpt from another discussion on this URL logging subject.
In order to forward URL logs, it is necessary to forward Threat logs of Severity "informational" to the Syslog server. Doing so will forward other informational threat logs (Data Filtering) in addition to URL logs.
Please refer to the following document for more information on how to configure URL log forwarding to Syslog: How to Forward Threat Logs to Syslog Server
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!