The following statistics are exposed by this MBean.
Aggregated BPO method execution statistics - the following counters are available:
Username – the username that invoked this method. This is only valid when per user statistics are collected.
BPO Method – the name of the BPO method
Elapsed Time(ms) - the average response time in milliseconds for this BPO method
Min Elapsed Time(ms) - the minimum elapsed time in milliseconds
Max Elapsed Time(ms) - the maximum elapsed time in milliseconds
Std Deviation Elapsed Time(ms) - the standard deviation for the elapsed time
Invocations - the number of invocations of this method
Errors - the number of exceptions thrown by this method
Aggregated SQL statement execution statistics - this data is available only if the MBean configuration parameter curam.jmx.sql_statement_statistics_enabled is set to true.
Username – the username that executed this SQL statement. This is only valid when per user statistics are collected.
SQL Text – the text of the SQL statement
Executions – the total number of times this SQL statement was executed including database and query cache hits
Elapsed Time(ms) – the average elapsed time in milliseconds to execute the statement. Only occurrences which hit the database are taken into account.
Min Elapsed Time(ms) - the minimum elapsed time in milliseconds
Max Elapsed Time(ms) - the maximum elapsed time in milliseconds
Std Deviation Elapsed Time(ms) - the standard deviation for the elapsed time
Rows Returned - the average number of rows returned by the statement
Min Rows Returned - the minimum number of rows returned by the statement
Max Rows Returned - the maximum number of rows returned by the statement
Std Deviation Rows Returned - the standard deviation for the number of rows returned by the statement
Query Cache Hit Ratio - the percentage of query cache hits
Aggregated application exception statistics
Username – the username that invoked the operation that threw the exception. This is only valid when per user statistics are collected.
Catalog Entry – the catalog entry for the exception's message
Occurrences – the number of occurrences of this exception
Aggregated SQL query cache statistics
Query cache type - the type of the query cache
Misses - the number of cache misses
Hits – the number of cache hits
Data about in-flight BPO method and SQL statement invocations - this data is only collected when the Cúram JMX configuration parameter curam.jmx.in_flight_statistics_enabled is set to true.
BPO method data
UUID – the unique identifier of this transaction
Parent UUID – the unique identifier of this transaction's parent
Username – the username that initiated this transaction
Method – the method being executed
Elapsed Time(ms) - the time elapsed, in milliseconds, since this invocation has been initiated
SQL statement data
UUID – the unique identifier of this transaction
Parent UUID – the unique identifier of this transaction's parent
Username – the username that initiated this transaction
SQL – the SQL statement being executed
Elapsed Time(ms) - the time elapsed, in milliseconds, since this execution has been initiated
Aggregated transaction tracing statistics - this data is only collected when Cúram JMX configuration parameter curam.jmx.transaction_tracing_enabled is set to true . The aggregated transaction data is exposed as XML. The XML schema is shown in XML Schema for Aggregated Transaction Tracing.
Tracing data is grouped by thread and the meaning of the C element attributes is detailed below:
C – the application layer
M - the invocation target, depending on the application layer it can be a URL, BPO method or an SQL statement
EA - the average elapsed time for an invocation
EMN –the minimum elapsed time for an invocation
EMX – the maximum elapsed time for an invocation
Availability of transaction tracing data: Transaction tracing data is not collected outside JVM process boundaries. This means that full tracing through all application layers is only available when the client and server applications are collocated.