Common fields
The following table lists and describes the fields that are common to all records of PFM - Agent for Service Response.
The following table shows the fields that are common to all records of PFM - Agent for Service Response, other than the unique fields of each record:
|
View name (Manager name) |
Description |
Summary |
Format |
Delta |
Data source |
|---|---|---|---|---|---|
|
Interval (INTERVAL) |
Collection interval during which the record was stored. |
ADD |
ulong |
Yes |
Agent Collector |
|
Record Time (RECORD_TIME) |
Time at which the record was created. |
COPY |
time_t |
No |
Agent Collector |
|
Record Type (INPUT_RECORD_TYPE) |
The xxxx part of the record IDs shown in the Table 10-13 (PD_xxxx, PI_xxxx, and PL_xxxx). |
COPY |
string(8) |
No |
Agent Collector |
The following table shows the fields that are common only to PI_record.
|
View name (Manager name) |
Description |
Summary |
Format |
Delta |
Data source |
|---|---|---|---|---|---|
|
Measurement Start Time (MSR_START_TIME) |
Measurement start time |
COPY |
time_t |
No |
Probe Daemon and IE Probe Daemon#1 |
|
Measurement Condition ID (MSR_COND_ID) |
Measurement condition ID |
COPY |
Long |
No |
Probe Daemon and IE Probe Daemon#1 |
|
Measurement Condition Name (MSR_COND_NAME) |
The label (any specified name) corresponding to the measurement condition. Stores the first matched label by searching within the following labels in this order:
If the label of the measurement condition is not defined in the both file, service-type-name_measurement-condition-ID is stored. |
COPY |
string (up to 63 bytes) |
No |
Probe Daemon and IE Probe Daemon#1 |
|
Result Code (RESULT_CODE) |
Measurement result code#2 |
COPY |
short |
No |
Probe Daemon and IE Probe Daemon#1 |
|
Result Strings (RESULT_STR) |
Character string corresponding to the measurement result code#2 |
COPY |
string (up to 31 bytes) |
No |
Probe Daemon and IE Probe Daemon#1 |
|
Service Type ID (SERV_TYPE_ID) |
Service type ID#3 |
COPY |
short |
No |
Probe Daemon and IE Probe Daemon#1 |
|
Service Type Name (SERV_TYPE_NAME) |
Service type name |
COPY |
string (up to 31 bytes) |
No |
Probe Daemon |
- #1
-
For IE Scenario (PI_IE) record, IE Scenario Overview (PI_IEO) record, and Logged Message for IE Scenario (PL_IESM) record, their data source is the IE Probe Daemon.
Otherwise, the data source is the Probe Daemon.
- #2
-
The following table lists and describes the result codes and the character strings that correspond to the result codes.
For details about the error, see the integrated trace log.
Table 10‒11: Result code Value
Code
Character string
Description
0
Success
SUCCESS
Measurement terminated normally.
1
Network error
NETWORK ERROR
Processing was cancelled due to a network or server failure that interrupted communication.
For example:
-
Name resolution has failed by DNS.
-
TCP connection has failed.
-
To close TCP connection has failed.
-
Web server has stopped.
For details about the network error, see the integrated trace log.
2
Timeout
TIME OUT
Processing cannot be completed within the specified timeout value.
3
Service error
SERVICE ERROR
The server is running normally, but the requested page or file cannot be acquired.
For example:
-
The user name or the password is incorrect.
-
SSL authentication failed in measurements of HTTPS (including Web transactions).
4
User-defined command error
USER_DEF_COMMAND ERROR
A user-defined command resulted in an error, such as in a program that does not support the user-defined command.
5
Unmatched response contents
UNMATCHED CONTENT
The page acquired by an IE scenario or a Web transaction does not satisfy the conditions (response determination information).
6
Replay IE scenario error
IE SCENARIO REPLAY ERROR
An error occurred while replaying the IE scenario.
For example:
-
The tag operated when the IE scenario was recorded is not found.
-
The frame is not found.
-
A dialog box that is not recorded appears.
For details, see 5.2.3(3) Notes on recording and replaying the IE scenarios.
7
IE scenario Navigation error
IE SCENARIO NAVIGATE ERROR
A navigation error occurred during replaying the IE scenario.
For details, see 5.2.4 Notes on the navigation.
99
Other
OTHER ERROR
Other error
For example:
-
Memory was insufficient during measurement.
-
An unexpected error occurred.
-
- #3
-
The following table lists the service type IDs.
Table 10‒12: Service type IDs Service
Service type name
Service type ID
HTTP
HTTP
101
HTTPS
HTTPS
102
SMTP
SMTP
103
POP3
POP3
104
IMAP4
IMAP4
105
DNS
DNS
106
DHCP
DHCP
107
FTP
FTP
108
TCP
TCP
109
Web transaction
WEBTRANS
110
IE scenario
IESCENA
111
User-defined service
USERSERV
199