Assets Not Allocated section in Perspectives meaning

Products

• CloudHealth

Issue/Introduction

When you begin creating perspective Groups, you initially start out with 100% of your assets "Not Allocated". This means that no assets within your cloud infrastructure have been assigned to a Group.  As you begin to create groups within your Perspective, the Assets Not Allocated count and percentage will begin to shrink. 

Assets Not Allocated is the catch-all group within each perspective.  When you start building a new perspective, this catch-all group contains all the infrastructure assets that are visible in the platform.  A user can leverage metadata (including tags) for any visible asset, to allocate the asset to a new or existing group.  This process will remove the asset from the Assets Not Allocated bucket.  No asset is counted twice within the confines of an individual perspective.

Note that not all assets can be tagged and taggable assets may not have tags applied.  This can lead to assets being bucketed in the Assets Not Allocated group as well.

Resolution

To minimize the Assets Not Allocated group, review the attributes of the unallocated assets and begin the process of merging them into their proper groups.  Keep in mind that not all assets can be tagged.  Also, the platform stores all historical assets for 12 months after termination/deletion, so those assets will also be part of the Assets Not Allocated count. Utilizing the Search box to query known attributes of created groups, such as a group's name, can help in regards to adding unallocated assets to their proper groups. 

Be advised that it is not expected or even possible in most situations to have all assets categorized.  In nearly all situations, there will be an Assets Not Allocated group present in created perspectives.