Group applications by customer?

Question

Under All Applications in SAM Summary, I am trying to filter as follows:

Customer A

- AppInsight for IIS

- Server 1

- Server 2

- Custom Application for Customer A

- Server 3

- Server 4

- Shared Application

- Server 5

Customer B

- AppInsight for IIS

- Server 6

- Server 7

- Custom Application for Customer B

- Server 8

- Server 9

- Shared Application

- Server 5

In this example, the application on Server 5 is used by both customers, so if it goes down, I need to see both customers affected. Any ideas how I can do this? For the rest of the servers I can filter by node customer, but I can't add multiple node customer fields to one server, can I?

tonedepear · Answer

I use groups for this. Devices can be in more than one group, and groups can be nested, so then I have a services panel in a dashboard with all the groups listed, as soon as something goes awry with any of the devices then all the groups containing that device flag up.I have a separate dashboard Services with Problems (subtitle "This list should be empty" !) so any group with issues pops in to that list also. I also have tabs by group down the left side to access individual customer dashboards but that's probably overkill for this. Then the dashboard view is restricted to the Single parent group which all the other groups are in, see last image. Hope that makes sense/is of use.

(Scuse all the censoring in the images, I like my job!)

jorich · Answer

If you are married to the All Applications resource for this, it looks like there may have to be a compromise on appearance to get your functionality because of the grouping options being limited to Node and Application properties.  I have several examples of different business teams with shared interests in the same server (e.g. Database and Application team).  I use a node CP called TeamAssociation and populate it with Team names delimited with semicolons (if there are multiple teams - otherwise just the one).  In this instance, you would group on that property at the top level.  It will roll the status up to show you the two customers affected, it just isn't quite as pretty a layout as you have defined.

Customer A

- AppInsight for IIS

- Server 1

- Server 2

- Custom Application for Customer A

- Server 3

- Server 4

Customer B

- AppInsight for IIS

- Server 6

- Server 7

- Custom Application for Customer B

- Server 8

- Server 9

Customer A; Customer B

- Shared Application

- Server 5

garyblack · Answer

Personally I think it makes more sense to use groups for this purpose.

I.E Group for each customer and then a subgroup within that for the applications, you can then have multiple servers in multiple groups.