Created on
09-20-2022
09:09 PM
Edited on
01-30-2025
08:36 AM
By
Stephen_G
Description | This article describes when there are issues with FortiGate logs GUI display from FortiAnalyzer and no logs are visible. |
Scope | FortiGate side troubleshooting. |
Solution |
This can be checked and addressed as per below:
execute log fortianalyzer test-connectivity
However, note, this can be resource intensive based on amount of logs.
It is possible to set the duration to be lower like 1 minute - 'diag debug duration 1' and then enable its debugs.
To collect debug information of FortiAnalyzer enabled logs:
It shows an output as below:
<226> __on_pkt_recv()-1376: opt=52, opt_len=9 <146> __on_pkt_recv()-1376: opt=52, opt_len=9
First determine the number of miglogd process as per command:
1 Main and 1 child process. For efficiency of logs, the child process can be increased as per below:
get sys performance status <----- Ensure enough memory is free.
Other useful document:
Related article: Troubleshooting Tip: FortiGate to FortiAnalyzer connectivity |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.