-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFE] Collect nmstate usage data for telemetry #1202
Comments
@cathay4t about first bullet we can generalize this by counters per nested interfaces ? like |
Initially, I would like to collect date for:
Each cluster only count as one for topology/feature/use case regardless how many interfaces it has or how many NNCP it has. So our data does not imfluenced by a big cluster with 1000+ VLANs or NNCPs. I will create demo like topologies:
- vlan
- linux-bridge-over-bond-over-sriov-vf
features:
- nm-global-dns
- mac-identifier
- sriov-vf-reference
- ovn-mapping
use-cases:
- edit_static_ipv4_address_and_prefix
- disable_static_ipv6 |
Just a note that when I've had conversations about telemetry in the past, I was told the amount of data we're allowed to send for it is extremely limited. Like instead of JSON booleans, we have to use bitmasks where each bit is mapped to a given key. I haven't actually confirmed that myself, but before we come up with a complex set of values that we want to return we may want to confirm that we can actually represent that in the amount of data we're allowed to send. |
@cybertron @cathay4t this is poc to integrate some statistics, from there we can reduce optimize what we need Looks like the top 10 can be filter at prometheus using |
We are hoping to get data on
This could help us on planning CI coverage and backport patches.
The text was updated successfully, but these errors were encountered: