You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expose a subset of opte kstats as oximeter metrics, limited to uft and
route cache metrics initially. We track each opte port in sled-agent so
that we can collate control plane metadata (nic id, parent id, etc.)
with kstat values.
Part of #10892.
Note: this is mostly a mechanical change, extracting more metrics from
opte's new kstats. We already know how to track and untrack links, so we
can mostly reuse that logic. I think the interesting parts are which
metrics to include (I'm proposing a subset related to uft and route
cache performance and occupancy) and how often to sample them (I'm using
the link sampling interval of 10s for now). It's easier to add features
than remove them, so I'd like to identify the minimal useful set of opte
metrics for now, then think about expanding the set later on.
Marking as draft while I deploy to a racklette for testing, and write up
notes on cardinality.
0 commit comments