Details

Epic Design/Requirements: Documents

Other info

The current plan here is to try to leverage the Network Observability Operator (another RH product) we have started communicating with them and it sounds like they may have all the features we require in there June/July release this year.

We should follow up again closer the time and start building some designs around what this could look like for future Cost Management integration work.

Notes: 

• Moving from Loki to Prometheus (1.5 is the current release)
• 1.6 will operate without Loki. Not everything but hopefully what we need.  Early June trying to align with OpenShift dates but OLM operator so it doesn’t have to.
• Will be able to create your own metrics out of flow logs
• Identify sub-nets also being added in 1.6
  • Flow metrics: https://github.com/jotak/network-observability-operator/tree/custom-metrics-dashboards/config/samples/flowmetrics
  • Subnet labels: https://github.com/netobserv/network-observability-operator/blob/main/docs/FlowCollector.md#flowcollectorspecprocessorsubnetlabels-1 
• We can install nightly builds:
• Slack channel: #forum-ocp-network-observability
• JIRA: NETOBSERV (Project). Engineering team
  • PM Team Uses:
• Lower cost or tax to run the topology viewer. Looking at a non-loki version of this.

Target Dates

Dev Complete :

QE :

UI: