HTTP (PI_HTP)
Function
The HTTP (PI_HTP) record stores information about HTTP service response time. This is a multi-instance record.
Default and changeable values
Item | Default value | Changeable |
---|---|---|
Collection Interval | 360 | Y |
Collection Offset | 0 | Y |
Log | No | Y |
LOGIF | (Blank) | Y |
ODBC key fields
PI_HTP_MSR_COND_ID
Lifetime
None
Record size
Fields
View name (Manager name) | Description | Summary rule | Format | Delta | Data source |
---|---|---|---|---|---|
DNS Time (DNS_TIME) | DNS time (seconds) ((4) in Figure 9-4) | AVG | double | No | Probe Daemon |
Data Transfer Time (DATA_TRANS_TIME) | Data transfer time (seconds) ((7) in Figure 9-4) | AVG | double | No | Probe Daemon |
HTTP Time (HTTP_TIME) | HTTP time (seconds) ((3) in Figure 9-4) | AVG | double | No | Probe Daemon |
Request Count (REQ_COUNT) | Number of requests issued (count) | AVG | double | No | Probe Daemon |
Server Processing Time (SERV_PROCESS_TIME) | Server processing time (seconds) ((6) in Figure 9-4) | AVG | double | No | Probe Daemon |
Setup Time (SETUP_TIME) | Setup time (seconds) ((2) in Figure 9-4) | AVG | double | No | Probe Daemon |
TCP Connection Time (TCP_CON_TIME) | TCP connection time (seconds) ((5) in Figure 9-4) | AVG | double | No | Probe Daemon |
Throughput (THROUGHPUT) | Resource transfer throughput (bits/second). This is determined by the total size of resources and the data transfer time. | AVG | double | No | Probe Daemon |
Total Amount of Data (TOTAL_DATA_SIZE) | Total amount of data transferred between the HTTP probe and the measurement-target server via the TCP connection (bytes) | AVG | double | No | Probe Daemon |
Total Resource Size (TOTAL_RES_SIZE) | Total size of resources acquired (bytes) | AVG | double | No | Probe Daemon |
Total Response Time (TOTAL_RESP_TIME) | Total response time (seconds) ((1) in Figure 9-4) | AVG | double | No | Probe Daemon |
The following figure shows the HTTP sequence.
Figure 9-4 HTTP sequence
HTTP operating environment and notes
A HTTP probe issues a HTTP request to the specified URL, uses the GET method to acquire the page or the POST method to register data, and measures the response time.
The following describes and provides notes on a HTTP operating environment.
Web authentication
The Basic Authentication method is used.
Cookie
PFM - Agent for Service Response accepts cookies based on Netscape Communication's specifications. The information sent as a cookie from the HTTP server is stored in the Cookie file that is created for each measurement condition. The Cookie files remain undeleted even after measurement is completed. If measurement cannot be performed correctly due to a change made to the contents of a measurement condition, delete the Cookie file for that measurement condition, which can be identified by the measurement condition ID. The following is the naming convention for Cookie files:
cookies_<measurement-condition-ID>
Cookie files are stored in the following folder:
installation-folder\agtv\probe\probedata\http
Program execution
Plug-ins, JavaScripts, and applets are downloaded but not executed.
Depth
For example, specifying a depth of 2 acquires the pages displayed in the resources and frames that are embedded in the page at the specified URL. No linked pages are acquired. PFM - Agent for Service Response repeats the acquisition of resources and frames embedded in the acquired page or frame as many times as the specified value.
For the embedded resources and frames, PFM - Agent for Service Response analyzes the acquired HTML, and acquires the resources and frames that are specified by the value of the tag and attribute shown in the table below.
Table 9-15 Embedded resources and frames to be acquired
Tag name | Attribute name |
---|---|
applet | code |
frame | src |
iframe | src |
img | src |
script | src |
The resources and frames embedded in the HTTP responses compressed by the tool such as gzip or compress are not acquired.
Use of proxy
If acquiring the Web page specified by the URL and the embedded resources and frames involves use of a proxy for only part of the acquisition target, measurement cannot be performed.
HTTP Version
HTTP/1.0 is applicable.
RFC compliance
For the functions that are not compliance with RFCs and the restrictions, see the above notes.