In 0.5.2, we revived and overhauled the Web UI. While the web UI will always be simplistic by design, and while it will never serve every single particular use case, we aim to make it both as usable and useful as possible within these limitations.
We invite everyone to provide feedback on any aspect of the web UI: what works for you and your use cases, what doesn’t, what’s missing, basically anything that comes to mind is useful feedback for us. Even if an idea might not fit the web UI as we envision it, we might be able to use it for the JSON API. So, don’t hold back.
A brief overview of where we stand, roughly.
With the release of 0.5.2, the web UI provides the following:
- An overview of all connected BMP routers and BGP sessions, showing all monitored ribs
- Overviews of routes per peer ASN, per peer IP, per RIB view (e.g. adj-RIB-in pre-policy)
- Overviews of routes per prefix, showing exact matches, less specifics, more specifics
- Diffs between (BMP streams from) routers: which peers are connected to both, or only one?
- Diffs between RIB views: which routes are in adj-RIB-in pre-policy, but not in adj-RIB-in post-policy?
- Detailed overviews of monited BGP sessions, in multiple levels:
- showing session information based on BGP Capabilities, e.g. BGP Roles and Extended Next Hop information
- showing aggregated information based on the actual routes, e.g. which ribs contain RPKI ROV Invalids, or which ribs contain Extended Communities
Known limitations:
- Information based on the actual routes is currently expensive: on deployments with a lot of stored routes, generating the page will take a while. There are many fundamental changes in the pipeline (which’ll hopefully land in v0.7.0) that should improve this significantly.
- Not all pages are reachable by simply clicking around in the UI. Most notably, the diff view to compare routes between two rib views. In the main overview of the BMP sessions, there are ‘vs’ links to compare the adj-RIB-in pre vs post for a particular peer. But the diff page can actually show the difference between any rib from any peer, cross BMP session, and even from a BMP session versus a BGP session. Currently, one needs to edit the URL to get to such a particular page.
On the (wish|TODO|ideas) list:
- Show RTR status in the main overview
- More path attributes in the detailed view:
- deprecated attributes that are known to cause issues
- add markers for specific well known communities
- More links:
- the ‘vs’ rib diff described in the Known limitations above