Open for Voting
over 2 years ago

UnManage Component Monitors within an Assigned Application Template

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.

  • I have ... never used this functionality before I've always manually assigned templates, hand disabled components...  I've never heard of the slider existing and it working like this...I guess I should poke around the UI more emoticons_happy.png.  I read up on the docs and this is a nice thing to know emoticons_happy.png. Thanks for the info!

    As an aside: I think it would be good if templates could have all components "disabled" by default.  Currently it appears you have to have at least 1 of them "enabled" when you build a template, and some may be disabled anyway (you never know how they are set up without looking).  Then if you manually assign OR do discovery and it overrides the "disabled" status (internally, temporarily) just to do the discovery, and then it flips the override for that server to "Enabled" if it finds a monitor comes back "successful", and then lets you manually flip it if it fails but you know you want it to be enabled (maybe you need to manually configure that component or at the time of discovery an installed service is actually down for a moment but you want to monitor it).

    Then there could be a "loose best practice" for everyone to follow: disable all component monitors by default. Or maybe at least a feature in SAM to "set all components in X template to disabled" and "set all components in X template to enabled" to standardize them how you want in your environment.

  • Ah, that's probably what I'm doing wrong. I have it set to exact match, the default. I'll play around with the slider. I appreciate the input.

  • The slider determines how exact of a match the template needs to be in order to be applied. If you lower the slider from exact match it will apply the template on a partial match and automatically disable any components which will not work when the application template is applied.

  • True but sometimes you can't have them in a sub folder.

  • What I've found in my testing is that if it detects ANY of the component monitors in the template, it applies the entire template and doesn't disable the non-present monitors. Correct me if I'm wrong there. I might have done something incorrectly during my testing with application discovery. I'll re-test again and confirm.