About Log Monitor data filtering sequences

Site coordinators can use the Log Monitor Policies form to add multiple filter policies and override filter policies written in the configuration file. By creating filter policies, you can reduce the amount of log data collected and stored in the servers and still have the option to generate data logs for specific uses at runtime. For example, at any point, you can create a filter policy to collect data for use in diagnosis, without the need to cycle servers or to change configuration files.

Note: These filter settings apply to the entire server farm.

To add filter policies, a site coordinator must use the Log Monitor Policies form in the Site Coordinator Configuration.

A filter policy is added to a sequence in the grid view of the Log Monitor Policies form. Multiple active filter policies are executed according to the defined sequence. Filter policies with greater sequence numbers are executed before policies with lesser sequence numbers. For example, in a scenario where there are three defined sequences with sequence numbers 1, 2, and 3, the filter policy with sequence number 3 runs first, followed by sequence number 2, and finally, sequence number 1. If no filter policy is created or if no sequence is set to active, then the existing rules defined in the app.config file are applied.

You can set filter criteria according to any combination of Source, Type, and Regular Expression. You can also include or exclude filter criteria according to your preference or need.

You cannot duplicate a sequence, but you can modify existing filter policies according to your requirements.