--- title: Running process filters description: Filter any processes, using combinations of name and key parameters, from coming back to the instance. Out-of-the box, you can filter OS processes. Filtering processes helps reduce the number of records created, updated, or deleted in the database which can improve overall database performance. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/discovery/run-process-filters.html release: australia product: Discovery classification: discovery topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Advanced Discovery configuration, Configuring Discovery, Discovery, ITOM Visibility, IT Operations Management] --- # Running process filters Filter any processes, using combinations of name and key parameters, from coming back to the instance. Out-of-the box, you can filter OS processes. Filtering processes helps reduce the number of records created, updated, or deleted in the database which can improve overall database performance. ## Before you begin Role required: discovery\_admin or admin ## About this task To add processes to the filter, you must setup configurations using the Running Process filter record \[running\_process\_filter\]. These records make sure the filtered processes do not populate the Running process \[cmdb\_running\_process\] table. ## Procedure 1. Navigate to running\_process\_filter.list. 2. Select **New** to create a record. The form and descriptions are explained below. \[Omitted image "running\_process\_filter\_record.png"\] Alt text: Running process filters form
| Field | Description |
|---|---|
| Active | Check the box to include or exclude. |
| Name | Name for the record. |
| Description | Short description of the record. |
| Category | A name for the configuration type. Running process filters can be grouped however you want so that it's easier to identify and choose in the table. |
| Probe | Mandatory field. Which probe will use this filter. Often Linux or Windows active processes or ADM enhanced. When the probe executes, the instance sends the running\_process\_filter records as a probe parameter. The probe then uses this to filter the results before sending the information back to the instance. |
| Discovery Schedule | You can apply the filter on a specific Discovery schedule. If you leave this field, it applies to all schedules, even Quick Discovery. |
| Filter | Any process matching the filter will not be added to the Running Processes \[cmdb\_running\_process\] table. For example, if you want to filter all svchost.exe processes except the svchost.exe process for IIS classification, the filter definition would be: - name is svchost.exe - parameters does not contain iissvcs For information on setting filter conditions see: [Condition builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/c_ConditionBuilder.md) |
| Case sensitive | Applies to the Filter field. If case sensitive is checked, the filter may pull more or less information than you want. Default is off. |
| OOB filters | There are Linux and Windows filters to choose from. See [Out-of-the-box process filters](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/out-of-the-box-process-filters.md) for more details. |