zzzz

You can add to groups Nodes, Applications, Components, and a bunch of different object types at once. So you can have a group with just the nodes and another with various applications that reside in those nodes or a mix of both (and can be used to have the group only go down if the application in one node and the node in…

Do note that root cause : A) can have multiple items B) do not have to be nodes (and thus might not have direct ip addresses) Either case, it would not have a single ip address attribute. I do not know if you can somehow add properties to each of the items in the root causes, but I'm guessing no. You can do it with a…

One issue I've had with AD groups is that the user used to search/verify for the group matters. As in, using a normal user account causes the group to be added but not allow those it in to login, but using another account (possibly a admin/service level) account works. The SW tech stated it has to do with permission levels…

One possible issue is that the variable names will depend on what object you are alerting on. The M part will change if you switch between alerting on groups, nodes, applications, etc. Ex: For Nodes, the node name is just M=Caption For Applications, it is M=Node.Caption For Components, it is M=Application.Node.Caption…