Uploaded image for project: 'On Prem Networking'
  1. On Prem Networking
  2. OPNET-309

Telemetry for interface types in kubernetes-nmstate

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • Telemetry for interface types in kubernetes-nmstate
    • BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-1838 - Telemetry for interface types in kubernetes-nmstate
    • OCPSTRAT-1838Telemetry for interface types in kubernetes-nmstate
    • 100% To Do, 0% In Progress, 0% Done

      Outcome Overview

      Once we have metrics on how customer networking environments are configured we will be able to make better decisions on priorities for future features.

       

      This was a request that was brought up by mcurry@redhat.com . We want to better understand what our customer networking environments look like and to do that we need metrics that can be reported via telemetry. This will most likely be done by querying the kubernetes-nmstate NodeNetworkState record and pulling metrics like number of ethernet interfaces, number of bonds, number of vlans, etc.

      Success Criteria

      It should be possible to look at telemetry data and determine things like what percentage of customers are using bonds or how many customers are using single nics versus how many have multiple nics.

       

       

      Expected Results (what, how, when)

       

       

      Post Completion Review – Actual Results

       ++ 

       

              mkowalsk@redhat.com Mat Kowalski
              bnemec@redhat.com Benjamin Nemec
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: