cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post

UnManage Component Monitors within an Assigned Application Template

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.

31 Comments
Product Manager
Product Manager

Applications that are unmanaged never results in data loss, aside from historical data that's eventually purged out of the database as part of nightly maintenance. So if you unmanage an application (or a node for that matter) longer than your retention period, you'll end up with no historical data in the database. That does not however, delete the node, application, etc.. itself. As soon as the object is remanaged it will once again begin polling data.

What I'm worried is going on is that some people are disabling components within an assigned application as a workaround for not having the ability to unmanage individual component monitors. Disabling a component does delete all historical data for that component immediately. So long as you know that and are making an educated decision that's fine, but I don't want anyone accidentally losing historical data because they thought they found a neat workaround for unmanaging individual component monitors. 

Level 14

Thanks for clarifying that.  That is what I thought and I have been looking for some way to just what you say with disabling components.  My main requirement was to be able to disable certain Scheduled Tasks but leave others to be monitored.  At present it is all or nothing.  I spoke to Kevin Sparenberg about this at London SWUG who said it was something that was being both asked for and looked at.  At the time we had a lot of scheduled tasks that were set to run one per week but would report as failed when they didn't run daily.  More granularity would have been great.  I have moved jobs since then.

Level 12

Yes...  My mistake, I was thinking of somethings else.  Sorry.

I still don't like Unmanage.  I would rather data was still collected, when it can be, during maintenance windows.  It can be helpful for analyzing issues that started during the maintenance window.  Having the ability to Mute Alerts allows that to happen.

I do agree with what aLTeReGo​ said as well.  Users need to be trained on the best approach for a situation.  However even with the training I find they still would rather just Unmanage Nodes than Mute Alerts.  Then they come to me and ask if they can get to the data that wasn't collected during the Unmanaged period.  I would rather just not have the option to Unmanage be available to them.  The same would hold true for Component Monitors or anything else the Orion modules are monitoring.

Level 9

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.

Product Manager
Product Manager

What you describe is exactly how application discovery works today.

Product Manager
Product Manager

Windows Scheduled tasks which are in a sub-folder are automatically ignored by SAM's Windows Scheduled Task Monitor.

Level 9

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.

Level 14

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

Product Manager
Product Manager

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.

Level 9

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.