6.3.3 Details of adaptor trace information

Adaptor trace information is provided as trace files to which the processing status of adaptors is output. This information is used at the stage of testing the operation of Stream Data Platform - AF to check the processing status of each callback operation.

The default is that adaptor trace information is not output because its output affects adaptor throughput. To make this trace information available, specify ON for the trace attribute in the adaptor trace definition. Before actual operations begin, set this attribute so that adaptor trace information will not be output. For details about the adaptor trace definition, see 9.6.2 Adaptor trace definition.

Adaptor trace information is created for each adaptor, with two megabytes of trace information output to each file in the wraparound mode.

Organization of this subsection
(1) Name of adaptor trace information
(2) Output format of adaptor trace information
(3) Example of output of adaptor trace information

(1) Name of adaptor trace information

Adaptor trace information is output under the following name:

adp_type-adaptor-group-name-adaptor-name_serial-number

The following describes each component of the file name:

If the adaptor trace file already exists when the adaptor starts, its file name is changed to file-name.bk.

For details about the adaptor definition files, see 9. Adaptor Definition Files.

(2) Output format of adaptor trace information

Adaptor trace information is output in CSV format, as shown below:

number,date,time,thread,event

The table below describes each output item.

Table 6-6 Items output as adaptor trace information

No.ItemDescription
1number4-digit serial number (when the value reaches 9999, it initializes to 0001)
2dateDate the trace information was collected, in the format YYYY/MM/DD
3timeTime the trace information was collected, in the format hh:mm:ss.fff
4threadAdaptor name (value specified in the name attribute in the adaptor definition)
5eventCallback name and detailed information, in the following format:

callback-name[Figure]{entry|exit}

  • callback-name: Value specified in the name attribute in the CB definition
  • [Figure]: Single-byte space
  • {entry|exit}:
    entry: Callback processing was started
    exit: Callback processing was terminated

An example of the output is shown below. In this example, the first line is a header and the subsequent lines are records.

No,Date,Time,Thread,Event
0001,2010/10/15,02:08:41.173,OutputAdaptor1,receiver entry
0002,2010/10/15,02:08:41.173,OutputAdaptor1,receiver exit
0003,2010/10/15,02:08:41.188,OutputAdaptor1,editor1 entry
0004,2010/10/15,02:08:41.188,OutputAdaptor1,editor1 exit
0005,2010/10/15,02:08:41.188,OutputAdaptor1,editor3 entry
0006,2010/10/15,02:08:41.204,OutputAdaptor1,editor3 exit
0007,2010/10/15,02:08:41.204,OutputAdaptor1,outputer entry
0008,2010/10/15,02:08:41.204,OutputAdaptor1,outputer exit
0009,2010/10/15,02:08:41.204,OutputAdaptor1,receiver entry
0010,2010/10/15,02:08:41.204,OutputAdaptor1,receiver exit
0011,2010/10/15,02:08:41.204,OutputAdaptor1,editor1 entry
0012,2010/10/15,02:08:41.204,OutputAdaptor1,editor1 exit
0013,2010/10/15,02:08:41.204,OutputAdaptor1,editor3 entry
0014,2010/10/15,02:08:41.204,OutputAdaptor1,editor3 exit
0015,2010/10/15,02:08:41.204,OutputAdaptor1,outputer entry
0016,2010/10/15,02:08:41.204,OutputAdaptor1,outputer exit
 :

(3) Example of output of adaptor trace information

This subsection describes the adaptor trace information that is output when records are discarded during callback processing or packets are discarded during HTTP packet input connector processing.

The following shows examples of output of adaptor trace information for callbacks:

  1. HTTP packet input connector
    This example discarded 50 excess records because the number of records to be stored in the output buffer for the HTTP packet input connector (callback name: inputer) exceeded the maximum value.

    3288,2010/10/15,10:16:11.223,InputAdaptor1,inputer entry
    3289,2010/10/15,10:16:11.223,InputAdaptor1,inputer execute delete record overflow 50
    3290,2010/10/15,10:16:11.223,InputAdaptor1,inputer exit

  2. Filter
    This example discarded 100 records (R1) that did not satisfy a field condition for filtering (callback name: filter1):

    3291,2010/10/15,10:16:11.223,InputAdaptor1,filter1 entry
    3292,2010/10/15,10:16:11.223,InputAdaptor1,filter1 execute delete condition R1 100
    3293,2010/10/15,10:16:11.223,InputAdaptor1,filter1 exit

  3. Record extraction
    This example discarded 10 records that did not satisfy an extraction target record condition (conditionE2) for record extraction (callback name: extract1):

    3294,2010/10/15,10:16:11.223,InputAdaptor1,extract1 entry
    3295,2010/10/15,10:16:11.223,InputAdaptor1,extract1 execute delete condition conditionE2 10
    3296,2010/10/15,10:16:11.223,InputAdaptor1,extract1 exit

  4. Dashboard output connector
    This example discarded 20 records because the number of records to be retained by the dashboard output connector (outputer) reached the maximum value:

    3288,2010/10/15,10:16:11.223,OutputAdaptor1,outputer entry
    3289,2010/10/15,10:16:11.223,OutputAdaptor1,outputer execute delete numoverflow 20
    3290,2010/10/15,10:16:11.223,OutputAdaptor1,outputer exit