Skip to main content
js2
Staff
Staff
September 30, 2021

Troubleshooting Tip: Local traffic logs tab shows no results

  • September 30, 2021
  • 0 replies
  • 37450 views

Description

 

This article describes how to resolve an issue where local traffic logs are not visible under Logs & Reports and the page shows the message 'No results'.

 

Scope

 

FortiGate.


Solution


Identify exactly where logs are displayed from in the unit.

 
In the above screenshot, the log location is set to the disk, so it is necessary to verify the log disk settings.
 
show full-configuration log disk filter
config log disk filter
set severity information        <----- Make sure severity is set to information.
set forward-traffic enable
set local-traffic disable       
set multicast-traffic enable
set sniffer-traffic enable
set anomaly enable
set voip enable
set gtp enable
set filter ''
set filter-type include
end
 
The 'local-traffic' option is set to disable due to which local-traffic logs are not showing in FortiGate.

Enable the option and verify the logs.
 
config log disk filter
    set local-traffic enable
end
 
In cases where said log location is memory or FortiCloud, follow these settings.
 
config log memory filter
    set local-traffic enable
end

config log fortiguard filter
    set local-traffic enable
end

Additionally, make sure to enable the following options in log settings.
 
config log setting
    set local-in-allow enable          <----- Show logs for traffic designated to FortiGate such as ping, management.
    set local-out enable              
<----- Show logs of traffic generated from FortiGate.
end
 
Traffic designated to FortiGate:
 
 
Traffic generated from FortiGate:
 

 

Note:

If per-policy local-in traffic logging is enabled, the allowed traffic, denied unicast traffic, and denied broadcast traffic logging do not need to be configured for the log settings. When traffic logging is enabled for the local-in policy, the denied unicast traffic and denied broadcast traffic logs will be included.

 

As of v7.6, Local Traffic Logging can be enabled on a Local-in Policy basis. This will allow more granular control over target logging on specific Local-in policies. In turn, this will reduce over-generalized logging. 

 

config log setting

    set local-in-policy-log {enable | disable}

end

 

In GUI:

Navigate to Logs & Report -> Log Settings -> Global Settings ->  Local traffic Logging -> Specify -> Log local-in traffic and choose Per Policy.

 

perpolicy.png

 

 

config firewall local-in-policy

    edit <id> <----- Point to the specific Local-in policy in question.

        set logtraffic {enable | disable}

    end

end

 

In the GUI:

Navigate to Policy & Objects -> Local-In Policy, choose the appropriate policy -> Edit, and enable Log violation traffic.

 

Screenshot 2025-09-24 144248.png

 

Related documents:

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.
Fortinet Flag the Hack. Wednesday, August 26, 9:00 AM - 5:00 PM ET, COSM, Atlanta, GA.
Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!