sensor-snmp: counter semantics — rates, wrap/reset detection, units, typed syntax #527
Labels
No labels
area:frontend
area:gui
area:transfer
area:zenoh
breaking-change
bug
correlation
deployment
documentation
duplicate
enhancement
good first issue
help wanted
invalid
keyspace-v2
netring-0.27
netring-0.28
netring-0.29
nlink-0.24
performance
priority:p0
priority:p1
priority:p2
prototype
question
redesign
rerun
research
security
sensor:logs
sensor:netlink
sensor:netring
sensor:parallax
sensor:snmp
sensor:sysinfo
sensor:systemd
v3-roadmap
wave:0
wave:1
wave:2
wave:3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
marcpardo/zensight#527
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #525.
Problem
snmp_value_to_telemetry(zensight-sensor-snmp/src/poller.rs) publishes raw wire values with no semantics:Counter(hundredths of a second) instead of a duration.OidEntry.syntax(Counter32/Gauge32/... from the MIB table,mib.rs) is stored but never used for typing or scaling.TelemetryPointcarries no unit metadata anywhere (zensight-common/src/telemetry.rs).Proposal
if/1/ifInOctetsstays, addif/1/ifInOctets.rateor arate=per_secondlabel — pick one convention and document it indocs/reference.md).Gaugeseconds.syntaxto drive typing/scaling instead of relying solely on the wire tag.TelemetryPointwith an optionalunitfield (serde-default, CBOR-tolerant) or standardize aunitlabel — decide in-issue; breaking the wire model is allowed (coordinate with exporters + GUI).Acceptance