

Urlsum: 2.00%, 0.314 GB Expiration-period: 0 days Weeklytrsum: 1.00%, 0.157 GB Expiration-period: 0 days Hourlytrsum: 3.00%, 0.472 GB Expiration-period: 0 daysĭailytrsum: 1.00%, 0.157 GB Expiration-period: 0 days Trsum: 7.00%, 1.100 GB Expiration-period: 0 days Threat: 16.00%, 2.515 GB Expiration-period: 0 days Traffic: 30.00%, 4.716 GB Expiration-period: 0 days Hip-reports: 1.00%, 0.157 GB Expiration-period: 0 days Where "number of days" = show system logdb-quota # set deviceconfig setting management report-expiration-period

Where "log type" = traffic / threat / trsum / etc. # set deviceconfig setting management quota-settings log-expiration-period You can use CLI commands to configure an expiration period or review the current retention time: The appliance deletes expired reports nightly at 2 A.M. By default, there is no expiration period, which means reports never expire. This sets the expiration period (in days) for reports (also here the range is 1 to 2000). By default, there is no expiration period, which means logs never expire. The appliance evaluates logs during creation of the logs and then deletes logs that exceed the expiration period or quota size.įor reports, you will find a similar setting under Device/Panorama tab (1) > Setup (2) > Management (3) > Logging and Reporting setting (4) > Log Export and Reporting tab (5). The range can vary from one to 2,000 days across all platforms. The firewall or Panorama appliance automatically deletes logs that exceed the specified period. You can find this setting under Device/Panorama tab (1) > Setup (2) > Management (3) > Logging and Reporting setting (4) > Log Storage tab (5) This allows you to configure an age-out period for each and every log type and all reports and adds more control to your expiration/retention.

We've grown since the olden days and a feature using 'Max Days' was added. Oldest logs were deleted whenever a quota was reached until we reached the configured quota size for the given log type. Older PAN-OS had a purging logic which was checked against the logdb quota and the predefined quota size for reports. This week's Tips & Tricks columns talks about a nifty little feature that allows you more control over log expiration/retention.
