When you begin creating 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 to CloudHealth. 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.
Not all assets can be tagged, several assets that can be tagged are not, and many environments do not have a consistent tagging structure. This often time leads to several assets being bucketed in the Assets Not Allocated group. These Assets do not disappear from the reports but are simply bucketed into that group within a Perspective.
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, keep in mind that CloudHealth 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.
For more information on how to create Perspectives, see: How to Build a Perspective