Sorry fail - not sure. Is the mechanism of sending logs to forticloud documented somewhere? Believe me or not, we lost several messages during internet line congestion comparing to local logging. BTW. Do you think that plain syslog over TCP is the remedy for lost messages? Unfortunately not: linkNot saying you lost logs, but the transmission path is ssl over tcp and it' s documented here and i believe all logging is done with 514/tcp ( you can diagnose sniffer it and see that ) https://www.forticloud.com/com.fortinet.gwt.Main/help.jsp?locale=en_US%EF%BB%BF#communication Also depending on FortiOS you can use the diag test app miglogd 6 and verify counts for logging details being sent.
Company which is not listening to customers can' t be successful in long term.tell that to cisco and juniper they seem still be around
It ( forticloud ) isn' t the best but it does have some benefits. Fortinet has provide numerous alternatives some free , some local, some are via syslog. You have to pick what' s best for your setup.
You have to pick what' s the best for your setup.I did already. Local logging on device
, but I would be happy if the device could last longer than about one year...
tell that to cisco and juniper they seem still be aroundYes and no. I' m not involved in Juniper too much/too long. Cisco shines in routing&switching. But load balancers - gone. SIMS and MARS - gone. Firewalls - OK unless you need UTM or SSL VPN, than it' s different story (and price). Anyway, end of OT. Peace.
