- 27 Jan 2022
- 3 Minutes to read
- Contributors
- Print
- PDF
HTTP Time Chart
- Updated on 27 Jan 2022
- 3 Minutes to read
- Contributors
- Print
- PDF
HTTP Timechart
Overview
The HTTP Timechart provides a breakdown for a specific page load event, detailing the page's hits and metrics. When the user opens a timechart, they are viewing raw data for that specific page load, not aggregate data for an URL or other category as in analysis.
Note: "Hits" does not refer to the number of times this page's URL has been loaded, but the number of HTTP transactions made under a specific page load event. Each row in the timechart's table is a single hit.
How to access
Access an analysis view that groups by Page Load ID (hit.parent)
Template: HTTP Pages analysis view
This analysis template view groups by page load ID*\Custom analysis views grouped by page load ID
Note: Any custom analysis view grouping by page load ID will also workFlow details of any HTTP view
Note: Opening the flow details for any table row of an HTTP viewIn the controls column of the table widget, open the controls menu and select "HTTP Timechart"
HTTP Timechart Header
The header shows the page's URL, total load time, and the client and server IP's and ports. Other common properties are listed below the table.
The table lists all of this page load's hits, and a waterfall chart visualizing where they took place in the overall page load.
By hovering the mouse over a waterfall line, the user can view detailed information about that hit's timings:
- Begin
- Client data transfer time (DTT)
- Server response time (SRT)
- Server data transfer time (DTT)
- End
IP Zone or Functionality
This feature is available in Monitoring as well as in analysis. A user can now filter by IPs and zones without specifying whether it is from source/destination or client/server.
To apply an OR filter, use one of the following categories:
- Client/Server IP
- Client/Server Zone
- Source/Dest IP
- Source/Dest Zone
If a user filters on one of these categories, an OR condition will be applied across the associated categories.
For example, if a user adds a filter value of 192.168.* for the category Client/Server IP, then the data will be filtered to include all values where the Client IP begins with 192.168.* or the Server IP begins with 192.168.*.
Subnet Filtering
A user can now filter for a range of IP filters using CIDR notation.
How it works
Adding an IP filter value followed by a backslash and decimal number will filter the results to only include addresses that match on the specified number of bits. The number after the backslash specifies the number of bits.
For example, adding a Client IP filter value of 192.0.0.0/8 will return all IPs that match on the first 8 bits, which are all addresses that are between 192.0.0.0 and 192.255.255.255.
Similarly, adding a Client IP filter value of 64.0.0.0/2 will return all IPs that match on the first 2 bits, which are all addresses that are between 64.0.0.0 and 127.255.255.255.
IPv6 Subnet filtering
You can also use IPv6 subnet filtering , as shown below:
Flow details
To access flow details, open Analysis and select any Capture based template.
How it works
From the main window, open the dropdown that is located in the the first column of each row. Select "See flow details" to open up the flow details view for a particular row.
Flow details has a Table widget and a Distribution widget. The metrics and categories will be the same as the parent template. The default filters will be the categorical values from the row selected for flow details.
© 2024 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks