get_health_metrics goes; SNMP_HEALTH_PROFILE declares uptime (TimeTicks, checked on swt-l2-3-38), CPU and memory as per-unit tables, first row as before.
Interface counters come from the 64-bit ifXTable where the switch has it.
Merge order: together with NetOrk/netork#1129 and the pin bump in netOrk. netOrk before #1129 only polls drivers that have their own get_health_metrics, so this driver alone would stop being polled. Part of NetOrk/netork#1105 / #1108.
- `get_health_metrics` goes; `SNMP_HEALTH_PROFILE` declares uptime (TimeTicks, checked on swt-l2-3-38), CPU and memory as per-unit tables, first row as before.
- Interface counters come from the 64-bit ifXTable where the switch has it.
Part of #4
**Merge order:** together with NetOrk/netork#1129 and the pin bump in netOrk. netOrk before #1129 only polls drivers that have their own `get_health_metrics`, so this driver alone would stop being polled. Part of NetOrk/netork#1105 / #1108.
The driver no longer collects over SNMP. SNMP_HEALTH_PROFILE states
where the switch publishes uptime (TimeTicks), CPU and memory (tables
with one row per stack unit, first row as before); the application
polls and computes (napalm-device-types docs/STRUCTURE.md).
Interface counters now come from the 64-bit ifXTable where the switch
has it, as the application reads them for every device.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
get_health_metricsgoes;SNMP_HEALTH_PROFILEdeclares uptime (TimeTicks, checked on swt-l2-3-38), CPU and memory as per-unit tables, first row as before.Part of #4
Merge order: together with NetOrk/netork#1129 and the pin bump in netOrk. netOrk before #1129 only polls drivers that have their own
get_health_metrics, so this driver alone would stop being polled. Part of NetOrk/netork#1105 / #1108.