Sometimes it's necessary to unmanage an individual component within an Application Template but it's not desirable to unmanage the entire application template because you lose visibility into the availability and performance of the rest of the elements that make up the application. Today the only option available is to break component monitors up into multiple applications templates that can then be unmanaged individually. SAM should allow users the flexibility to unmanage individual components within an application template, both from within the web interface as well as through the Scheduled Unmanage utility.
Top Comments
This option should also be available when the template is assigned. That way, errors are not recorded immediately, before you have a chance to unmanage the components that do not apply to the particular…
I usually disable the component manually, but I can see how scheduling would make this better.
I've had to resort to moving some component monitors into separate templates in order to be able to unmanage them when needed.