Epic Goal

• Add PktDrop, DNS, RTT metrics
• Add Resource (Pod / Service) metrics
• Ensure users understand the performance impacts
• Document these impacts

Why is this important?

Since 1.4 release, netobserv allow installation without Loki. To keep the ability to drill down into DNS & PktDrop, we should expose these in Prometheus metrics.

It's also a good opportunity to add the RTT ones that will be supported in 1.5 and update the flow dashboards accordingly.

Before exposing metrics that can kill the cluster performances, we should ensure it is explicitly requested in the CR and the user understand the impact.

Planning Done Checklist

The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

• Priority+ is set by engineering
• Epic must be Linked to a +Parent Feature
• Target version+ must be set
• Assignee+ must be set
• (Enhancement Proposal is Implementable
• (No outstanding questions about major work breakdown
• (Are all Stakeholders known? Have they all been notified about this item?
• Does this epic affect SD? {}Have they been notified{+}? (View plan definition for current suggested assignee)

Additional information on each of the above items can be found here: Networking Definition of Planned

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement
  details and documents.

...

Dependencies (internal and external)

Followup on:

https://issues.redhat.com/browse/NETOBSERV-1009 

https://issues.redhat.com/browse/NETOBSERV-139 

https://issues.redhat.com/browse/NETOBSERV-1284