Technical Tip: Log from FortiCloud source shows no results due to connection timeout

[btey]

Description
This article discusses when log is uploaded to FortiCloud server and when no log result is shown on FortiGate when the log source is set to FortiCloud.

Solution
1) Ensure the connection to FortiCloud server is established.

# diagnose test application miglogd 20
Home log server:
    Address: 172.16.95.92:514
Alternative log server:
    Address: 172.16.95.26:514
    oftp status: established        <-----
Debug zone info:
    Server IP:      172.16.95.92
    Server port:    514
    Server status:  up
    Log quota:      102400MB
    Log used:       673MB
    Daily volume:   20480MB
    FDS arch pause: 0
fams archive pause: 0

2) If the connection is established, it is possible to set longer connection timeout as below:

# config log fortiguard setting
    set conn-timeout {integer}
end

FortiGate Cloud connection timeout in seconds.   

Minimum value: 1
Maximum value: 3600
Default value: 10

Related documents.
https://docs.fortinet.com/document/fortigate/6.2.2/cli-reference/379620/log-fortiguard-setting
https://docs.fortinet.com/document/fortigate/6.2.0/cookbook/668197/log-related-diagnose-commands