Skip to Content
ConfigurationFiltersFilters

Filters

Filters allow you to customize rules for data recording. While you can completely disable events in prism.conf, filters allow finer control. Filters tell prism to allow or ignore events that match specific criteria - worlds, actions, materials, players, and more.

For example, many servers have harvest-only “resource” worlds which could generate millions of useless activity logs. No one really cares who mined dirt and stone in a resource world, which is where filters come in.

Filters help you avoid recording data that you don’t want. Reducing what gets saved to your database will improve performance and disk usage.

Writing Filters

Prism does not generate any filters by default. In prism.conf, look for the filters=[] config.

Every filter must have:

  • A defined behavior
  • At least one condition
  • enabled=true

The behavior determines if the filter will ignore or allow recording if the conditions are met.

filters=[
    {
        behavior=IGNORE
    }
]

The behavior property must be set to one of these choices:

  • ALLOW - Activities matching the conditions will be recorded.
  • IGNORE - Activities matching the conditions will not be recorded.

Debugging

Set debug-filters=true in prism.conf to log each filter’s per-condition result (MATCHED / NOT_MATCHED / NOT_APPLICABLE) and final decision for every activity.

storage.confConditions