Introscope Metrics

Average Response Time (ms)

Response Time is the time it takes for a request to complete; this provides a basic measurement of application response speed. Therefore: Low response times are desirable. 2. High response times suggest a problem.
1.

The Average Response Time metric averages the response times of all requests that were completed during an interval. Note: The count for Average Response Time is identical to the value of Responses Per Interval.

Concurrent Invocations
Invocations are requests handled by the application and its various parts; concurrent invocations are the requests being handled at a given time.

Introscope calculates the Concurrent Invocations metric by counting the number of requests which were still in flight (that is, which were still being handled) at the end of a particular interval.
1- A low Concurrent Invocations value is desirable. 2- A high Concurrent Invocations value suggets a problem.

Errors Per Interval

Errors are the number of exceptions reported by JVM and HTTP error codes. Examples of errors include:
1- a 404 Page Not Found status reported by the HTTP server. 2- a SQL exception. 3- a Java exception

Obviously, a low error count is desirable.

Responses Per Interval

Es una medida de rendimiento de datos y por lo tanto de rendimiento de la aplicacin. Responses Per Interval reflects number of invocations finished that interval; it is a measure of data throughput and thus of application performance. Generally:

A high number is desirable. A low number is undesirable.

Of course, an unexpected spike in responses could indicate overuse of the external system, such as a denial of service attack on a website.

Stall Count
Stalled requests are those which have not completed within a specified time threshold. If a request is counted as stalled, that does not mean it is hung and will never be completed, but that its execution exceeded the stall threshold.
1- A low count is desirable. 2- A high count is undesirable.

The default stall threshold is 30 seconds.

GC Heap metrics

Garbage Collection is the process of freeing memory taken up by objects no longer in use; once memory is freed up it is useable by other objects. GC Heap|Bytes In Use GC Heap|Bytes In Use reports the amount of memory being currently used by objects. GC Heap|Bytes Total GC Heap|Bytes Total reports the total amount of memory allocated by the JVM.

CPU Utilization
CPU utilization is measured by Introscopes platform monitor, and measures the amount of CPUs being used. There are two different measurements: CPU:Utilization % (process) Percentage of the total computing power of the Introscope host, but limited to the percentage utilized by the JVM process that introscope monitors. CPU:Utilization % (aggregate) Utilization of an individual processor