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.

FormerIdeaCreator
Parents

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

    Also, for n-tier applications that run on several servers, shouldn't there be ONE application monitor that gives the status of the app no matter which piece on which ever server is running or having issues.

Comment

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

    Also, for n-tier applications that run on several servers, shouldn't there be ONE application monitor that gives the status of the app no matter which piece on which ever server is running or having issues.

Children
  • in reply to marunderwood

    I usually disable the component manually, but I can see how scheduling would make this better.

  • in reply to mcbridea

    Correct me if I am wrong but I believe that once you disable and save the Component, you loose the historical data from the previous monitoring of that Component.  Having the ability to just Unmanage it would be preserve that historical data.

    There is another advantage that I see with aLTeReGo's idea...  Currently I allow my users to Unmanage, within the web, Nodes and Application Monitors.  However I forbid them from editing the assigned Monitors and Templates.  Unfortunately I cannot give them access to do one without the other being available to them as well.  (see and vote there as well!!!)  When they run into a situation where they want just one Component disabled, they come to me and I disable it for them.  This feature would hopefully be outside of editing the Monitor and maybe on the Component Details screen like with Node and Application Monitor Unmanage, thus allowing me to give control over Component Unmanage to my users as well.

SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.

SolarWinds Customer Success Center Certification Media Vault Link Accounts
About THWACK Blogs For Government Edit Settings Free Tools & Trials
Legal Documents Terms of Use Privacy California Privacy Rights Security Information
©2024 SolarWinds Worldwide, LLC. All Rights Reserved.