DOC-1907: Add Paginate Messages page

local-antora-playbook.yml

@@ -18,7 +18,7 @@ content:
   - url: https://github.com/redpanda-data/docs
     branches: [v/*, shared, site-search,'!v-end-of-life/*']
   - url: https://github.com/redpanda-data/cloud-docs
-    branches: 'main'
+    branches: 'DOC-1907-paginate-messages-events'
   - url: https://github.com/redpanda-data/redpanda-labs
     branches: main
     start_paths: [docs,'*/docs']

modules/ROOT/nav.adoc

@@ -49,6 +49,7 @@
 *** xref:develop:consume-data/follower-fetching.adoc[Follower Fetching]
 *** xref:console:ui/programmable-push-filters.adoc[Filter Messages]
 *** xref:console:ui/record-deserialization.adoc[Deserialize Messages]
+*** xref:console:ui/paginate-messages-events.adoc[Paginate Messages and Events]
 ** xref:develop:data-transforms/index.adoc[]
 *** xref:develop:data-transforms/how-transforms-work.adoc[Overview]
 *** xref:develop:data-transforms/run-transforms-index.adoc[Get Started]

modules/console/pages/index.adoc

@@ -24,7 +24,7 @@ image::broker-overview.png[]
 
 Observe and debug your streaming data:
 
-* *Message inspection*: Browse and filter messages within your topics, with options to search by key, timestamp, or custom filters.
+* *Message inspection*: Browse and filter messages within your topics, with options to search by key, timestamp, or custom filters. See xref:console:ui/paginate-messages-events.adoc[] to inspect large result sets.
 * xref:console:ui/programmable-push-filters.adoc[*Programmable push filters*]: Write custom JavaScript filters to isolate specific messages, enabling deep inspection and debugging.
 * *Rewind and Replay*: Roll back consumer offsets to reprocess messages, allowing you to correct issues or replay data as needed.
 

modules/console/pages/ui/paginate-messages-events.adoc

@@ -0,0 +1,65 @@
+= Paginate Messages and Pipeline Events in {ui}
+:description: Retrieve more than 500 messages or pipeline events in {ui} by paging through larger result sets.
+:page-topic-type: how-to
+
+
+// tag::single-source[]
+
+{description} Use pagination when you need to inspect large topics or debug
+ifdef::env-cloud[]
+xref:develop:connect/about.adoc[Redpanda Connect]
+endif::[]
+ifndef::env-cloud[]
+xref:redpanda-connect:home:index.adoc[Redpanda Connect]
+endif::[]
+pipelines that emit more events than the initial result set includes.
+
+== Paginate topic messages
+
+When you browse a topic in {ui}, the *Messages* tab returns an initial batch of records. To retrieve additional records beyond this batch:
+
+. In the menu, go to *Topics* and select a topic.
+. Open the *Messages* tab.
+. Apply any filters or a starting offset to narrow the records you want to inspect.
++
+ifdef::env-cloud[]
+See xref:manage:schema-reg/programmable-push-filters.adoc[] and xref:manage:schema-reg/record-deserialization.adoc[].
+endif::[]
+ifndef::env-cloud[]
+See xref:console:ui/programmable-push-filters.adoc[] and xref:console:ui/record-deserialization.adoc[].
+endif::[]
+. After the initial results load, load the next batch to continue through the topic.
+
+You can continue paginating until you reach the end of the topic or the end of the offset range you specified.
+
+== Paginate Redpanda Connect pipeline events
+
+When you debug a Redpanda Connect pipeline, {ui} shows the events the pipeline emits, including logs at the configured log level. Pipelines that run with debug-level logging often produce more events than fit in a single result set.
+
+To retrieve additional pipeline events:
+
+. In the menu, go to *Connect* and select the pipeline you want to debug.
+. Open the pipeline's events view.
+. After the initial events load, load the next batch to continue inspecting events.
+
+ifdef::env-cloud[]
+For guidance on configuring log levels and monitoring pipelines, see xref:develop:connect/configuration/monitor-connect.adoc[].
+endif::[]
+ifndef::env-cloud[]
+For guidance on configuring log levels and monitoring pipelines, see xref:redpanda-connect:guides:monitoring.adoc[].
+endif::[]
+
+== Performance considerations
+
+Retrieving large result sets increases load on the {ui} backend and the cluster. To keep responses fast:
+
+* Narrow the result set with filters or a bounded offset range before paginating.
+ifdef::env-cloud[]
+* Use xref:manage:schema-reg/programmable-push-filters.adoc[JavaScript push filters] to match only the records you need.
+endif::[]
+ifndef::env-cloud[]
+* Use xref:console:ui/programmable-push-filters.adoc[JavaScript push filters] to match only the records you need.
+endif::[]
+* For pipeline debugging, raise the log level only as long as you need it.
+
+// end::single-source[]