Troubleshooting Tip: How to verify the log limits of the FortiAnalyzer hardware platforms
Description
This article describes how to confirm whether a FortiAnalyzer hardware platform has reached its rated log limits.
Notes:
These limits are not enforced, and reaching them does not automatically lead to data loss. However, consistently exceeding the log limits may overload the hardware and significantly degrade the system performance.
The information here is for FortiAnalyzer hardware only. In FortiAnalyzer VM, the log limits are defined by the VM license and do not relate to the hardware capabilities of the unit.
Log Forwarding utilizes additional resources. Forwarding all logs to an external server should not have a very significant impact, but applying filters in the log-forward configuration may increase the CPU utilization even though there is no explicit limit for that.
Â
Scope
FortiAnalyzer/FortiManager - hardware platforms only.
Solution
The following CLI command prints the limits:
Â
get system loglimitsÂ
The following CLI command tree shows the actual log rate and log volume stats:
Â
diagnose fortilogd
lograte Display log rate.
lograte-adom Display log rate by adom.
lograte-device Display log rate by device.
lograte-total Display log rate by total.
lograte-type Display log rate by type.
logvol-adom Display log GB/day by adom.
msgrate Display message rate.
msgstat Display log message status.
status Running status.Â
Example:
Run 'get system loglimits' to see the unit's rated limits:
Â
get system loglimits
GB/day : 200
Peak Log Rate : 9000
Sustained Log Rate : 6000Â
Check the current log rate (the values are logs/sec averages for the last 5, 30, and 60 seconds):
Â
diagnose fortilogd lograte
last 5 seconds: 5009.8, last 30 seconds: 4757.8, last 60 seconds: 4545.2Â
Check the long-term log rate averages (the values are logs/sec averages for the last 1, 24 and 168 hours):
Â
diagnose fortilogd lograte-total
Totals Last Hour Day Week
-------------------------------------------------------
: 4455.2 4241.5 4357.4Â
Check the received log volumes per-ADOM:
Â
diagnose fortilogd logvol-adom "root"
2025-09-30 2025-09-29 2025-09-28 2025-09-27 2025-09-26 2025-09-25 2025-09-24 average
adom 'root':
49.16 GB 130.13 GB 128.05 GB 132.07 GB 155.21 GB 127.13 GB 139.06 GB 122.97 GBÂ
To review the log forwarding rate:
Â
diagnose test application logfwd 4
...
** Server#3: TEST-SERVER ld-TEST-SERVER Qid=21 Connected
src-intf:port2 bind: from 8d20h36m12s ago
srcip-update-ts changed
curr-msg-seqno=1785400942420
nmsg-sent=3002972 nlog-sent=38118712 send_timeout=0 send_err=0
conn_err=0 msg_append_err=0 unreliable-errno=0
rate in last 5sec, 30sec, 60sec
msg/sec: 103.6 94.9 94.7
log/sec: 4528.2 4404.3 4361.9
...