Average Result Processing Time metrics are not showing up in the Investigator.

Document ID : KB000011585
Last Modified Date : 14/02/2018
Show Technical Document Details

 The ART (Average Response Time) and ARPT (Average Result Processing Time) are two different metrics and are sometimes confused for one another.  The Average Result Processing Time is measured in milliseconds and is the average time spent processing a ResultSet from the end of the executeQuery() call to the invocation of the ResultSet's close() method.


 My SQL metrics are not showing the Average Result Processing Time metric.  How can I get them to show up in the Investigator?

All supported APM versions on any supported environments.

 The Average Result Processing Time is a metric that is generated by the instrumentation on the Close method of a System.Data.SqlClient.SqlDataReader object.  The SQL node not having this metric is most likely from an SQL statement not having returned a data set or a result set that was processed via a data reader and/or has not triggered the Close method on a System.Data.SqlClient.SqlDataReader object.


 If an SQL statement is executed by an SQL method that is not returning a data set such as ExecuteNonQuery(), then it will not trigger the processing and closing of a data reader object.


 However, a workaround to enable the ARPT metric for the above statement would need an engagement with CA Services to assist in examining those statements in more detail to see if they can come up with a new tracer to give an ARPT equivalent type metric.

Additional Information:

Configure SQL monitoring for Java