This article describes the changed behavior of miglogd and syslogd on v7.0.
Scope
FortiGate v7.0.
Solution
Before v7.0, the Syslog sent an information counter on miglogd:
diag test app miglogd 6 2024-04-29 12:17:15 mem=61774201, disk=61657447, alert=0, alarm=0, sys=123548402, faz=0, faz-cloud=0, webt=0, fds=0 2024-04-29 12:17:15 interface-missed=237047 2024-04-29 12:17:15 Queues in all miglogds: cur:0 total-so-far:0 2024-04-29 12:17:15 global log dev statistics: 2024-04-29 12:17:15 syslog 1: 2024-04-29 12:17:15 sent=61774203, failed=02024-04-29 12:17:15 , cached=0, dropped=0 2024-04-29 12:17:15 , relayed=02024-04-29 12:17:15 2024-04-29 12:17:15 syslog 2: 2024-04-29 12:17:15 sent=61774203, failed=02024-04-29 12:17:15 , cached=0, dropped=0 2024-04-29 12:17:15 , relayed=02024-04-29 12:17:15
After v7.0 use ‘diagnose test application syslogd 4’.
diag test app syslogd 4 syslog=336, nulldev=0, webtrends=0, localout_ioc=370, alarms=0 global log dev statistics: syslog 0: sent=336, failed=0, cached=0, dropped=0 localout-ioc statistics in root: sent=0, failed=1, cached=0, dropped=217