-
Task
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
Request for sending data via telemetry
The goal is to collect metrics about features used by kubernetes-nmstate because nmstate team would like to priority the most used features in our develop and test plans.
<Metric name>
kubernetes_nmstate_features_applied
Labels
- dhcpv4-custom-hostname, possible value is integer
- dhcpv6-custom-hostname, possible value is integer
- iface-name-refered-by-sriov-vf-id, possible value is integer
- lldp, possible value is integer
- mac-based-identifier, possible value is integer
- mptcp, possible value is integer
- ovn-mapping, possible value is integer
- ovs-bond, possible value is integer
- ovs-db-global, possible value is integer
- ovs-db-interface, possible value is integer
- ovs-dpdk, possible value is integer
- ovs-patch, possible value is integer
- sriov, possible value is integer
- static-dns-name-server, possible value is integer
- static-dns-option, possible value is integer
- static-dns-search, possible value is integer
- static-hostname, possible value is integer
- static-route, possible value is integer
- static-route-rule, possible value is integer
- static-route-rule-suppress-prefix-length, possible value is integer
- iface-count10-plus, possible value is integer
- iface-count50-plus, possible value is integer
- iface-count100-plus, possible value is integer
- iface-count200-plus, possible value is integer
- iface-count500-plus, possible value is integer
The cardinality of the metric is at most 100. We might add more features in the future, but will limit them to 100.
Component exposing the metric: https://github.com/nmstate/kubernetes-nmstate
Not sure I understand the term of label correctly. Please check this link for example of nmstate metrics:
- relates to
-
OPNET-309 Telemetry for interface types in kubernetes-nmstate
-
- New
-