Skip to main content

Network Logs Tab

The Network Logs tab provides a detailed, tabular view of all network requests executed during a trace run. It helps users analyze request behavior, performance, and outcomes for debugging and monitoring purposes.

F
Written by Flakron Bajrami
Updated today

Overview

This view is especially useful for:

  • Identifying slow or failing requests

  • Verifying API calls and assets loading

  • Debugging frontend/backend communication


Layout

The page consists of three main sections:

  1. Filters Bar (top)

  2. Logs Grid/Table (center)

  3. Load More & Counters Summary (bottom)


Filters


Filter by Type

  • Dropdown labeled “Filter by type”

  • Default: All Types

  • Allows narrowing logs by request category

Typical values include:

  • Document

  • Image

  • Script

  • (Other types depending on request classification)

Use this filter to focus on specific resource types (e.g., only API calls or only images).


Entries Per Page

  • Dropdown on the right side (e.g., 25 entries per page)

  • Controls how many rows are displayed in the grid

Typical options:

  • 25

  • 50

  • 100

Changing this resets pagination and reloads the grid.


Logs Grid

The grid displays network requests in a structured table.

Columns

  • Sequential index of the log entry


URL

  • Full request URL

  • Truncated for display if too long

  • Tooltip shows the full URL on hover


Method

  • HTTP method used for the request

  • Examples:

    • GET

    • POST

    • PUT

    • DELETE


Status

  • HTTP response status code

  • Examples:

    • 200 (Success)

    • 404 (Not Found)

    • 500 (Server Error)

Helps quickly identify failed requests.


Type

  • Resource type of the request

  • Examples:

    • Document

    • Image

    • Script


Duration

  • Time taken to complete the request (in milliseconds)

  • Useful for performance analysis


Row Behavior

  • Each row represents a single network request

  • Hovering over the URL shows the full value

  • Rows are read-only (no inline editing)


Load More Functionality


At the bottom of the grid, a Load More button allows users to incrementally load additional records.

How It Works

  • Clicking Load More loads one additional page of records

  • The number of records loaded depends on the selected Entries Per Page value

Example:

  • If 25 entries per page is selected:

    • Initial load: 25 records

    • After clicking Load More: +25 records

  • If 50 entries per page is selected:

    • Load More adds 50 additional records


Counters & Summary

At the bottom of the grid:

  • Displays a summary such as:
    “Showing 25 of 1603 log(s)”

  • Indicates:

    • Number of visible rows

    • Total number of logs collected


Availability Across the Platform

The Network Logs tab is reused across multiple areas of the platform, providing a consistent experience for analyzing network activity in different contexts.

Where It Appears

The same Network Logs view is available in:

  • Web Client (Trace Details Modal)

    • Displays logs for executed traces

  • Editor

    • Available while creating or debugging tests

    • Helps inspect network activity during step execution

  • History Report

    • Accessible when reviewing past trace runs

    • Useful for analyzing previously executed tests and their network behavior

Did this answer your question?