---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Running process filters

# Running process filters {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

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, admin

## About this task

To add processes to the filter, you need to 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. Click New to create a new record.  
   The form and descriptions are explained below.

   {#run-process-filters__table_rxm_mty_rxb__entry__2}

   | Field | Description |
   |-|-|
   | Active | Check the box to include or exclude. |
   | Name | Name for the record. |
   | Description | Short description of the record. |
   | Group | A name for the configuration type. Running process filters can be grouped however you want so that it 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 cmdb_running_process table. For example, if you wish 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 {#run-process-filters__ul_dlc_45y_rxb} For information on setting filter conditions see: [Condition builder](https://www.servicenow.com/docs/access?context=c_ConditionBuilder&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) |
   | 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://servicenow-prod.fluidtopics.net/5MWZZf0kKfJfAqFxI_5EBg "There are a variety of Linux and Windows out-of-the-box running process filters that are turned on and used for filtering processes.") for more details. |
   [ ]

   {#run-process-filters__table_rxm_mty_rxb}
3. Enter the details and click Submit.
* **[Out-of-the-box process filters](https://servicenow-prod.fluidtopics.net/5MWZZf0kKfJfAqFxI_5EBg)**   
  There are a variety of Linux and Windows out-of-the-box running process filters that are turned on and used for filtering processes.