Previous Topic: Support for Setting Logging Parameters Per TransactionNext Topic: Java SDK Log Enhancements


Support for Mandatory Logging of Certain Parameters Per Transaction

For every request that the AuthMinder Server processes, the Txn-Begin and Txn-End log lines are logged irrespective of the log level.

The following is an example of a Transaction Begin log line:

	TxnID=150057 | ClientTxnID=[_1T8I_31_34] | Protocol=5 (TXN_NATIVE) | ReqSize=936 | 
	TST=2011-11-13 15:25:13:0 (DB)

The following is an example of a Transaction End log line:

	TxnID=150057 | ClientTxnID=[_1T8I_31_34] | Processor=13 (AUTH_ARCOTID) | Operation=1030 
	(AUTH_AID_VERIFY_SIGNEDCHAL) | Response=0 (SUCCESS) | Reason=0 (UNDEFINED) | RespSize=245 | Time=97 | DBT=10 
	| NQ=9 | ExtEvents={ NONE } | AddInfo=[NONE] | LTB=48631 | LNL=0402/0402 | LML=196

The following are the details of the parameters in the log line:

TxnID

Transaction identifier

ClientTxnID

Client (typically Java SDK) transaction identifier

Protocol

Internal identifier for the input protocol used

ReqSize

Size of the input request in bytes

TST

Timestamp of the request and the source (DB indicates that the time source is the database server)

Processor

Internal identifier for processing module

Operation

Identifier for the operation

Response

Response code, indicates the final status of the transaction

Reason

Further detailed status of the transaction, typically applicable in case of failure

RespSize

Size of the response sent in bytes

Time

Time taken to process the request

DBT

Time spent for database operations

NQ

Number of database queries executed

ExtEvents

Any external events triggered. This is applicable in case of plug-in

AddInfo

Contains operation specific data, if any

LTB

Bytes logged to the file

LNL

Number of lines actually logged or attempted

LML

Longest log line length