Overview Tab

The Overview tab provides options for getting structured information and statistical data for captured sessions. It is located in the Live Traffic tab and all entries are available in the Sessions list.

Overview contains a set of widgets, which are dynamically changing depending on the number of selected sessions:

  • Timings—Available for selecting both a single session and a selection of multiple sessions.
  • Sizes—Available for selecting both a single session and a selection of multiple sessions.
  • Statistics—Available for multiple sessions only.
  • Request Details—Available for a single session only.
  • Response Details—Available for a single session only.

Timings

The Timings widget provides a visual representation of the time that is needed to execute a single session or select multiple sessions. Each session is listed on a separate line and is presented with a URL that corresponds to the URL column in the Live Traffic list, and a chart of the request and response timings.

The maximum length of the URL is 30 symbols. To visualize a tooltip with the entire session URL, click the three dots at the end of the wrapped URL. The Timings chart splits into two main parts—the blue section of the chart shows timings related to the request, and the orange section of the charts shows timings related to the response. Each sub-chart area has a tooltip with descriptive information about the visualized timing.

Timings widget

Tracked Request Timings provides the following options:

  • Gateway Determination Time—The time (in milliseconds) required to determine the gateway. All values over 1000ms are unusual and suggest an issue.

  • DNS Time—The time (in milliseconds) required for a DNS lookup. Average DNS lookup times are between 20 and 120ms.

  • TCP Connect Time—The time (in milliseconds) required to establish a TCP/IP connection. A value around 21000ms suggests that the target is unreachable, and the Windows OS took 21 seconds to confirm the issue.

  • HTTPS Handshake Time—The time (in milliseconds) required to finish an HTTPS handshake. While capturing HTTPS traffic, you will see what the client and the server are using to communicate with Fiddler Everywhere. This can be different from what they would use if the Fiddler Everywhere proxy was not in the middle. To see the CONNECT tunnels without the Fiddler Everywhere interference, disable the Capture HTTPS traffic option.

  • Client Connected—The time (in milliseconds) between the current and the previous event. The timestamp that indicates when the event happened is available in the Request Details widget.

  • Client Begin Request—The time (in milliseconds) between the current and the previous event. The timestamp that indicates when the event happened is available in the Request Details widget.

  • Fiddler Got Request Headers—The time (in milliseconds) between the current and the previous event. The timestamp that indicates when the event happened is available in the Request Details widget.

  • Client Done Request—The time (in milliseconds) between the current and the previous event. The timestamp that indicates when the event happened is available in the Request Details widget.

  • Server Connected—The time (in milliseconds) between the current and the previous event. The timestamp that indicates when the event happened is available in the Request Details widget.

  • Fiddler Begin Request—The time (in milliseconds) between the current and the previous event. The timestamp that indicates when the event happened is available in the Request Details widget.

  • Server Got Request—The time (in milliseconds) between the current and the previous event. The timestamp that indicates when the event happened is available in the Request Details widget.

The Tracked Response Timings provides the following options:

  • Server Begin Response—The time (in milliseconds) between the current and the previous response event. The timestamp that indicates when the event happened is available in the Request Details widget.

  • Fiddler Got Response Headers—The time (in milliseconds) between the current and the previous response event. The timestamp that indicates when the event happened is available in the Request Details widget.

  • Server Done Response—The time (in milliseconds) between the current and the previous response event. The timestamp that indicates when the event happened is available in the Request Details widget.

  • Client Begin Response—The time (in milliseconds) between the current and the previous response event. The timestamp that indicates when the event happened is available in the Request Details widget.

  • Client Done Response —The time (in milliseconds) between the current and the previous response event. The timestamp that indicates when the event happened is available in the Request Details widget.

Under the list of session lines, you will find the Request (light blue) and Response (orange) footers with total timings in milliseconds (ms) or seconds (s) for all listed sessions. For example, if five sessions are selected from the Live Traffic list, the displayed time in the Request and Response footers is the total time taken for all five selected requests or responses.

Timings widget

Sizes

The Sizes widget provides a visual representation of the size of a single session or a selection of multiple sessions. Each session is listed on a separate line and is presented with a URL, which corresponds to the URL column in the Live Traffic list, and a chart that shows the sizes of the headers and the body of the request and response, each included in a single chart.

The maximum length of the URL is 30 symbols. To visualize a tooltip with the entire session URL, click the three dots at the end of the wrapped URL.

Tracked session sizes provides the following options:

  • Request Headers—The size of all request headers in bytes or kilobytes.

  • Request Body—The size of all request bodies in bytes or kilobytes.

  • Response Headers—The size of all response headers in bytes or kilobytes.

  • Response Body—The size of all response bodies in bytes or kilobytes.

Under the list of session lines, you will find the Request Headers (dark blue), Request Body (light blue), Response Headers (red), and Response Body (orange) footers with the total size in kilobytes (kB) or bytes (B) for all listed sessions.

Sizes widget

Statistics

The Statistics widget contains a table with structured information for multiple selected sessions. The widget is only available when multiple sessions are selected (collapsed and inactive for a single session selection).

  • Session Count—The number of selected sessions.

  • Headers Sent—The size of the sent request headers in bytes.

  • Body Sent—The size of the sent request bodies in bytes.

  • Headers Received—The size of the received response headers in bytes.

  • Body Received—The size of the received response bodies in bytes.

  • Started At—The date and time when the earliest client request is established. Corresponds to the Client Begin Request request timing.

  • Completed At—The date and time when the latest client response finishes. Corresponds to the Client Done Response response timing.

  • Aggregate Duration—The total aggregate duration for all selected sessions in milliseconds.

  • DNS Time—The aggregate DNS time for all selected sessions in milliseconds.

  • Connect Time—The aggregate TCP connect time for all selected sessions in milliseconds.

  • Handshake Time—The aggregate HTTPS handshake time for all selected sessions in milliseconds.

  • Requests per Host—A list of the hosts and the number of requests to each of them.

  • Responses by Code—A list of the received HTTP response status codes and the number of appearances.

  • Response Size by Type—A list of the received response types and their aggregate size.

Request Details

The Request Details widget contains a table with the following information:

  • URL—The URL address of the selected session.

  • Method—The HTTP request method.

  • Client IP—Indicates the client IP that sent this request. Most of the time, the IP will show the loopback address (0.0.0.0), but it will be different if multiple computers on the network are pointed to a single Fiddler Everywhere instance.

  • Remote IP—Indicates the IP address of the server used for this request.

  • Protocol—The protocol type (HTTP or HTTPS) used by the session.

  • SSL Version—The version of the used cryptographic protocols (TSL or SSL).

  • Sizes displays the following options:

    • Body—The size of the request body in bytes.
    • Headers—The size of the request headers in bytes.
  • Timings —A list by execution order with timestamps for each triggered request event.

Response Details

The Response Details widget contains a table with the following information:

  • Status—The HTTP response status code and status message.

  • Sizes

    • Body—The size of the response body in bytes.
    • Headers—The size of the response headers in bytes.
  • Timings—A list by execution order with timestamps or times (in milliseconds) for each triggered response event.

In this article