...
This tool can read a binary transaction log containing server heartbeats emitted by a Talon Server and write them out in a human readable format. Computing and tracing statistics from the running application process results in cpu overhead and garbage. As a lower cost alternative Talon server can be configured to log its server heartbeats to a transaction log, and this tool can be used to compute and trace the binary stats in a separate process (possibly on another host).
...
The platform allows fairly granular control over which portions of the above stats are collected to provide the ability to control the associated overhead with collecting them. See AEP Engine Statistics for information on enabling collection of these statistics.
Basic Usage
| Info | ||
|---|---|---|
| ||
In order to use this tool, Binary Heartbeat Logging must have been enabled on the application in question. Even if you have enabled stats collection, but did not enable the hearbeat logging, you will not be able to retrieve said statistics at a later date. |
| Code Block | ||
|---|---|---|
| ||
StatsDumpTool [-h] [-o] [-s] [-e] <transactionLog> [<-h|--help> Displays this help message (default='false')] [<-o|--outFile> Name of output file name. Default file name is 'stats.txt] [<-s|--startDate> Start date of the query. The date must be in yyyy-MM-dd HH:mm:ss format] [<-e|--endDate> End date of the query. The date must be in yyyy-MM-dd HH:mm:ss format] <transactionLog> Path of the stats transaction log to read |
...
| Code Block | ||
|---|---|---|
| ||
cd path/to/logs/dir
java -cp nvx-core-all.jar:<your-app-classes> com.neeve.tools.StatsDumpTool
or
java -cp nvx-talon-all.jar:<your-app-classes> com.neeve.tools.StatsDumpTool |
Querying records within a time range
...
| Tip |
|---|
Be careful when specifying these timestamps! Leading/trailing spaces or additional spaces between date and time block might cause them to not be parsed correctly. |
Examples
...
| Code Block | ||
|---|---|---|
| ||
bin\xstatsdumptool.bat target\test-classes\com\neeve\tools\statsdumptest.log <10,2224,Ironman> 20160218-20:59:34:555 (inf)...[RogLog->'statsdumptest'] Live transaction log file is 'statsdumptest.log'... <10,2224,Ironman> 20160218-20:59:34:696 (inf)...[RogLog->'statsdumptest'] Scavenging old log files.... <10,2224,Ironman> 20160218-20:59:34:700 (inf)...[RogLog->'statsdumptest'] ....scavenged 0 files (0 failed). Writing 2619 records to C:\sources\neeve\github\nvx-platform-tools\nvx-stats-dump-tool\target\test-classes\com\neeve\tools\stats.txt Done ... |
The output shows that the tool has read 2,619 records and written them to the output file (stats.txt). Note that the output file is created in the same directory as the input file.
...