Skip to main content

Navigate large result sets

Use page size, numbered jumps, Prev and Next controls, and current-page sorting without loading every matching check at once.

Detailed Logs uses pages so a long history remains responsive. The first applied query builds a catalog of the matching checks, calculates exact totals, and prepares secure page positions. Individual page changes can then retrieve only the rows needed for that page.

Choose rows per page

Available page sizes are:

  • 50 rows.
  • 100 rows, the default.
  • 250 rows.
  • 500 rows.

A smaller page is easier to scan on a phone or slower connection. A larger page reduces the number of page changes when working on a desktop.

Changing Rows per page does not update the result until you select Apply. Applying filters starts at page 1 and recalculates page totals for the new page size.

Use the page controls

Pagination appears above and below the table.

  • Prev moves to the preceding page.
  • Next moves to the following page.
  • A numbered button jumps directly to that page.
  • The highlighted number is the current page.

When there are 10 pages or fewer, every page number is shown. Larger result sets show up to 10 useful jump points, including the beginning, end, nearby pages, and intermediate positions.

The status line reports:

  • Current page and total pages.
  • Rows shown on the current page.
  • Total checks matching the applied filters.

Preparing this log range

When filters are first applied, the service reads the matching retained history to calculate exact totals and page positions. A 30-day one-minute monitor can take longer to prepare than a short or heavily filtered range.

During preparation:

  • Existing results stay visible until the new result is ready.
  • Apply, Reset, and Export are temporarily disabled.
  • Starting a newer log request cancels the stale browser request.

After the catalog is available, known page jumps avoid rebuilding it unnecessarily.

Sort the current page

Select a sortable column heading to reorder the rows currently displayed. Supported headings include Time, Status, HTTP, Latency, Diagnosis, Error, and URL.

  • Time starts newest first.
  • Selecting the same heading again reverses its direction.
  • Selecting another heading starts that field in its default direction.

Sorting is a current-page display operation. It does not reorder every page, change the summary totals, or change the CSV export order. Apply filters when you need to narrow the full result set rather than only rearrange visible rows.

Understand page changes after data expires

Raw checks age out under the 30-day retention policy. If the page remains open while old rows expire or new checks arrive, a previously calculated page count can eventually differ from a newly applied query.

Select Apply again to rebuild the catalog from the current retained history. If a requested page is beyond the new end of the result set, the service returns the final available page.

Tips for large investigations

  1. Use a short date range around the event.
  2. Add Down only or a diagnosis before increasing page size.
  3. Keep 100 rows per page for general investigation.
  4. Use numbered jumps for broad movement and Prev/Next for nearby pages.
  5. Export the applied result when analysis is easier in a spreadsheet.

Related articles

Did this answer your question?

Your response helps improve this Help Center.