Bay Area Backbone Monitor: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 10: | Line 10: | ||
* Check links between nodes at backbone site (connected, latency, bandwidth) |
* Check links between nodes at backbone site (connected, latency, bandwidth) |
||
** We've seen poorly configured switches significantly lower performance between nodes |
** We've seen poorly configured switches significantly lower performance between nodes |
||
| + | *Automatically group nodes at the same site together |
||
| − | * |
||
| + | *Backbone is a group of sites |
||
| + | **Backbone links should be auto-discoverable based on the grouping of nodes in sites, and sites together |
||
| + | *Map of backbone |
||
Latest revision as of 15:42, 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
- Automatically group nodes at the same site together
- Backbone is a group of sites
- Backbone links should be auto-discoverable based on the grouping of nodes in sites, and sites together
- Map of backbone