1. Proposed title of this feature request

VM-Centric Views in Network Observability

2. What is the nature and description of the request?
Network Observability currently is only a pod-centric view of OpenShift.  Virtual Machine administrators typically don't think of things in Pods, and as such aren't going to look at things the way we do currently (found by looking at owner).  The request is: 

• In the quick filters have an option for 'Virtual Machines'
  • When this filter is applied the Virtual Machine Instance objects should be shown (like the VM name)
• When viewing the topology the item that shows primarily should be the VM Name, potentially with the project under it (like it is for others)
• When building a topology with this filter applied, you should be able to see VM's clearly identified and external communication should be shown as IPs (like it does under the resource filter)

I understand that a filter may just be a part of this solution, it may be worth considering creating a fifth display level for Virtual Machines (currently node,namespace,owner,resource), or updating the resource level to more accurately reflect the requested changes.  I can think of very few instances where an administrator would care more about the virt-launcher pod than the VMI.

3. Why does the customer need this? (List the business requirements here)
Our platform is increasingly being used by Virtual Machine administrators.  As such we need to provide clear and familiar ways for them to utilize and interpret data our platform provides for a good user experience.

4. List any affected packages or components.
Network Observability Operator