Troubleshooting Tip: Log showing truncated on the QRadar syslog server
| Description | This article describes an issue in which FortiGate logs appear truncated on the Q-Radar syslog server. |
| Scope | FortiGate. |
| Solution | The attached capture shows a FortiGate sending the log towards the QRadar syslog server.
Below is the log text extracted from the Wireshark capture:
date=2025-12-08 time=11:25:32 devname="_FGT_FW1" devid="FGVMSL0000000" eventtime=1765173333344578239 tz="+0530"logid="0419016384" type="utm" subtype="ips" eventtype="signature" level="alert" vd="root" severity="low" srcip=10.128.2.50 srccountry="Reserved" dstip=10.132.115.104 dstcountry="Reserved" srcintf="port1" srcintfrole="undefined" dstintf="port2" dstintfrole="undefined" sessionid=107963143 action="dropped" proto=6 service="HTTP" policyid=121 poluuid="1f2bfaf8-97b1-51ef-026b-b7e43fcb8613" policytype="policy" attack="Assetnote. Scanner" srcport=47874 dstport=80 hostname="sampletest. com"
The following image shows the log received on the QRadar:
The last line of the log on Q-Radar only shows two octets of IP addresses present in the log. IPv4 has four octets i.e. x.x.x.x. To compare with the log text extracted from the Wireshark capture, the complete IP address is 103.15.1.1.
The issue occurred because the Max Syslog Payload Length on the Q-Radar side was set to approximately 1024 bytes, while the actual log size exceeded this limit. After increasing the Max Syslog Payload Length in Q-Radar, the complete log will be displayed correctly. |

