Bay Area Backbone Monitor: Difference between revisions
Jump to navigation
Jump to search
(Created page with "The Bay Area Backbone Monitor Project is developing software to monitor, display, and alert people on the current state of the Bay Area Backbone. It is currently gathering requirements. == Requirements == * Measure and keep a history of inter-backbone bandwidth, latency, and jitter * Easy to consume dashboard showing current backbone status * SMS (or other) alerts for backbone problems * ...") |
No edit summary |
||
| Line 8: | Line 8: | ||
* Easy to consume dashboard showing current backbone status |
* Easy to consume dashboard showing current backbone status |
||
* SMS (or other) alerts for backbone problems |
* SMS (or other) alerts for backbone problems |
||
| + | * Check links between nodes at backbone site (connected, latency, bandwidth) |
||
| − | * ... |
||
| + | ** We've seen poorly configured switches significantly lower performance between nodes |
||
| + | * |
||
Revision as of 10:20, 14 June 2022
The Bay Area Backbone Monitor Project is developing software to monitor, display, and alert people on the current state of the Bay Area Backbone.
It is currently gathering requirements.
Requirements
- Measure and keep a history of inter-backbone bandwidth, latency, and jitter
- Easy to consume dashboard showing current backbone status
- SMS (or other) alerts for backbone problems
- Check links between nodes at backbone site (connected, latency, bandwidth)
- We've seen poorly configured switches significantly lower performance between nodes