Repository navigation
Add Airtime by Band, RF Spectrum and Signal Scope widgets for the NOC Builder - #53
Merged
Merged
Conversation
… Builder Publishes three Dashboard visuals that had no widget: fleet airtime per band over time, the radios placed in the 2.4, 5 and 6 GHz spectrum, and every client by access point and signal strength. RF Spectrum and Signal Scope share app/wifi/rf.py with the Dashboard.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Three Dashboard visuals had no NOC widget. This adds them:
radio_trendcovers one radio;channel_utilizationis a ranking)RF Spectrum and Signal Scope use
app/wifi/rf.py, the same module as the Dashboard, so channel placement and signal thresholds cannot drift between the two. Signal Scope spreads clients around their sector with a stable hash (zlib.crc32), so the dots do not move between renders.Notes
All new routes sit behind the existing suite-token dependency and take no request-supplied value other than the bounded time window.
Test plan
No automated tests: this repo has no
tests/folder.