Common Terms: Backend
Common Terms: Backend
To understand Introscope metrics, you should understand how Introscope uses some common terms. backend An external system, such as a database, a mail server, a transaction processing system (such as CICS or Tuxedo), or a messaging system (such as WebSphere MQ). concurrency and concurrent invocations Concurrent methods are methods that started during an interval without finishing during the same interval. Since you want methods to complete quickly, an unusually high value for concurrent Invocations is undesirable. errors Errors generated by the application or system being monitored. frontend The component of an application that first handles an incoming request. It may be a Servlet, a JSP, a management DB, an EJB or some other component. harvest The process in which Introscope gathers data from Collectors. interval A user-defined time slice used to define and average metrics. In Introscope this is usually 7.5 seconds, though the way some of the monitored systems capture data sometimes necessitates a different interval. response Response always refers to method execution. Response is measured as: 1. count, referring to the number of transactions finished during that interval. 2. time, referring to the time it took to execute a method, in milliseconds. Responses Per Interval is the standard Introscope throughput metric. response time The time it took to execute a method. May be measured as:
1- average response time (ms)The average time, in milliseconds, it took to execute the method during the interval.\ 2- response time, min and maxThe lowest and highest response times during the interval.
rate The number of method executions per second or time interval. stall An instance where a methods invocation time has exceeded a threshold defined by an administrator.