All Release Notes Reporter for FortiGate 1.0.1.32 (2020-03-11)

• Fixed an issue that may prevent Search Term Alerts from working after the alerts are edited. If you’re experiencing this issue, edit your Search Term alert, and make sure the filter for Site Resource with the values /s and /su are set to ‘Not equal to’. There was an issue where this portion of the filter would be set to ‘Equal to’ if the alert was edited and saved, preventing the alert from working correctly.
• Fixed issue that may result in out of memory issues after startup when the data retention policy attempts to calculate the size of old /closed indexes.
• Elasticsearch no longer writes out enormous heap dump files when it runs out of memory. Any existing heap dump files will be deleted when disk space gets low.
• Installation now cleans up Elasticsearch package extraction temporary files even if the extract fails.
• Fixed issue in Alert Settings where the Alert Evidence Config Table sets example data to ‘User’ after the table is loaded.
• Added support for the slightly different FortiGate logs available from AT&T’s hosted FortiGate solution.
• Referrer URL is now loaded from the Rawdata field if the referrer field is blank. The Rawdata field is logged if you have `set extended-log enable` on your web filter profiles, and your syslog server is set to ‘reliable’. See the Getting Started Guide for Fastvue Reporter for FortiGate for more information.

Download Latest Update