Description: 

The parent of the current Jira is https://issues.redhat.com/browse/SWATCH-3360 . There, It was pointed out ( as also mentioned here ) that, It's expected to see same RHEL-Based hypervisor reported twice with same exact socket count displayed, where

• one entry is displayed as Physical and is for the node’s own copy of RHEL that is used as the operating system to run the hypervisor
• the other entry is displayed as Hypervisor and is for the RHEL that is used by the guest systems ( contributing towards the usage\capacity for the virt-who required subs ) 

An example of what we can see in https://console.redhat.com/subscriptions/usage/rhel would be this 

Name                            Guests              Type              Sockets              Last Seen
rhvh.example.com                8                   Physical          4                    <some date>
rhvh.example.com                8                   Hypervisor        4                    <some date>
VM.example.com                  --                  Virtual           1                    <some date>

Requirements raised by the end-user :

The data we export right now, including the RHV\RHEL-H duplicates mentioned, makes it very complicated for the end-user to calculate the exact socket usage for individual types of systems. These are the two things proposed for further improvements: 

1. There is no need to show the "Guests" count for the "Physical" type entry. It only makes sense to show it for the "Hypervisor" entry.
2. The end-user proposes the view to be something like this instead of what we see right now i.e. 

Name                     Virtual       Physical       Hypervisor       Public_Cloud       Guests              Sockets              Last Seen
rhvh.example.com         No            Yes            Yes              No                 8                   4                    <some date>
VM.example.com           Yes           No             No               No                 --                  1                    <some date>

This not only helps to avoid the duplicated entry for the RHEL-based hypervisors but also allows the end-user to easily filter the data as needed, to finalize their subscription requirements for the  year-end renewals. 

NOTE: The end-user has 300+ RHV hypervisors in their infra and they are pretty frustrated by the way, Sub-Watch shows the data at present ( whether in UI or in Exported csv ).

I will be adding the recording of the part of the discussion with end-user that led to this feature request, in a private comment.