Assign SAM template to Group but only for applicable nodes?

Hey,

I have a template with 5 Windows Process Monitor components applied to a group.

I've noticed that all nodes inside the group got all the Process Monitors applied to them, regardless of if the process exists or not

I understand that breaking the template into multiple templates and making utlra specific groups would solve this issue, but it's a lot of micromanaging and manual labor. There will also be a lot of overlap among the groups since most of the nodes have more than 1 of said process running and we're talking about 100+ nodes here. I thought that maybe I could not find a way to create dynamic groups based on installed software, which would also solve the micromanagement issue, but from what I've found it's not possible.

Is it possible to apply a template to the whole group while at the same time make it such that a component is not applied if not applicable?

If not, is there a way to remove the useless monitors after the fact en-masse? Maybe a DB query? But I guess it's likely that the template will be re-applied since it's part of the group. Not really sure, we're new to the Software and still figuring our way around.

Find more posts tagged with

sam

process_monitor

sam templates

groups

Accepted answers

shuth

"Is it possible to apply a template to the whole group while at the same time make it such that a component is not applied if not applicable?"

The issue with this is depending on your template, SAM has no way of knowing what components are applicable or not. Is the software/component missing because it's not installed on that server on purpose or by mistake? Is the service/process meant to be stopped or is it a problem?

On the SAM settings page there is an option to Scan Applications - you can specify the servers to scan (can only filter by Node properties, not groups), what templates to scan with, and an option to define the match parameters (Minimal / Partial / Strong / Exact). Minimal = at least one component matches, I think Partial/Strong are 33%/66%, and Exact means all components have to match to apply the template to the node.

All comments

donrobert5

Have you tried to improve your grouping? You can create a nested group. Example, you can group all your Windows server, then nest a group under it for Windows group that are DNS, then apply the Component Monitor to the DNS group instead of the Windows one?

Can you also utilize the Custom property, I'm thinking adding a custom property condition apart from the grouping? I no longer have a SW environment so i can't verify the 2nd suggestion.

You can also assign and remove the assignments for groups and individual nodes from Settings >> All settings >> SAM Settings >> Manage Application Monitors. documentation.solarwinds.com/.../sam-managing-templates-sw1127.htm

I tried to to check the Orion Demo Site but those pages are disabled so you will need to play around yours. You can also utilize the SW Academy and utilize the virtual classrooms for training on how to fully utilize Server and Application Monitor.

customerportal.solarwinds.com/virtualclassrooms

shuth

MElefth

Yeah unfortunately the issue isn't on my end. Let me explain a bit better.

We have this software suite, let's call it X and X has multiple components. We, the server admins, were informed by the application administrators that each server has a role and thus has a specific component of X installed.

I created a subgroup for each component of X and assigned a Process Monitor on each group based on the process name of the component. Result? I noticed that some of the monitors were reporting a status of "down" so I went and checked the processes running on the affected machines and noticed that not only was that process non-existent, there were processes running from the other components of X as well. I then checked a few other servers at random and noticed the same thing there as well, hence why i mentioned a major overlap in my post.

MElefth

The application scanner sounds interesting. I'll play with it a bit and see if it works the way I want it

MElefth

Worked beautifully, will try to use asset tags to minimize the useless scanning since i cant use groups to select nodes.