| Abbreviation | Meaning | Explanation |
|---|---|---|
| Req | Number of requests | Total number of requests to an action (in the defined interval or since start, depending on your interval selection). |
| Time | Time spent in millis (duration) | Total amount of time spent in the action. Although, if the called action is waiting for something to be transported through network or from disk, the value is not equal to spent processor time, this value is usually an important indicator to determine how much some user-clicks cost. |
| CR | Concurrent requests | Number of concurrent requests to the action. This value is not of much interest for time intervals, since it will be any value which was set at the moment of the interval update (and can be even negative since interval updates are fires unsynchronized to prevent performance loss). However, with the default interval (since start) selected it will tell you how many requests are served in the moment. |
| MCR | Max concurrent requests | Max concurrent requests. Unlike the CR value, this value is interesting for intervals; it gives you the info how much parallel load the action suffers. |
| Min | Minimal duration in ms | The minimum amount of time (in milliseconds) spent in an action. For most use-cases you can expect this value to be pretty low or even zero. |
| Max | Maximal duration in ms | The maximum amount of time (in milliseconds) spent in an action. |
| Avg | Average duration in ms | The average amount of time spent in a action. This method will give you the average duration of a request. This is especially interesting if you have different load through the day, by comparing or drawing for example the 5 mins value of AVG you can determine how well your system handles different load. This value is calculated by simple division time / requests and can be slightly incorrent, if you have very many requests which have short duration. |
| Last | Last request durations | The duration of the last request. |
| Err | Number of errors | Total number of uncaught errors of the action (Of course only the doExecute / moskitoDoExecute are monitored). |
| ERate | Error rate in % | Error Rate in Percent |
| Abbreviation | Meaning | Explanation |
|---|---|---|
| Req | Number of requests | Total number of retrieval requests |
| Hit | Number of hits | Total number of hits among the requests |
| HR | Hit ratio | Hit ratio (hits / requests). You want it as high as possible. 1.0 is max. |
| WR | Number of writes | Total number of writes (number of items put into the cache) |
| GC | Number of garbage collected items | Number of garbage collected items (only if the cache implementation uses SoftReferences) |
| RO | Number of rolled over items | Number of rolled over items. Rollover is implementation specific, but for most caches with fixed sizes it will happen. |
| EX | Number of expired items | Number of expired items (only if the cache supports expiration). |
| FI | Number of filtered items | Number of filtered items (only if the cache supports filtering). |
| FR | Fill ratio | Fill ratio, how much storage place is actually used (if implemented by the cache :-)). |
| Abbreviation | Meaning | Explanation |
|---|---|---|
| Req | Number of requests | Total number of requests to a method/interace (in the defined interval or since start, depending on your interval selection). |
| Time | Time spent in millis (duration) | Total amount of time spent in the method / interface. Although, if the called method is waiting for something to be transported from net or from disk, the value is not equal to spent processor time, this value is usually an important indicator to determine how much some functionality costs. |
| CR | Concurrent requests | Number of concurrent requests to a method / interface. This value is not of much interest for time intervals, since it will be any value which was set at the moment of the interval update (and can be even negative since interval updates are fires unsynchronized to prevent performance loss). However, with the default interval (since start) selected it will tell you how many requests are served in the moment. |
| MCR | Max concurrent requests | Max concurrent requests. Unlike the CR value, this value is interesting for intervals; it gives you the info how much parallel load a method / interface suffers. |
| Min | Minimal duration in ms | The minimum amount of time (in milliseconds) spent in a method / interface. For most use-cases you can expect this value to be pretty low or even zero. |
| Max | Maximal duration in ms | The maximum amount of time (in milliseconds) spent in a method / interface. |
| Avg | Average duration in ms | The average amount of time spent in a method / interface. This method will give you the average duration of a request. This is especially interesting if you have different load through the day, by comparing or drawing for example the 5 mins value of AVG you can determine how well your system handles different load. This value is calculated by simple division time / requests and can be slightly incorrent, if you have very many requests which have short duration. |
| Last | Last request durations | The duration of the last request. |
| Err | Number of errors | Total number of uncaught errors of the method / interface. The IOExceptions, ServletExceptions and RuntimeExceptions are counted separately, the ERR value gives your the amount of the Throwables thrown by or through your Filter/Servlet. |
| IOE | Number of IOExceptions | Total number of uncaught IOExceptions. |
| SEE | Number of ServletExceptions | Total number of uncaught ServletExceptions. |
| RTE | Number of RuntimeExceptions | Total number of uncaught RuntimeExceptions. |
| ERate | Error rate in % | The number of uncaught errors as percent of total requests. |
| Abbreviation | Meaning | Explanation |
|---|---|---|
| Cur | Current number of sessions | Current number of sessions (this feature is yet experimental) |
| Min | Min number of sessions | Min number of sessions (this feature is yet experimental) |
| Max | Max number of sessions | Max number of sessions (this feature is yet experimental) |
| New | Number of created sessions | Number of created sessions (this feature is yet experimental) |
| Del | Number of deleted sessions | Number of deleted sessions (this feature is yet experimental) |
| Abbreviation | Meaning | Explanation |
|---|---|---|
| Current | Current amount of memory | Current amount of memory |
| Min | Minimum amount of memory | Minimum amount of memory |
| Max | Maximum amount of memory | Maximum amount of memory |
| Current Mb | Current amount of memory in Mb | Current amount of memory in Mb |
| Min Mb | Minimum amount of memory in Mb | Minimum amount of memory in Mb |
| Max Mb | Maximum amount of memory in Mb | Maximum amount of memory in Mb |
| Abbreviation | Meaning | Explanation |
|---|---|---|
| Free | Free memory | free memory (commited - used) |
| Free MB | Free memory in Mb | free memory (commited - used) in mb |
| Init | Initial amount of memory | represents the initial amount of memory (in bytes) that the Java virtual machine requests from the operating system for memory management during startup. The Java virtual machine may request additional memory from the operating system and may also release memory to the system over time. The value of init may be undefined. |
| Init MB | Initial amount of memory in Mb | represents the initial amount of memory (in megabytes) that the Java virtual machine requests from the operating system for memory management during startup. The Java virtual machine may request additional memory from the operating system and may also release memory to the system over time. The value of init may be undefined. |
| Min Used | Minimum amount of used memory | Minimum amount of memory ever used (in bytes) |
| Min Used MB | Minimum amount of used memory in Mb | Minimum amount of memory ever used (in megabytes) |
| Used | Amount of used memory | The amount of memory currently used (in bytes). |
| Used MB | Amount of used memory in Mb | The amount of memory currently used (in megabytes). |
| Max Used | Maximum amount of used memory | Maximum amount of memory ever used (in bytes) |
| Max Used MB | Maximum amount of used memory in Mb | Maximum amount of memory ever used (in megabytes) |
| Min Commited | Minimum amount of commited memory | Minimum amount of memory ever commited (in bytes) |
| Min Commited MB | Minimum amount of commited memory in Mb | Minimum amount of memory ever commited (in megabytes) |
| Commited | Amount of commited memory | Represents the amount of memory (in bytes) that is guaranteed to be available for use by the Java virtual machine. The amount of committed memory may change over time (increase or decrease). The Java virtual machine may release memory to the system and committed could be less than init. committed will always be greater than or equal to used. |
| Commited MB | Amount of commited memory in Mb | Represents the amount of memory (in megabytes) that is guaranteed to be available for use by the Java virtual machine. The amount of committed memory may change over time (increase or decrease). The Java virtual machine may release memory to the system and committed could be less than init. committed will always be greater than or equal to used. |
| Max Commited | Maximum amount of commited memory | Maximum amount of memory ever commited (in bytes) |
| Max Commited MB | Maximum amount of commited memory in Mb | Maximum amount of memory ever commited (in megabytes) |
| Max | Amount of max memory | Represents the amount of memory (in bytes) that is guaranteed to be available for use by the Java virtual machine. The amount of committed memory may change over time (increase or decrease). The Java virtual machine may release memory to the system and committed could be less than init. committed will always be greater than or equal to used. |
| Max MB | Amount of max memory in Mb | Represents the maximum amount of memory (in megabytes) that can be used for memory management. Its value may be undefined. The maximum amount of memory may change over time if defined. The amount of used and committed memory will always be less than or equal to max if max is defined. A memory allocation may fail if it attempts to increase the used memory such that used > committed even if used <= max would still be true (for example, when the system is low on virtual memory) |
| Abbreviation | Meaning | Explanation |
|---|---|---|
| Req | Number of requests | Total number of requests to a method/interace (in the defined interval or since start, depending on your interval selection). |
| Time | Time spent in millis (duration) | Total amount of time spent in the method / interface. Although, if the called method is waiting for something to be transported from net or from disk, the value is not equal to spent processor time, this value is usually an important indicator to determine how much some functionality costs. |
| CR | Concurrent requests | Number of concurrent requests to a method / interface. This value is not of much interest for time intervals, since it will be any value which was set at the moment of the interval update (and can be even negative since interval updates are fires unsynchronized to prevent performance loss). However, with the default interval (since start) selected it will tell you how many requests are served in the moment. |
| MCR | Max concurrent requests | Max concurrent requests. Unlike the CR value, this value is interesting for intervals; it gives you the info how much parallel load a method / interface suffers. |
| Min | Minimal duration in ms | The minimum amount of time (in milliseconds) spent in a method / interface. For most use-cases you can expect this value to be pretty low or even zero. |
| Max | Maximal duration in ms | The maximum amount of time (in milliseconds) spent in a method / interface. |
| Avg | Average duration in ms | The average amount of time spent in a method / interface. This method will give you the average duration of a request. This is especially interesting if you have different load through the day, by comparing or drawing for example the 5 mins value of AVG you can determine how well your system handles different load. This value is calculated by simple division time / requests and can be slightly incorrent, if you have very many requests which have short duration. |
| Last | Last request durations | The duration of the last request. |
| Err | Number of errors | Total number of uncaught errors of the method / interface. |
| ERate | Error rate in % | The number of uncaught errors as percent of total requests. |
| Abbreviation | Meaning | Explanation |
|---|---|---|
| Req | Number of requests | Total number of requests to a method/interace (in the defined interval or since start, depending on your interval selection). |
| Time | Time spent in millis (duration) | Total amount of time spent in the method / interface. Although, if the called method is waiting for something to be transported from net or from disk, the value is not equal to spent processor time, this value is usually an important indicator to determine how much some functionality costs. |
| CR | Concurrent requests | Number of concurrent requests to a method / interface. This value is not of much interest for time intervals, since it will be any value which was set at the moment of the interval update (and can be even negative since interval updates are fires unsynchronized to prevent performance loss). However, with the default interval (since start) selected it will tell you how many requests are served in the moment. |
| MCR | Max concurrent requests | Max concurrent requests. Unlike the CR value, this value is interesting for intervals; it gives you the info how much parallel load a method / interface suffers. |
| Min | Minimal duration in ms | The minimum amount of time (in milliseconds) spent in a method / interface. For most use-cases you can expect this value to be pretty low or even zero. |
| Max | Maximal duration in ms | The maximum amount of time (in milliseconds) spent in a method / interface. |
| Avg | Average duration in ms | The average amount of time spent in a method / interface. This method will give you the average duration of a request. This is especially interesting if you have different load through the day, by comparing or drawing for example the 5 mins value of AVG you can determine how well your system handles different load. This value is calculated by simple division time / requests and can be slightly incorrent, if you have very many requests which have short duration. |
| Last | Last request durations | The duration of the last request. |
| Err | Number of errors | Total number of uncaught errors of the method / interface. The IOExceptions, ServletExceptions and RuntimeExceptions are counted separately, the ERR value gives your the amount of the Throwables thrown by or through your Filter/Servlet. |
| IOE | Number of IOExceptions | Total number of uncaught IOExceptions. |
| SEE | Number of ServletExceptions | Total number of uncaught ServletExceptions. |
| RTE | Number of RuntimeExceptions | Total number of uncaught RuntimeExceptions. |
| ERate | Error rate in % | The number of uncaught errors as percent of total requests. |
| Abbreviation | Meaning | Explanation |
|---|---|---|
| Get | Number of get calls | Total number of calls to the method V get(K). |
| mGet | Missed get calls | Total number of calls to the method V get(K) which returned null as result |
| mGet_R | Missed get calls ratio | The ratio of missed get calls (calls that returned null) to total get calls. For most (but not all) usecases a high value (>0.5) means, that your data retrieval strategy is inefficent. |
| hGet_R | Hit get calls ratio | The ratio of hit get calls (hit get calls are those, which returned a not null object, as opposite to the missed get calls). The equation mGet_R+hGet R=1 should always be true. |
| Put | Number of put calls | Total number of calls to the method V put(K, V). |
| owPut | Puts which overwrite | Number of put calls which actually overwrite data in the storage. |
| owPut_R | Overwrite put ratio | Ratio of overwriting put calls to total put calls. Gives you the feeling how much of the data is actually being replaced. |
| newPut_R | New put ratio | Ratio of put calls which are puting new data into the storage to total put calls. Gives you the feeling how much of the data is actually being placed in the storage. Note that 'owPut R'+'newPut R' should be always 1. |
| Rem | Number of remove calls | Total number of calls to V remove(K) method |
| no_Rem | No effect removes | Number of calls to the remove method which have no effect because there was no object under the given key. |
| no_Rem_R | No effect removes ratio | Ratio between no-effect-removes and removes. If this value is too high (max is 1.0) you are trying to remove non-existing objects way too often, and should have a look at your algorithms. |
| Put/Get_R | Put/Get Ratio | Put/Get ratio. If this value is above 1.0 you are probably doing something wrong. |
| Put/Rem_R | Put/Remove Ratio | Put/Remove ratio. If this value is to high and owPut R is low your application is probably leaking memory. |
| Size | Size | The size of the storage (number of contained elements). |
| cKeyC | Calls to containsKey | Total number of calls to containsKey method. |
| cKeyH | Hits to containsKey | Total number of calls to containsKey method, which returned true. |
| cKeyHR | containsKey hit ratio | Number of calls to containsKey method which returned true / total number of calls. If you are using the storage as a cache you will want this value high (1.0 is max). |
| cValC | Calls to containsValue | Total number of calls to containsValue method. Since contains value method is very time intensive, you shouldn't use it too often. |
| cValH | Hits to containsValue | Total number of calls to containsValue method, which returned true. |
| cValHR | containsValue hit ratio | Number of calls to containsValue method which returned true / total. As stated above, the containsValue method is very time intensive (at least linear to the number of items in the undelying map implementation), so having using it with low hit rate is a performance killer. |
| Abbreviation | Meaning | Explanation |
|---|---|---|
| Started | Total number of started threads | Total number of started threads |
| Min Cur | Min number of currently running threads | Min number of currently running threads |
| Current | Number of currently running threads | Number of currently running threads |
| Max Cur | Max number of currently running threads | Max number of currently running threads |
| Daemon | Total number of started daemon threads | Total number of started daemon threads |
| Abbreviation | Meaning | Explanation |
|---|---|---|
| Free | Free memory | free memory (commited - used) |
| Free MB | Free memory in Mb | free memory (commited - used) in mb |
| Init | Initial amount of memory | represents the initial amount of memory (in bytes) that the Java virtual machine requests from the operating system for memory management during startup. The Java virtual machine may request additional memory from the operating system and may also release memory to the system over time. The value of init may be undefined. |
| Init MB | Initial amount of memory in Mb | represents the initial amount of memory (in megabytes) that the Java virtual machine requests from the operating system for memory management during startup. The Java virtual machine may request additional memory from the operating system and may also release memory to the system over time. The value of init may be undefined. |
| Min Used | Minimum amount of used memory | Minimum amount of memory ever used (in bytes) |
| Min Used MB | Minimum amount of used memory in Mb | Minimum amount of memory ever used (in megabytes) |
| Used | Amount of used memory | The amount of memory currently used (in bytes). |
| Used MB | Amount of used memory in Mb | The amount of memory currently used (in megabytes). |
| Max Used | Maximum amount of used memory | Maximum amount of memory ever used (in bytes) |
| Max Used MB | Maximum amount of used memory in Mb | Maximum amount of memory ever used (in megabytes) |
| Min Commited | Minimum amount of commited memory | Minimum amount of memory ever commited (in bytes) |
| Min Commited MB | Minimum amount of commited memory in Mb | Minimum amount of memory ever commited (in megabytes) |
| Commited | Amount of commited memory | Represents the amount of memory (in bytes) that is guaranteed to be available for use by the Java virtual machine. The amount of committed memory may change over time (increase or decrease). The Java virtual machine may release memory to the system and committed could be less than init. committed will always be greater than or equal to used. |
| Commited MB | Amount of commited memory in Mb | Represents the amount of memory (in megabytes) that is guaranteed to be available for use by the Java virtual machine. The amount of committed memory may change over time (increase or decrease). The Java virtual machine may release memory to the system and committed could be less than init. committed will always be greater than or equal to used. |
| Max Commited | Maximum amount of commited memory | Maximum amount of memory ever commited (in bytes) |
| Max Commited MB | Maximum amount of commited memory in Mb | Maximum amount of memory ever commited (in megabytes) |
| Max | Amount of max memory | Represents the amount of memory (in bytes) that is guaranteed to be available for use by the Java virtual machine. The amount of committed memory may change over time (increase or decrease). The Java virtual machine may release memory to the system and committed could be less than init. committed will always be greater than or equal to used. |
| Max MB | Amount of max memory in Mb | Represents the maximum amount of memory (in megabytes) that can be used for memory management. Its value may be undefined. The maximum amount of memory may change over time if defined. The amount of used and committed memory will always be less than or equal to max if max is defined. A memory allocation may fail if it attempts to increase the used memory such that used > committed even if used <= max would still be true (for example, when the system is low on virtual memory) |
