BMP BGP Monitoring Protocol
A protocol where a router pushes its BGP tables and every update to an analysis station. Solves the problem that you otherwise have to pretend to be a neighbour to see what the router actually received.
Before BMP there were two bad options for anyone wanting to know what a router had received. Either you scraped command-line output on a schedule, which gives brittle snapshots, or you set up an extra BGP session to a collector — and then you only see what made it through outbound policy. RFC 7854 from 2016 solves it with a one-way TCP stream from the router where the station gets both an initial dump and continuous per-neighbour updates, with the crucial choice of exporting either before or after inbound policy. The former is the interesting one: it is the only way to see what the neighbour actually announced before your own filters had their say. Usually paired with pmacct or OpenBMP and a time series database, and in practice the standard tool for after-the-fact investigation of routing incidents.