NMS-15853: More BMP docs related to distributed processing.

docs/modules/reference/pages/telemetryd/protocols/bmp/bmp.adoc

@@ -7,4 +7,12 @@ The integration in {page-component-title} lets you use these route views, status
 .BMP integration overview
 image::bmp/bmp_integration_overview.png[width=70%]
 
-The following sections provide details about associated parsers, adapters, and listeners.
+The following sections provide details about associated parsers, adapters, and listeners.
+
+== Distributed BMP processing with Sentinel
+
+You can use Sentinel to process BMP statistics ingested by one or more Minions in order to alleviate load on the core.
+All of the BMP-related adapters can run on Sentinel, allowing you to generate events and metrics, and ingest route changes.
+In this mode, events are sent back to the message broker for the core to process and metrics are persisted directly to the time series database.
+
+TIP: The https://github.com/OpenNMS-forge/bmp-playground[BMP Playground] provides a virtual lab that you can use to simulate BGP, BMP, and to see how the {page-component-title} components can be configured at runtime.

docs/modules/reference/pages/telemetryd/protocols/bmp/persisting-adapter.adoc

@@ -112,3 +112,5 @@ Refer to xref:reference:configuration/sentinel-features.adoc#ga-kafka-configurat
 
 NOTE: When running Kafka as the broker, the consumer config needs to have the `auto.offset.reset=earliest` setting, otherwise
 the BMP Adapter may miss some of the early messages, like the PeerUp notification, which are essential for proper BMP state.
+
+NOTE: When running on Sentinel, it is still necessary to have the `opennms-telemetry-bmp-stats` feature running on the core.