Open for Voting

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.

Parents
  • You can remove the individual component monitors for specific nodes. I created a template, applied it to many server and went into each node to remove the component monitors that I did not need for that node.

  • What I'd like to see is some improvement with the windows service monitor specifically. If when adding this component monitor to a node via a template it will detect if the service exists and automatically disable that component on that node if not present.

    Currently I have templates built out by application and they contain everything for that application. Multiple nodes have components that make up the entire application so I find myself disabling up to 70% of the components for some nodes. Having the windows service monitor auto-detect presence would help in this tremendously. It's a start, but ultimately I'd like to have an option to disable any component monitors that fail a test when a template is assigned. That way it would make it easier for me at least in that regard. Just an idea.

  • What you describe is exactly how application discovery works today.

Comment Children
  • 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.

  • 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.

  • 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.

  • 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.