Skip to content

0.16.0

Choose a tag to compare

@dsmorgan dsmorgan released this 24 Sep 17:17
· 6 commits to main since this release

Added

  • Load view: UniFi switch ports carry throughput (#53, from Sam /
    @slmingol). The controller reports a rolling byte rate per switch port,
    the same figure its own UI shows, and the collector now stores it as the
    port's in/out rate and as a rate_history sample. Switch-to-switch and
    switch-to-AP legs on UniFi-managed switches color in the load view and
    get a 24-hour peak, where before only SNMP-polled ports did. An AP's
    uplink carries the same figures and is stored too. A down device keeps
    its last good reading, as it does for port status and speed.

  • Load view: the busier end of a cable wins. Where both ends of a
    link report a rate, the edge used to show whichever end sorted first by
    name. The two ends read the same wire through different windows, a
    UniFi rolling rate against a five-minute SNMP average, so the edge now
    shows the higher reading, for the current figure and the 24-hour peak
    separately. A burst one poller caught no longer hides behind the
    other's average.

Changed

  • Deployment guide: verify snapshot delivery before you need it (#25).
    A new step walks through mounting the off-host share into both patchbay
    services, triggering one snapshot, checking the share from another
    machine for the renamed copy and no leftover .part file, waiting for
    the sync, and opening the off-host copy with the stack down.

Fixed

  • Rate samples age out whatever the source. The seven-day
    rate_history prune lived in the LibreNMS collector, so a site whose
    rates came from another source would have kept every sample forever.
    The normalizer's housekeeping pass prunes now, every cycle, beside the
    raw-payload expiry.

  • The test suite passes under bare pytest (#54, from Sam / @slmingol).
    Two test modules import helpers from a sibling through the tests
    package, which resolves only with the repository root on the path.
    python -m pytest puts the working directory there and plain pytest
    does not, so the same tree passed on one machine and failed eight tests
    on another. The pytest config adds the root now.