Query criteria reference
This topic is a reference for session criteria and sources of latency.
Query Criteria
Criteria | Description |
---|---|
Show | A session is a collection of pages that a single user visited during a given time period. You can select completed sessions and / or sessions still in progress. |
Watchpoint | Queries traffic to a specific Watchpoint or traffic to all Watchpoints. |
Time range | Filters out data that falls outside of a specified time range. Select one of the predefined time ranges on the fixed range drop-down list, or create a specific time range using the custom time range control. |
Records | Limits the number of pages or sessions that displayed in your query results. You can display up to 5000 records. |
User ID | When configured to do so by an Administrator, the system can extract user identification tokens from web traffic. You can limit results to a traffic associated with a specific user, or choose any. |
Web group | When configured to do so by an Administrator, the system can extract group identification tokens from web traffic. You can limit results to a traffic associated with a specific group, or choose any. |
Page Name | You can limit results to a specific page name, or choose any. |
Client IP / Block | Filters traffic based on a specific client's IP address or IP block. |
Server IP / Block | Filters traffic based on a specific server's IP address or IP block. |
URI stem | Filters traffic based on a a specific URI stem. If you selected |
Host | Filters traffic based on a specific host name. |
Availability | Filters traffic by error category or error code. |
Info | Filters traffic by any informational condition categories, or by a list of specific informational condition codes. |
Performance | Filters traffic based on whether or not a page Service Level Threshold (SLT) was broken. |
Geolocation information | Geolocation information criteria filter traffic according the physical location of the client. Specifically, you can filter by city, country, DNS-name, ISP, Metro-area, organization, and region. |
Session system | Session system custom fields criteria filter traffic according to a system session custom field value. You can filter on values for Browser name, Entry Page Name, Exit Page Name, OS, and Site Referrer. |
Session user-defined | Session user-defined custom fields criteria filter traffic according to any session custom fields you have defined. |
Metric Filter | Use the Metric Filter to apply criteria based on specific metrics to traffic, such as host latency > 2000. |
Order | Orders by a given metric, such as Throughput or End-to-end latency in ascending or descending order, The default order is by Time descending. |
Sources of latency
Source of | Latency Color | Definition |
---|---|---|
SSL time (SSL) | If your site uses encryption, the system will record the time spent negotiating the encryption (if it occurs.) | |
Redirect time (Redir) | Redirect time describes how long the system spends redirecting a page container or object. For pages, it does not include redirect latency of any components in a page, only the container. | |
Host time (HS) | Host time describes the time the web, application, and database take to process a request. It can be very small in the case of a static image) or large (for a complex report, for example.) | |
Network time | Network time describes the time spent traveling across intervening networks. When the server has prepared its response, host time is over and network time begins. A small object might be delivered quickly; a large one might take a long time. If a user has a low-bandwidth connection such as a dial-up modem, the network time might be significant. BMC End User Experience Management records additional information about packet loss, out-of-order delivery, and round-trip time to help with this diagnosis. | |
Idle time (Idle) | When a browser is retrieving a page, but there is no activity between objects on the same page, the HTTP interaction is idle. For example, some web crawlers pause between object retrievals so they do not consume too much capacity; in other cases, some pages contain JavaScript that must be executed before the rest of the page can be rendered. When inactivity occurs mid-page, the system measures this as idle time. | |
Think time | Users pause between page changes, for example, when reading a page. When viewing a user's session, this think time is shown as a part of performance. |