An AdminCollection node is a collection of elements that are administered together.
The following section describes the scenarios in which an AdminCollection node is created or removed.
AdminCollection node life cycle
The attributes of an AdminCollection node contain stable information about the collection of elements such as type of the elements that are administered, count of the trigger. AdminCollection node inherits its attributes and relationships from the Collection node.
AdminCollection nodes are used to represent a collection of resources such as VMs, Load balancers, and databases. These resources are administered as a group, such as an Amazon Web Service VPC, or an Azure Resource Group.
An AdminCollection node is created from data collected from the cloud API call.
An AdminCollection node is destroyed when it no longer exists in the API data. Aging is not applied to this type of node kind.
AdminCollection node attributes
The attributes of an AdminCollection node are as described in the following table below:
Attribute name and
Globally unique key.
Name of the detail.
Type of the detail.
Not displayed in UI.
AdminCollection node relationships
The relationships of an AdminCollection node are as described in the following table:
Cloud Region where this service resides.
Hosts that are a member of this Collection.
MFParts that are a member of this Collection.
Business Application Instances
Business Application Instances that are a member of this Collection.
Software Instances that are a member of this Collection.
Virtual Machines that are a member of this Collection.
Load Balancers that are a member of this Collection.
Collections that are also a member of this Collection.
Collection that this collection is a member of.
Pattern that is maintaining this Collection.
Cloud Service for this Collection.