-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
Product / Portfolio Work
-
None
-
0% To Do, 50% In Progress, 50% Done
-
False
-
-
False
-
None
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
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
This feature will address adding any new metrics to the k-nmstate operator. Exposing those metrics for telemetry will be worked on in https://issues.redhat.com/browse/OCPSTRAT-1838
Expected Results (what, how, when)
Post Completion Review – Actual Results
++
- blocks
-
OCPSTRAT-1838 Telemetry for interface types in kubernetes-nmstate
-
- New
-
- is related to
-
OPNET-309 Telemetry for interface types in kubernetes-nmstate
-
- New
-
- links to