content updates
parent
ce704bf596
commit
10d8d4ea93
|
@ -23,18 +23,14 @@ After you've done that, you changes will automatically be loaded into zmfilter w
|
|||
|
||||
Check the ``zmfilter.log`` file to make sure it is running as sometimes missing perl modules mean that it never runs but people don't always realize.
|
||||
|
||||
|
||||
PURGE BY AGE
|
||||
|
||||
**Purge By Age**
|
||||
To delete events that are older than 7 days, create a new filter with "Date" set to "less than" and a value of "-7 days", sort by "date/time" in "asc"ending order, then enable the checkbox "delete all matches". You can also use a value of week or week and days: "-2 week" or "-2 week 4 day"
|
||||
|
||||
Save with 'Run Filter In Background' enabled to have it run automatically.
|
||||
|
||||
Optional skip archived events: click on the plus sign next to -7 days to add another condition. "and" "archive status" equal to "unarchived only".
|
||||
|
||||
Optional slow delete: limit the number of results to 3. If you have a large backlog of events that would be deleted, this can hard spike the CPU usage for a long time. Limiting the number of results to only the first three each time the filter is run spreads out the delete processes over time, dramatically lessening the CPU load.
|
||||
|
||||
|
||||
There are two methods for ZM to remove files when they are deleted that can be found in Options under the System tab ZM_OPT_FAST_DELETE and ZM_RUN_AUDIT.
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue