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:

Table 9-10 List of Common fields (to PD_record, PI_record, and PL_record)

View name
(Manager name)
DescriptionSummaryFormatDeltaData source
Interval
(INTERVAL)
Collection interval during which the record was stored.ADDulongYesAgent Collector
Record Time
(RECORD_TIME)
Time at which the record was created.COPYtime_tNoAgent Collector
Record Type
(INPUT_RECORD_TYPE)
The xxxx part of the record IDs shown in the Table 9-14 (PD_xxxx, PI_xxxx, and PL_xxxx).COPYstring(8)NoAgent Collector

The following table shows the fields that are common only to PI_record.

Table 9-11 Common fields (only to PI_record)

View name
(Manager name)
DescriptionSummaryFormatDeltaData source
Measurement Start Time
(MSR_START_TIME)
Measurement start timeCOPYtime_tNoProbe Daemon and IE Probe Daemon#1
Measurement Condition ID
(MSR_COND_ID)
Measurement condition IDCOPYLongNoProbe 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:
  1. The labels defined in the measurement condition registration file.
  2. The labels defined in the measurement condition label definition file.
If the label of the measurement condition is not defined in the both file, service-type-name_measurement-condition-ID is stored.
COPYstring (up to 63 bytes)NoProbe Daemon and IE Probe Daemon#1
Result Code
(RESULT_CODE)
Measurement result code#2COPYshortNoProbe Daemon and IE Probe Daemon#1
Result Strings
(RESULT_STR)
Character string corresponding to the measurement result code#2COPYstring (up to 31 bytes)NoProbe Daemon and IE Probe Daemon#1
Service Type ID
(SERV_TYPE_ID)
Service type ID#3COPYshortNoProbe Daemon and IE Probe Daemon#1
Service Type Name
(SERV_TYPE_NAME)
Service type nameCOPYstring (up to 31 bytes)NoProbe 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 9-12 Result code

ValueCodeCharacter stringDescription
0SuccessSUCCESSMeasurement terminated normally.
1Network errorNETWORK ERRORProcessing 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.
2TimeoutTIME OUTProcessing cannot be completed within the specified timeout value.
3Service errorSERVICE ERRORThe server is running normally, but the requested page or file cannot be acquired.
For example:
  • The user name or the password is incorrect.
4User-defined command errorUSER_DEF_COMMAND ERRORA user-defined command resulted in an error, such as in a program that does not support the user-defined command.
5Unmatched response contentsUNMATCHED CONTENTThe page acquired by an IE scenario or a Web transaction does not satisfy the conditions (response determination information).
6Replay IE scenario errorIE SCENARIO REPLAY ERRORAn 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 4.2.3(3) Notes on recording and replaying the IE scenarios.
7IE scenario Navigation errorIE SCENARIO NAVIGATE ERRORA navigation error occurred during replaying the IE scenario.
For details, see 4.2.4 Notes on the navigation.
99OtherOTHER ERROROther error
For example:
  • Memory was insufficient during measurement.
  • An unexpected error occurred.
#3
The following table lists the service type IDs.

Table 9-13 Service type IDs

ServiceService type nameService type ID
HTTPHTTP101
HTTPSHTTPS102
SMTPSMTP103
POP3POP3104
IMAP4IMAP4105
DNSDNS106
DHCPDHCP107
FTPFTP108
TCPTCP109
Web transactionWEBTRANS110
IE scenarioIESCENA111
User-defined serviceUSERSERV199