Basic statistics trace
The basic statistics trace files are written as standard text files and should be readable in all common text editors.
The basic statistics file output appends a data set that documents key counts relating to FTM application activity recorded against a time stamp of when the data was written. The
following table shows the sections that are included in the report.
| Section | Description |
|---|---|
| Unit of work summary | Details the number of units of work during the analysis and the total time duration measured. |
| Mappers | Details the cost of calls to individual inbound and outbound mappers. |
| Processed Events | Details the cost of processing individual events. |
| Raised Events | Details the number of each event raised with details of aggregation achieved. |
| Transitions | Details the cost of processing individual transitions. |
| Actions | Details the cost of processing individual actions. |
| External Event Publishing | Details the cost of publishing individual events. |
| SQL | Details the cost of processing instrumented SQL statements. |
| Custom Activities | Details the cost of processing custom activities in application code. |
Under each section, the report lists the named activities in descending order of total cost. For example, a list based on total time duration shows the activities with the highest durations first.
For each record in the section, the detailed information available for the duration of each instrumented
run is shown in the following table.
| Item | Description |
|---|---|
| Name | A reference to a specific activity that has been tracked as a unique set of statistics, such as mapper name, or transition reference. It should be easily understood in the context of the instrumentation class. |
| Cost (s) | The total cost (time duration), in seconds, for this instrumented activity. |
| Percentage | The percentage cost of this activity against the total cost of all instrumented units of work. |
| Count | The number of times this activity occurred in a normal (not failed or aborted) context. |
| Norm time (s) | The total cost (time duration), in seconds, for this instrumented activity in a normal context. |
| Av. Norm time (s) | The average time of this activity in a normal context. (Norm time s / Count) |
| Min norm time (s) | Minimum time taken for one execution of this activity. |
| Max norm time (s) | Maximum time taken for one execution of this activity. |
| Failed count | The number of times this activity occurred in a failed context. |
| Failed time (s) | The total cost (time duration), in seconds, for this instrumented activity in a failed context. |
| Av. Failed time (s) | The average time of this activity in a failed context. (Failed time s / Failed count) |
| Aborted count | The number of times this activity occurred in an aborted context. |
| Aborted time (s) | The total cost (time duration), in seconds, for this instrumented activity in an aborted context. |
| Av. Aborted time (s) | The average time of this activity in an 'aborted context. (Aborted time s / Aborted count) |
Note: Depending on the instrumentation class, aborted may mean different things. For a mapper class, aborted
indicates a serious failure. For a transition, it simply means the transition did not meet the criteria of the
event filter and was, therefore, aborted. For many instrumentation classes, aborted may not have any meaning
at all.
The data in the instrumentation set is tab delimited so that it may easily be imported into any common spreadsheet package. This allows further analysis and manipulation of the data.
The following figure shows a simplified statistics set that has been imported into a spreadsheet for easy manipulation.
