Implemented

Automated Adding of Application Templates Based on Group Membership

In the hopes to increase automation for IT, it would be GREAT if SAM could automatically add a set of templates to a host based on group membership

Below are some example rules:

- If a host is identified as being WINDOWS, add the Windows Server Services and Counters template

- If a host is added to a group called "Exchange Servers in Washington DC", add the Exchange Monitoring Template

By automatically adding specified monitor templates based on already defined group criteria, we are reducing the amount of manual work that the Monitoring admin needs to perform, and reducing the potential for forgetting about a template that should have been assigned. This extra piece of automation - especially when combined with dynamic group memberships is hugely powerful.

  • This may not be Jason's intention, but having a default set to monitors for a specific vendor type would be helpful.  I add the same 3 monitors to all my windows servers when I add them (A/V, SCCM Client and Windows monitors), so it would be nice if they could get automatically added to all windows servers. 

  • How do you see credentials working within groups? Would you rely solely upon credentials embedded within the application template itself, or would you imagine assigning credential to a group somehow? I'd mention node credentials for nodes that are managed via WMI but there are a great number of templates this wouldn't work for such as MySQL, Oracle, etc.

  • No, I would not expect any sort of magic detection and assignment based on what is installed on the system - because you are right ... there are many scenarios for many situations ... machines on and off the domain, different versions of applications, and even the same application running on multiple machines - but managed by different teams and therfore requiring different alerting thresholds.

    I would envision that the templates are assigned to the groups manually, to allow the Admin to specify what they actually want per group. This would essentially allow a one-time configuration per group of how you want everything IN that group monitored. The adding and removing nodes to the group is done as normal.

  • I like the way you're thinking, but I'm curious how you would expect certain conditions to be handled. From your example, if the node is part of the Exchange group, add the exchange template. But which? One you would define for the group manually? Since there are several different Exchange role types, and multiple templates for each role, do you have the expectation that Orion would know which exchange role was running each node in the group and assign the corresponding template accordingly?

    As most environments have a mix servers that are joined to the domain, and those that are not, and environments with multiple domains, how do you foresee credentials being handled for these templates?

    I'm asking, not because I'm being a punk, but rather as a Product Manager who must grapple with these very questions.