Repository navigation
bgpcanary 1.7.6
Fixed
- Event page: the list of raw BGP updates stopped at the event's end. It covered the five minutes before the start up to the end, so a short event's list left out the route changes that came right after it: a 15-second ping alert's list was empty although RIS heard 174 updates in the next five minutes. An instant event such as a new upstream chain showed only the five minutes before the change. The list now covers the same half hour either side as the rest of the page, and for a long event the half hours around its start and around its end, each with a link to what changed in it.
- Bookkeeping rows in that list wait behind a tick box that says how many there are. Looking-glass corrections, seed rows after a restart and stale withdrawals only correct the stored state, and on some events they made up most of the list.
- When the list reaches its limit it says so: how many updates the stretch holds, and a link to BGP data for the stretch. It used to stop at 3,000 rows with a "+".
- An event stored with its end before its start (releases before 1.3.3 could close one that way) now gets its page, its tree and Around this event from its start, instead of a window that stopped half a minute before it.
- Event pages find a stretch's stored updates by time, instead of going through the prefix's whole history first: an eight-day event's page came a second quicker.
Update a server install with sudo bgpcanary-update. Container image: ghcr.io/gregsowell/bgpcanary:1.7.6 (with Docker Compose: docker compose pull && docker compose up -d).
New installs: docs/INSTALL.md for a server, docs/DOCKER.md for a container.