What do the fields in xroute-server.log mean? (xServer1)

[quintiqus]

For example, I have this line in that log, but I'm curious to what especially the bold numbers mean:

2016-06-28 14:20:23,714;INFO;RequestTimes;req-986660-1467141600948;172.16.16.16;unknown-http;30030;unknown-cluster;XRoute.calculateRoute;true;;;;default;xroute.1;1;0;0;127;0;22622;128;22752;NO-TXN;;2231617,5331073;2176754,5140986;;2;;-;-;-

[Bernd Welter]

Hello Quintiqus,

that's simple... they give you valuable info about the timestamps of various transaction parts. Have a look at the following line - it is a style that's logged whenever the server is started. You can identify the
2016-06-18 23:17:45,291;INFO;RequestTimes;id;client host;user;port;clusterId;service;success;log1;log2;log3;profile;pool instance;deserialization;input trafo;module queueing;module time;output trafo;serialization;total inner;total outer;transaction;use-cases;ref-coord 1;ref-coord 2;dynamic provider;dimensions;additionalInfo;errorType;errorCode;errorMsg

Request timestamps imported into table.

The proper description of these columns is given in the Administrators_Guide/DSC_Logging_Configuration.htm



You can use these info to determine

• is the stress level of the server high (module queueing times over acceptable value)
• do transaction spend too much time in the backend (module time)
• where do the clients come from (client host)
• ... much more

which is very helpful in case of performance analysis.
Best regards Bernd

[quintiqus]

Thanks Bernd! Just what I needed!

[jschisch]

Hi Bernd,

Just another question to a xroute log line. Beside normal log lines I receive the following:

Code: Select all

xroute:4479,0,0,0,66,5,2217,66,79,6,2267,3193864192,15685560000000,535822336,90228600,117964800,115479400,m0001,0,0,6040826955,4479,RUNNING,3315388416,3521170000000,37748736,7140088,26345472,25556632

Is there a documentation for each field available?

Thanks,
Johannes

[Bernd Welter]

Hello Johannes,

the loglines I mentioned above are triggered by a transaction. The ones you mentioned are written on a periodical interval and are based on the following pattern:

Code: Select all

2018-01-18 08:59:42,774;INFO;com.ptvgroup.xserver.framework.StatisticTimer;numSuccess, numFailure, numRejected, numServiceRequests, avgTime, minTime, maxTime, avgComputationTime, avgOuterTime, minOuterTime, maxOuterTime, commitedVirtualMemorySize, processCpuTime, heapCommittedMemorySize, heapUsedMemorySize, nonHeapCommittedMemorySize, nonHeapUsedMemorySize [, instanceId, restarts, userRestarts, uptime, useCounter, moduleStatus, commitedVirtualMemorySize, processCpuTime, heapCommittedMemorySize, heapUsedMemorySize, nonHeapCommittedMemorySize, nonHeapUsedMemorySize]+

Or in list form:

• com.ptvgroup.xserver.framework.StatisticTimer
• numSuccess
• numFailure
• numRejected
• numServiceRequests
• avgTime
• minTime
• maxTime
• avgComputationTime
• avgOuterTime
• minOuterTime
• maxOuterTime
• commitedVirtualMemorySize
• processCpuTime
• heapCommittedMemorySize
• heapUsedMemorySize
• nonHeapCommittedMemorySize
• nonHeapUsedMemorySize [
• instanceId
• restarts
• userRestarts
• uptime
• useCounter
• moduleStatus
• commitedVirtualMemorySize
• processCpuTime
• heapCommittedMemorySize
• heapUsedMemorySize
• nonHeapCommittedMemorySize
• nonHeapUsedMemorySize]+

So these values describe latest statistics about aggregated previous transactions since server start and tell you about the server state.

Best regards,
Bernd

[jschisch]

Hi Bernd,

That is exactly what I'm looking for.

Many thanks for your reply.

Best regards
Johannes