BreakingFixed
Metric names and units follow the conventions
A corrective release, but one that renames series. promtool check
metrics flagged 0.6.0: some were exported in milliseconds,
microseconds, hours or bits per second, where both the Prometheus and the
OpenTelemetry rules ask for seconds and bytes.
- Durations are now in seconds, throughputs in bytes per second, and
a list of gauges loses its
.total suffix. Dashboards, alerts
and recording rules on the old names need updating — the note carries the
full table.
- Zabbix item keys follow the metric names. Re-run
zabbix setup to refresh the templates; items under the old
keys stop receiving data and keep their history.
- The Zabbix server is set at install time —
ZABBIX_SERVER
for the MSI, --zabbix-server for config init, an
environment variable for the container. A new host registers and fills in
by itself.
- Topology. A route is identified by its destination and its next
hop, interfaces carry their subnets and addresses, Windows hosts publish
their routes, and SNMP devices no longer flicker.
- The console reports measured values. Resident memory and CPU are
now the real figures, with the Go heap shown beside them.
- Watch out on Linux:
senhub-agent update run by
0.6.0 installs the new binary without restarting the service — finish
with sudo systemctl restart senhub-agent.
Full release note, with the renamed metrics table →