This documentation space contains information about PATROL Agents when deployed in a BMC Helix Operations Management environment. If you are a TrueSight Operations Management user, see PATROL Agent 22.1. Open link

Example of filter processing logic for disabling KMs

In the disabledKMsArch Agent configuration variable, enter the following list separated by commas:

/NT/.*/,/CentOS/.*, /NT/!NT_CPU,NT_MEMORY/,/!CentOS/CentOS_QUEUE.*,CentOS_PROCESS.*/}}


The Windows Agent builds three filters as follows:

  • Positive filter (/NT/.*/,/AIX/.*,/CentOS/.*) — disables (does not load) all KMs on all Windows and CentOS systems
  • Negative filter (/NT/!NT_CPU,NT_MEMORY/) — does not disable (loads) CPU and memory applications on Windows systems
  • Implicit Positive filter (/!CentOS/CentOS_QUEUE.*,CentOS_PROCESS.*/) — explicitly enables (loads) the CentOS queue and process applications on CentOS systems, which implies that these applications are disabled (not loaded) on Windows systems


For all monitored systems, the PATROL Agent loads the CPU and memory applications on all Windows systems. When the Agent loads these applications depends upon each application's status (preload, static, and dynamic).

Was this page helpful? Yes No Submitting... Thank you