Skip to main content
WinterSnowYap
Staff
Staff
December 3, 2025

Troubleshooting Tip: FortiAnalyzer custom report filter not working due to missing 'filter' info at dataset

  • December 3, 2025
  • 0 replies
  • 274 views
Description This article describes how to troubleshoot a FortiAnalyzer custom report filter when it is not working because of the missing 'filter' info in the dataset.
Scope FortiAnalyzer.
Solution

Below is the scenario:

At FortiAnalyzer (Device Manager), 2 FortiGates have been added.

 

For example:  

  • 'FGT_HQ'.
  • 'FGT_Branch'.

 

202512_FAZ custom report filter_001.jpg

 

At FortiAnalyzer, the '10.100.5.172' IP address is only inside 'FGT_HQ' logs.

 

202512_FAZ custom report filter_002.jpg

 

At FortiAnalyzer, the Dataset information is as follows.

 

202512_FAZ custom report filter_003.jpg

 

At FortiAnalyzer, generate the report, and the result shows more information that is not included in the filter for FortiGate.

Below is the comparison between 2 different datasets and 2 different results.

 

202512_FAZ custom report filter_004a.jpg

 

202512_FAZ custom report filter_004b.jpg

 

Correct the dataset as follows:

 

SELECT

          from_dtime(dtime) as time,

    devname,

    policyid,

    srcip,

    dstip,

    hostname,

    catdesc,

          utmaction

FROM

          $log

WHERE

          $filter AND utmaction = 'block'

ORDER BY

          dtime DESC


Related article:
Technical Tip: How to create FortiAnalyzer reports using custom SQL queries

    Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
    Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!