So, tags definitely need some serious rethinking. I currently see two types of "tags":
1. Tags that are applied to agents via installers or policies.
2. Tags that can be applied from the Admin Console to almost anything under the General Administration tab.
First: Tags are powerful. They can be used for grouping, policies, permissions, event rules, views and probably many other things I haven't touched on yet. They are pretty much the key to doing things to CIs.
Unfortunately, v9.5 of ProactiveNet still appears to be in a hybrid state between the CMA and Admin Console:
- Tags created in the CMA don't show up in the Admin console and tags in the Admin Console are not valid for use in policies.
- There isn't really a "repository of tags" that are selectable via a drop-down. You have to maintain a goofy spreadsheet so you know how things are tagged.
- BMCs best practice is to apply tags to agent installers and use scripts to modify tags on host operating systems. I think this is an older way to go.
- You can also tag things within a CMA Policy based on agent selection criteria. I believe this function should be improved upon greatly as it offers the potential for the most dynamic tagging capabilities.
I believe (in v9.5's current state) the best practice is to have two primary types of policies: A host tagging and grouping policy followed by the monitoring policies (using precedence for one over the other). I don't think tags should be applied directly to agent installers at all.
The current v9.5 downside to this is that you still have to manually update Agent Selectors but hopefully there is a future integration with either ADDM Discovery or the CMDB that allows us to get dynamic data from those sources. I've also found this is easier to maintain instead of working through a bunch Agent Installers.
Once you have established your Tagging Policy, you now have the tags available to establish any monitoring policies. And, to top it off, it is so easy to add/remove tags from the policy instead of working on the agent host itself running a silly script.
The other aspect to tags is the automatic Grouping of CIs from a CMA policy along with assigning permissions to CIs from a CMA policy. Both of these still need a little refining but that little Server Configuration screen in the CMA policy offers a ton of power for organizing your CIs in the Operations Console.
Does anyone else have some experience with Tagging and Grouping CIs in v9.5? How do you leverage the power of Tags without making it too manual?