Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-1017

Metrics: Top pod or service talkers

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • 5
    • False
    • None
    • False
    • NetObserv - Sprint 238, NetObserv - Sprint 239, NetObserv - Sprint 240, NetObserv - Sprint 245, NetObserv - Sprint 246, NetObserv - Sprint 247, NetObserv - Sprint 248

      Create new metrics to report top pod talkers as:

      • direction (egress / ingess)
      • kind (pod / service)
      • name
      • namespace
      • node name
      • owner name
      • bytes

      To create a new metric, a definition file must be added in https://github.com/netobserv/network-observability-operator/tree/main/controllers/flowlogspipeline/metrics_definitions , similar to the ones already there.

      For this metric, I would imagine something along those lines could work (not tested) :

      encode:
        type: prom
        prom:
          metrics:
            - name: top_pods_egress_bytes_total
              type: counter
              valuekey: Bytes
              filter:
                key: FlowDirection
                value: "1"
              labels:
                - SrcK8S_Name
                - SrcK8S_Namespace
                - SrcK8S_Kind
                - SrcK8S_Node
      

      And another one by destinations filtered on ingress

      I don't remember how to do the "Top" thing but I remember it's possible

              jtakvori Joel Takvorian
              jpinsonn@redhat.com Julien Pinsonneau
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: