If you defined custom processes to monitor in earlier versions of the PATROL Knowledge Module for UNIX, these processes are automatically migrated the first time that you load the KM; however, if you add customized processes after the KM is first loaded, these processes are not migrated and will not show up under the PROCESS_PRESENCE application class.
The workaround for this issue depends on whether or not you are using the PATROL Configuration Manager to manage your customizations. Select the process below that fits your scenario.
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks