1. Proposed title of this feature request
Virtual Machines recognized as network Resources in the Topology view

2. What is the nature and description of the request?
Today, the Topology view of the Observability operator displays traffic between virt-launcher Pods.

While this is useful and helps integrate OpenShift Virtualization into the Observability operator, it is suboptimal. Instead of seeing virt-launcher Pods that are an implementation detail of OpenShift Virtualization, I would like to see VM objects that are the user-facing API.

With this RFE, I would like to:

• Hide virt-launcher Pod resources
• Add VirtualMachine as the new Source/Destination Kind
• Associate traffic that is flowing between virt-launcher Pods with VirtualMachines, in all the tabs in the UI

3. Why does the customer need this? (List the business requirements here)
Users want to use the Observability Operator to monitor traffic between their Pods and VMs. While it is possible to monitor VM traffic my looking at virt-launcher Pods, it is exposing implementation details and harms the UX.

4. List any affected packages or components.
Observability Operator