Customers are trying to implement the Application Discovery in an environment where applications are started and stopped manually by the application admin.
Ideally the UMP Application Discover should discover the robots where the discovered application moves to and push the probes/profiles to the new robot (which does occur), but should then delete the probe/profiles and remove the robot from the Application Discover sub-group (which does not occur).
In these scenarios the environment is dynamic and the service/application can be started/stopped or installed/removed automatically by the system (load balancer) or application administrator.
Currently customers are having trouble using Application Discovery/ MCS to monitor those processes/services as they move all the time and create false alarms from the robot the application is no longer running on.
Encounter a situation where an application was removed from a server that was added to an Application Discovery subgroup in the UMP USM portlet. The application probe and enable profiles were pushed out to the device when it was first discovered.
Discovery should not see the application any longer but the application probe continues to generate alarms on this robot.
How do we configuration Application Discovery to remove the probe/profile from the robot and remove the robot from the Application Discovery sub-group when the application is removed from the robot?
Enhancement Request - this functionality is not currently built into the UMP USM Application Discovery feature