Oracle® Enterprise Manager Oracle Fusion Middleware Metric Reference Manual, 11g Release 1 (11.1.0.1) Part Number E18807-01 |
|
|
PDF · Mobi · ePub |
The oracle_coherence metrics provide description, collection statistics, data source, multiple thresholds (where applicable), and user action information for each metric.
Aggregated cache performance across all nodes on which a cache is running
The rough number of cache hits during the last collection interval. A cache hit is a read operation invocation (i.e. get()) for which an entry exists in this map.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-1 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of milliseconds (during the last collection interval) for the get() operations for which an entry existed in this map.
The following table shows how often the metric's value is collected.
The rough number of cache misses during the last collection interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-3 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of milliseconds (during the last collection interval) for the get() operations for which no entry existed in this map.
The following table shows how often the metric's value is collected.
The cummulative time (in millis) spent on load operations during the last collection interval; -1 if persistence type is NONE.
The following table shows how often the metric's value is collected.
The total number of load operations during the last collection interval; -1 if persistence type is NONE.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-6 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The cummulative time (in milliseconds) spent on store and erase operations during the last collection interval; -1 if persistence type is NONE or READ-ONLY.
The following table shows how often the metric's value is collected.
The total number of store and erase operations during the last collection interval; -1 if persistence type is NONE or READ-ONLY.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-8 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of get() operations during the last collection interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-9 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of milliseconds spent on get() operations during the last collection interval.
The following table shows how often the metric's value is collected.
The total number of put() operations during the last collection interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-11 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric addresses the cache configuration
The BatchFactor attribute is used to calculate the `soft-ripe` time for write-behind queue entries. A queue entry is considered to be `ripe` for a write operation if it has been in the write-behind queue for no less than the QueueDelay interval. The `soft-ripe` time is the point in time prior to the actual `ripe` time after which an entry will be included in a batched asynchronous write operation to the CacheStore (along with all other `ripe` and `soft-ripe` entries). This attribute is only applicable if asynchronous writes are enabled (i.e. the value of the QueueDelay attribute is greater than zero) and the CacheStore implements the storeAll() method. The value of the element is expressed as a percentage of the QueueDelay interval. Valid values are doubles in the interval [0.0, 1.0].
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The cache description.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The time-to-live for cache entries in milliseconds. Value of zero indicates that the automatic expiry is disabled. Change of this attribute will not affect already-scheduled expiry of existing entries.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of milliseconds between cache flushes. Value of zero indicates that the cache will never flush.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The limit of the cache size measured in units. The cache will prune itself automatically once it reaches its maximum unit level. This is often referred to as the `high water mark` of the cache.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of units to which the cache will shrink when it prunes. This is often referred to as a `low water mark` of the cache.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The persistence type for this cache. Possible values include: NONE, READ-ONLY, WRITE-THROUGH, WRITE-BEHIND.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of seconds that an entry added to a write-behind queue will sit in the queue before being stored via a CacheStore. Applicable only for WRITE-BEHIND persistence type.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The RefreshFactor attribute is used to calculate the `soft-expiration` time for cache entries. Soft-expiration is the point in time prior to the actual expiration after which any access request for an entry will schedule an asynchronous load request for the entry.
This attribute is only applicable for a ReadWriteBackingMap which has an internal LocalCache with scheduled automatic expiration. The value of this element is expressed as a percentage of the internal LocalCache expiration interval. Valid values are doubles in the interval[0.0, 1.0]. If zero, refresh-ahead scheduling will be disabled.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The timestamp when this model was last retrieved from a corresponding node. For local servers it is the local time.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The maximum size of the write-behind queue for which failed CacheStore write operations are requeued. If zero, the write-behind requeueing will be disabled. Applicable only for WRITE-BEHIND persistence type.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The cache performance metrics
The average number of milliseconds per get() invocation since the cache statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The average number of milliseconds per get() invocation tduring the last collection interval.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The average number of milliseconds per get() invocation that is a hit.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The average number of milliseconds per get() invocation hat is a hit during the last collection interval.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The average number of milliseconds per get() invocation that is a miss.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The average number of milliseconds per get() invocation that is a miss during the last collection interval.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The average number of milliseconds per put() invocation since the cache statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The average number of milliseconds per put() invocation since the cache statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The rough number of cache hits since the cache statistics were last reset. A cache hit is a read operation invocation (i.e. get()) for which an entry exists in this map.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The rough number of cache hits during the last collection interval. A cache hit is a read operation invocation (i.e. get()) for which an entry exists in this map.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-13 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of milliseconds (since the last time statistics were reset) for the get() operations for which an entry existed in this map.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of milliseconds (during the last collection interval) for the get() operations for which an entry existed in this map.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The rough number of cache misses since the cache statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The rough number of cache misses during the last collection interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-14 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of milliseconds ( since the last time statistics were reset) for the get() operations for which no entry existed in this map.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of milliseconds (during the last collection interval) for the get() operations for which no entry existed in this map.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The rough probability (0 <= p <= 1) that the next invocation will be a hit, based on the statistics collected since the last reset of the cache statistics.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The size of the write-behind queue size. Applicable only for WRITE-BEHIND persistence type.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of entries in the cache.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The average number of entries stored per CacheStore write operation. A call to the store() method is counted as a batch of one, whereas a call to the storeAll() method is counted as a batch of the passed Map size. The value of this attribute is -1 if the persistence type is NONE.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The average time (in millis) spent per write operation; -1 if persistence type is NONE.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of CacheStore failures (load, store and erase operations); -1 if persistence type is NONE.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of CacheStore failures (load, store and erase operations) during the last collection interval; -1 if persistence type is NONE.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The cumulative number of load operations per node; -1 if persistence type is NONE
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The cummulative time (in millis) spent on load operations during the last collection interval; -1 if persistence type is NONE.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of load operations; -1 if persistence type is NONE.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of load operations during the last collection interval; -1 if persistence type is NONE.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-15 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The cummulative time (in milliseconds) spent on store and erase operations; -1 if persistence type is NONE or READ-ONLY.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The cummulative time (in milliseconds) spent on store and erase operations during the last collection interval; -1 if persistence type is NONE or READ-ONLY.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of store and erase operations; -1 if persistence type is NONE or READ-ONLY.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of store and erase operations during the last collection interval; -1 if persistence type is NONE or READ-ONLY.
The following table shows how often the metric's value is collected.
Table 2-16 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of get() operations since the cache statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of get() operations during the last collection interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-17 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of milliseconds spent on get() operations since the cache statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of milliseconds spent on get() operations during the last collection interval.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of put() operations since the cache statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of put() operations during the last collection interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-18 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "Service" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "Service" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "Service" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of milliseconds spent on put() operations since the cache statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
This cluster metrics are described.
The name of the cluster.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of cluster nodes.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The license mode that this cluster is using. Possible values are Evaluation, Development or Production.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The member id for the cluster member that is co-located with the reporting MBeanServer; -1 if the cluster service is not running.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
An array of all existing cluster members.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The aggregated coherence cluster metrics are descirbed
The number of entries in the cache.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of entries present in the cache during the last collection interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-19 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
< |
Not Defined |
Not Defined |
1 |
Cache deleted or new cache added |
For this metric you can set different warning and critical threshold values for each "Cluster Name" object.
If warning or critical threshold values are currently set for any "Cluster Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Cluster Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of cluster nodes.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of cluster nodes present during the last collection interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-20 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
< |
Not Defined |
Not Defined |
1 |
Cache deleted or new cache added |
For this metric you can set different warning and critical threshold values for each "Cluster Name" object.
If warning or critical threshold values are currently set for any "Cluster Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Cluster Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The publisher success rate from the viewing node to the viewed node since the statistics were last reset.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-21 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
< |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each "Cluster Name" object.
If warning or critical threshold values are currently set for any "Cluster Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Cluster Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The receiver success rate from the viewing node to the viewed node since the statistics were last reset.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-22 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
< |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each "Cluster Name" object.
If warning or critical threshold values are currently set for any "Cluster Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Cluster Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The coherence cluster alert metrics are described.
The name of the cluster.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The total number of cluster nodes.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The change in the number of nodes since the last collection.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-23 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 60 Seconds |
After Every Sample |
< |
0 |
-5 |
1 |
Nodes departed the Cluster |
For this metric you can set different warning and critical threshold values for each "Cluster Name" object.
If warning or critical threshold values are currently set for any "Cluster Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Cluster Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The change in the number of nodes since the last time statistics were collected.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-24 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 60 Seconds |
After Every Sample |
> |
0 |
Not Defined |
1 |
Nodes added to Cluster |
For this metric you can set different warning and critical threshold values for each "Cluster Name" object.
If warning or critical threshold values are currently set for any "Cluster Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Cluster Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The coherence connection metric s are described.
The time duration (in milliseconds) that the client has been connected.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The backlog (in bytes) of the outgoing queue
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The backlog of the outgoing message queue.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The timestamp when this model was last retrieved from a corresponding node. For local servers it is the local time.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The IP address of the corresponding client.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The port of the corresponding client.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The date/time value (in local time) that the corresponding client connected to the Proxy.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of bytes recieved since the last time the statistics were reset.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-25 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name", "NodeID", and "UUID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name", "NodeID", and "UUID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name", "NodeID", and "UUID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of bytes sent since the statistics were last reset.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-26 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name", "NodeID", and "UUID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name", "NodeID", and "UUID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name", "NodeID", and "UUID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The connection manager metrics are described.
The number of client connections.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The IP address of the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The pool capacity (in bytes) of the incoming buffer.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of buffers in the incoming pool.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The pool capacity (in bytes) of the outgoing buffer.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of buffers in the outgoing pool.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The backlog (in bytes) of the outgoing queue.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The backlog of the outgoing message queue.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The timestamp when this model was last retrieved from a corresponding node. For local servers it is the local time.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of bytes received by the Proxy host since the statistics were last reset.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-27 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of bytes sent by the Proxy host since the statistics were last reset.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-28 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
Garbage Collector memory pool metrics after completion of garbage collection per node.
Garbage Collector Name.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Coherence Node ID.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
GC Thread Count per garbage collector .
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
GC Start Time for a garbage collector.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
GC End Time for a garbage collector.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Garbage Collector key.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The amount of memory that is guaranteed to be available for use by the JVM after GC.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The initial amount of memory that the JVM requested for a memory pool from the operating system during startup.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Garbage Collector memory pool metrics before completion of garbage collection per node.
Garbage Collector Name.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Coherence Node ID.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
GC Thread Count per garbage collector
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-29 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
GC Start Time for a garbage collector.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
GC End Time for a garbage collector.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Garbage Collector key.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The amount of memory that is guaranteed to be available for use by the JVM after GC.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-30 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The initial amount of memory that the JVM requested for a memory pool from the operating system during startup.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-31 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The maximum amount of memory that can be used by the JVM.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-32 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The amount of memory currently in use.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-33 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
Metrics from a garbage collection for each garbage collector per node.
Garbage Collector Name.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Coherence Node ID
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Number of items garbagee collected
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-34 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
Number of items garbage collected in a sample interval
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-35 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
Metrics indicating session usage by a web application using Coherence.
Coherence Web Application ID.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Coherence Node ID.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The fully qualified class name of the HttpSessionCollection implementation in use.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The fully qualified class name of the Factory implementation in use.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The name of the local cache that stores non-distributed session attributes.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The number of non-distributed session attributes stored in the local session attribute cache.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The name of the local cache that stores non-distributed sessions.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The number of non-distributed sessions stored in the local session cache
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The average size (in bytes) of the session attributes stored in the "overflow" clustered cache.
The name of the clustered cache that stores the "large attributes" that exceed a certain size.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The maximum size (in bytes) of a session attribute stored in the "overflow" clustered cache.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The minimum length (in bytes) that the serialized form of an attribute value must be for that attribute value to be stored in the separate "overflow" cache.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The number of updates to session attributes stored in the "overflow" clustered cache.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The number of updates to session attributes stored in the "overflow" clustered cache per minute.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The name of the clustered cache that stores javax.servlet.ServletContext attributes.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The name of the web application Servlet Context.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The average lifetime (in seconds) of session objects invalidated.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The name of the clustered cache that stores serialized session objects.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The length (in characters) of generated session IDs.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The maximum size (in bytes) of a session object placed in the session storage clustered cache.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The number of session objects that are pinned to this instance of the web application.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The session expiration time (in seconds).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The number of updates of session object stored in the session storage clustered cache.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Metrics indicating session usage by a web application using Coherence aggregated over all nodes where application session information is stored.
This metric is a subset of Http Session Metrics aggregated over nodes where application session data is stored. Therefore, metric column descriptions are the same as those contained in the Http Session metric, but Application ID is the key and aggregation of metrics happens over all nodes where application id session information is stored.
The application id number.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-36 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The number of attributes in the local attribute cache
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-37 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The number of updates of session object stored in the session storage clustered cache per minute.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-38 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The updates to attributes stored in the overflow cache.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-39 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The number of attributes stored in the overflow cache per minute.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-40 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The updates to the object store in the session cache.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-41 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The number of updates to the object store in the session cache per minute.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-42 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
Memory usage metrics for heap and non-heap memory for each Coherence node.
Coherence Node ID.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The amount of heap memory that is guaranteed to be available for use by the JVM.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-43 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The initial amount of heap memory that the JVM requested for a memory pool from the operating system during startup.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The maximum amount of heap memory that can be used by the JVM.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-44 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The amount of heap memory currently in use.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-45 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The amount of non-heap memory that is guaranteed to be available for use by the JVM.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-46 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The initial amount of non-heap memory that the JVM requested for a memory pool from the operating system during startup.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-47 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The amount of non-heap memory currently in use.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-48 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The approximate number of objects for which finalization is pending.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-49 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The node performance metrics aggregated over caches are described.
The total number of get() operations since the cache statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of get() operations during the last collection interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-50 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of put() operations since the cache statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of put() operations during the last collection interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-51 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The node configuration metrics are described.
The buffer size of the unicast datagram socket used by the Publisher, measured in the number of packets. Changing this value at runtime is an inherently unsafe operation that will pause all network communications and may result in the termination of all cluster services.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The buffer size of the unicast datagram socket used by the Receiver, measured in the number of packets. Changing this value at runtime is an inherently unsafe operation that will pause all network communications and may result in the termination of all cluster services.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The maximum number of packets to send without pausing. Anything less than one (e.g. zero) means no limit.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of milliseconds to pause between bursts. Anything less than one (e.g. zero) is treated as one millisecond.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
Indicates whether flow control is enabled for this node.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
Specifies how messages will be formatted before being passed to the log destination
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
Specifies which logged messages will be output to the log destination. Valid values are non-negative integers or -1 to disable all logger output.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The maximum number of characters that the logger daemon will process from the message queue before discarding all remaining messages in the queue. Valid values are integers in the range [0...]. Zero implies no limit.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The Member`s machine Id.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
A configured name that should be the same for all Members that are on the same physical machine, and different for Members that are on different physical machines.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
A configured name that must be unique for every Member.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The maximum amount of memory that the JVM will attempt to use in MB.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The IP address of the Member`s MulticastSocket for group communication.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
Specifies whether or not this Member uses multicast for group communication. If false, this Member will use the WellKnownAddresses to join the cluster and point-to-point unicast to communicate with other Members of the cluster.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The port of the member`s MulticastSocket for group communication.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The percentage (0 to 100) of the servers in the cluster that a packet will be sent to, above which the packet will be multicasted and below which it will be unicasted.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The time-to-live for multicast packets sent out on this Member`s MulticastSocket.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
Indicates whether or not the early packet loss detection protocol is enabled.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
A configured name that should be the same for Members that are in the same process (JVM), and different for Members that are in different processes. If not explicitly provided, for processes running with JRE 1.5 or higher the name will be calculated internally as the Name attribute of the system RuntimeMXBean, which normally represents the process identifier (PID).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The product edition this Member is running. Possible values are: Standard Edition (SE), Enterprise Edition (EE), Grid Edition (GE).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
A configured name that should be the same for Members that are on the same physical "rack" (or frame or cage), and different for Members that are on different physical "racks".
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The timestamp when this model was last retrieved from a corresponding node. For local servers it is the local time.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The minimum number of milliseconds that a packet will remain queued in the Publisher`s re-send queue before it is resent to the recipient(s) if the packet has not been acknowledged. Setting this value too low can overflow the network with unnecessary repetitions. Setting the value too high can increase the overall latency by delaying the re-sends of dropped packets. Additionally, change of this value may need to be accompanied by a change in SendAckDelay value.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
A configured name that can be used to indicate the role of a Member to the application. While managed by Coherence, this property is used only by the application
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
A configured name that should be the same for Members that are on the same physical site (e.g. data center), and different for Members that are on different physical sites.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The date/time value (in cluster time) that this Member joined the cluster.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The maximum total number of packets in the send and resend queues that forces the publisher to pause client threads. Zero means no limit.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of milliseconds to pause client threads when a traffic jam condition has been reached. Anything less than one (e.g. zero) is treated as one millisecond.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The node performance metrics are described.
Number of CPU cores for the machine this Member is running on.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The Member`s machine Id.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
A configured name that should be the same for all Members that are on the same physical machine, and different for Members that are on different physical machines.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
A configured name that must be unique for every Member.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total amount of memory in the JVM available for new objects in MB.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-52 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
< |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each "Id" object.
If warning or critical threshold values are currently set for any "Id" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Id" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The efficiency of packet loss detection and retransmission. A low efficiency is an indication that there is a high rate of unnecessary packet retransmissions.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of packets which were bundled prior to transmission. The total number of network transmissions is equal to (PacketsSent - PacketsBundled).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of packets which were bundled prior to transmission during the last collection interval. The total number of network transmissions is equal to (PacketsSent - PacketsBundled).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of packets received since the node statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of packets received during the last collection interval.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of duplicate packets received since the node statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of duplicate packets received since the node statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of packets resent since the node statistics were last reset. A packet is resent when there is no ACK received within a timeout period.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of packets resent during the last collection interval. A packet is resent when there is no ACK received within a timeout period.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of packets resent ahead of schedule. A packet is resent ahead of schedule when there is a NACK indicating that the packet has not been received.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of packets resent ahead of schedule during the last collection interval. A packet is resent ahead of schedule when there is a NACK indicating that the packet has not been received. .
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of packet retransmissions which were later proven unnecessary.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of packet retransmissions sent during the last collection interval which were later proven unnecessary.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of packets sent since the node statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of packets sent during the last collection interval.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
A configured name that should be the same for Members that are in the same process (JVM), and different for Members that are in different processes. If not explicitly provided, for processes running with JRE 1.5 or higher the name will be calculated internally as the Name attribute of the system RuntimeMXBean, which normally represents the process identifier (PID).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The publisher success rate for this cluster node since the node statistics were last reset. Publisher success rate is a ratio of the number of packets successfully delivered in a first attempt to the total number of sent packets. A failure count is incremented when there is no ACK received within a timeout period. It could be caused by either very high network latency or a high packet drop rate.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The publisher success rate for this cluster node during the last collection interval. Publisher success rate is a ratio of the number of packets successfully delivered in a first attempt to the total number of sent packets. A failure count is incremented when there is no ACK received within a timeout period. It could be caused by either very high network latency or a high packet drop rate.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-53 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each "Id" object.
If warning or critical threshold values are currently set for any "Id" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Id" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
A configured name that should be the same for Members that are on the same physical "rack" (or frame or cage), and different for Members that are on different physical "racks".
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The receiver success rate from the viewing node to the viewed node during the last collection interval.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The receiver success rate from the viewing node to the viewed node during the last collection interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-54 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
< |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each "Id" object.
If warning or critical threshold values are currently set for any "Id" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Id" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The timestamp when this model was last retrieved from a corresponding node. For local servers it is the local time.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
A configured name that can be used to indicate the role of a Member to the application. While managed by Coherence, this property is used only by the application.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of packets currently scheduled for delivery. This number includes both packets that are to be sent immediately and packets that have already been sent and awaiting for acknowledgment. Packets that do not receive an acknowledgment within ResendDelay interval will be automatically resent.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-55 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each "Id" object.
If warning or critical threshold values are currently set for any "Id" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Id" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
A configured name that should be the same for Members that are on the same physical site (e.g. data center), and different for Members that are on different physical sites.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of recovered TcpRing disconnects since the node statistics were last reset. A recoverable disconnect is an abnormal event that is registered when the TcpRing peer drops the TCP connection, but recovers after no more then maximum configured number of attempts.This value will be -1 if the TcpRing is disabled.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of recovered TcpRing disconnects during the last collection interval. A recoverable disconnect is an abnormal event that is registered when the TcpRing peer drops the TCP connection, but recovers after no more then maximum configured number of attempts.This value will be -1 if the TcpRing is disabled.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of TcpRing timeouts since the node statistics were last reset. A timeout is a normal, but relatively rare event that is registered when the TcpRing peer did not ping this node within a heartbeat interval. This value will be -1 if the TcpRing is disabled.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of TcpRing timeouts during the last collection interval. A timeout is a normal, but relatively rare event that is registered when the TcpRing peer did not ping this node within a heartbeat interval. This value will be -1 if the TcpRing is disabled.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The date/time value (in cluster time) that this Member joined the cluster.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The id of the cluster node to which this node is having the most difficulty communicating, or -1 if none is found. A channel is considered to be weak if either the point-to-point publisher or receiver success rates are below 1.0.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
Point to point metrics.
The number of packets addressed to the viewed member that the viewing member is currently deferring to send. The viewing member will delay sending these packets until the number of outstanding packets falls below the value of the Threshold attribute. The value of this attribute is only meaningful if the viewing member has FlowControl enabled.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
Indicates whether or not the viewing member is currently deferring packets to the viewed member. The value of this attribute is only meaningful if the viewing member has FlowControl enabled.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of milliseconds that have elapsed since the viewing member last received an acknowledgment from the viewed member.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of milliseconds that have elapsed since the viewing member last sent a packet to the viewed member.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of milliseconds that have elapsed since the viewing member declared the viewed member as slow, or -1 if the viewed member has never been declared slow.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of packets that the viewing member has sent to the viewed member which have yet to be acknowledged. The value of this attribute is only meaningful if the viewing member has FlowControl enabled.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
Indicates whether or not the viewing member currently considers the viewed member to be unresponsive. The value of this attribute is only meaningful if the viewing member has FlowControl enabled.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The percentage of time since the last time statistics were reset in which the viewing member considered the viewed member to be unresponsive. Under normal conditions this value should be very close to 0.0. Values near 1.0 would indicate that the viewed node is nearly inoperable, likely due to extremely long GC pauses. The value of this attribute is only meaningful if the viewing member has FlowControl enabled.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The publisher success rate from the viewing node to the viewed node since the statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The publisher success rate for this cluster node during the last collection interval. Publisher success rate is a ratio of the number of packets successfully delivered in a first attempt to the total number of sent packets. A failure count is incremented when there is no ACK received within a timeout period. It could be caused by either very high network latency or a high packet drop rate.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The receiver success rate from the viewing node to the viewed node since the statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The receiver success rate from the viewing node to the viewed node during the last collection interval.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The maximum number of outstanding packets for the viewed member that the viewing member is allowed to accumulate before initiating the deferral algorithm. The value of this attribute is only meaningful if the viewing member has FlowControl enabled.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
System properties and resources about the operating system on which the Coherence node JVM is running.
Coherence Node ID.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Operating system architecture.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Number of processors available to the Coherence node JVM.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Amount of virtual memory that is guaranteed to be available to running Coherence node JVM in bytes.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-56 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The amount of free physical memory.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-57 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The amount of free swap space.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-58 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
Maximum permissible open file descriptor.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Operating system name.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Current count of open file descriptors.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-59 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The CPU time used by the process on which the Java virtual machine is running.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The amount of total physical memory.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Response metrics.
This metric shows the response status.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-60 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every Minute |
After Every Sample |
= |
Not Defined |
0 |
1 |
The Coherence Cluster instance is down |
Coherence Node Runtime metrics
Internal key metric
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Coherence Node ID
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Start or input parameters a Coherence Node JVM process is started with
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
Virtual Machine name
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Seconds |
The service configuration metrics are described.
The total number of partitions that each cache storage is divided into.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The default timeout value in milliseconds for requests that can be timed-out (e.g. implement the com.tangosol.net.PriorityTask interface), but do not explicitly specify the request timeout value.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
Specifies whether or not the service is running.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
Statistics for this service in human readable format.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The High Availability status for this service. The value of MACHINE-SAFE means that all the cluster nodes running on any given machine could be stoppped at once without data loss. The value of NODE-SAFE means that any cluster node could be stoppped without data loss. The value of ENDANGERED indicates that abnormal termination of any cluster node that runs this service may cause data loss.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
Specifies whether local storage is enabled for this cluster Member.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The amount of time in milliseconds that a task can execute before it is considered hung. Note that a posted task that has not yet started is never considered as hung.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The default timeout value in milliseconds for tasks that can be timed-out (e.g. implement the com.tangosol.net.PriorityTask interface), but do not explicitly specify the task execution timeout value.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The service performance metrics are described.
The number of backups for every cache storage.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of partitions that this Member backs up (responsible for the backup storage).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of partitions that this Member owns (responsible for the primary storage).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of partitions that are not currently backed up.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of primary and backup partitions which remain to be transferred until the partition distribution across the storage enabled service members is fully balanced.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of partitions that are backed up on the same machine where the primary partition owner resides.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The timestamp when this model was last retrieved from a corresponding node. For local servers it is the local time.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The average duration (in milliseconds) of an individual synchronous request issued by the service since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The maximum duration (in milliseconds) of a synchronous request issued by the service since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of pending synchronous requests issued by the service.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The duration (in milliseconds) of the oldest pending synchronous request issued by the service.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of timed-out requests since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of timed out requests per node since the last collection interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-61 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of synchronous requests issued by the service since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of synchronous requests issued by the service during the last collection interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-62 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The High Availability status for this service. The value of MACHINE-SAFE means that all the cluster nodes running on any given machine could be stoppped at once without data loss. The value of NODE-SAFE means that any cluster node could be stoppped without data loss. The value of ENDANGERED indicates that abnormal termination of any cluster node that runs this service may cause data loss.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-63 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
MATCH |
Not Defined |
ENDANGERED |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
Specifies the total number of cluster nodes running this Service for which local storage is enabled.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The average duration (in milliseconds) of an individual task execution.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The size of the backlog queue that holds tasks scheduled to be executed by one of the service threads.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of executed tasks since the last time the statistics were reset
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of executed tasks during the last collection interval.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of currently executing hung tasks.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The longest currently executing hung task duration in milliseconds.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The ID of the longest currently executing hung task.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The maximum size of the backlog queue since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of timed-out tasks since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of timed out tasks since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of abandoned threads from the service thread pool. A thread is abandoned and replaced with a new thread if it executes a task for a period of time longer than execution timeout and all attempts to interrupt it fail.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of abandoned threads from the service thread pool during the last collection interval. A thread is abandoned and replaced with a new thread if it executes a task for a period of time longer than execution timeout and all attempts to interrupt it fail.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-64 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The average number of active (not idle) threads in the service thread pool since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of threads in the service thread pool.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-65 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The number of currently idle threads in the service thread pool.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of threads that became idle in the service thread pool during the last collection interval.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of evictions from the backing map managed by this StorageManager caused by entries expiry or insert operations that would make the underlying backing map to reach its configured size limit.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of inserts into the backing map managed by this StorageManager. In addition to standard inserts caused by put and invoke operations or synthetic inserts caused by get operations with read-through backing map topology, this counter is incremented when distribution transfers move resources 'into' the underlying backing map and is decremented when distribution transfers move data 'out'.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of filter-based listeners currently registered with the StorageManager.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of filter-based listeners currently registered with the StorageManager.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The total number of listener registration requests processed by the StorageManager since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of locks currently granted for the portion of the partitioned cache managed by the StorageManager.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The service performance metrics aggregated over nodes are described.
The number of backups for every cache storage.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of partitions that this Member backs up (responsible for the backup storage).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of partitions that this Member owns (responsible for the primary storage).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of partitions that are not currently backed up.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of primary and backup partitions which remain to be transferred until the partition distribution across the storage enabled service members is fully balanced.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of partitions that are backed up on the same machine where the primary partition owner resides.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The average duration (in milliseconds) of an individual synchronous request issued by the service since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The maximum duration (in milliseconds) of a synchronous request issued by the service since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of pending synchronous requests issued by the service.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The duration (in milliseconds) of the oldest pending synchronous request issued by the service.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of timed-out requests since the last time the statistics were reset.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-66 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each "Name" object.
If warning or critical threshold values are currently set for any "Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of synchronous requests issued by the service during the last collection interval.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of synchronous requests issued by the service since the last time the statistics were reset.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-67 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each "Name" object.
If warning or critical threshold values are currently set for any "Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The total number of synchronous requests issued by the service during the last collection interval.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
Specifies the total number of cluster nodes running this service for which local storage is enabled.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The average duration (in milliseconds) of an individual task execution.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The size of the backlog queue that holds tasks scheduled to be executed by one of the service pool threads.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of executed tasks since the last time the statistics were reset
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of executed tasks during the last collection interval.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of currently executing hung tasks.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The longest currently executing hung task duration in milliseconds.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The maximum size of the backlog queue since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of timed-out tasks since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The total number of timed-out tasks during the last collection interval.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of abandoned threads from the service thread pool. A thread is abandoned and replaced with a new thread if it executes a task for a period of time longer than execution timeout and all attempts to interrupt it fail.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-68 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each "Name" objects.
If warning or critical threshold values are currently set for any "Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The number of abandoned threads from the service thread pool during the last collection interval. A thread is abandoned and replaced with a new thread if it executes a task for a period of time longer than execution timeout and all attempts to interrupt it fail.l
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The average number of active (not idle) threads in the service thread pool since the the statistics were last reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 300 Hours |
The number of threads in the service thread pool.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-69 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Hours |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each "Name" object.
If warning or critical threshold values are currently set for any "Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The store manager metrics are described.
The total number of events dispatched by the StorageManager since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of evictions from the backing map managed by this StorageManager caused by entries expiry or insert operations that would make the underlying backing map to reach its configured size limit. The eviction count is used to audit the cache size in a static system. Cache Size = Insert Count - Remove Count - Eviction count. Therefore the eviction count is not reset by the reset statistics method.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of inserts into the backing map managed by this StorageManager. In addition to standard inserts caused by put and invoke operations or synthetic inserts caused by get operations with read-through backing map topology, this counter is incremented when distribution transfers move resources `into` the underlying backing map and is decremented when distribution transfers move data `out`. The insert count is used to audit the cache size in a static system. Cache Size = Insert Count - Remove Count - Eviction count. Therefore the insert count is not reset by the reset statistics method.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of filter-based listeners currently registered with the StorageManager.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of key-based listeners currently registered with the StorageManager.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The total number of listener registration requests processed by the StorageManager since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of locks currently granted for the portion of the partitioned cache managed by the StorageManager.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of pending lock requests for the portion of the partitioned cache managed by the StorageManager.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of removes from the backing map managed by this StorageManager caused by operations such as clear, remove or invoke. The remove count is used to audit the cache size in a static system. Cache Size = Insert Count - Remove Count - Eviction count. Therefore the remove count is not reset by the reset statistics method.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The storage manager aggregate metrics are described.
The total number of events dispatched by the StorageManager since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of evictions from the backing map managed by this StorageManager caused by entries expiry or insert operations that would make the underlying backing map to reach its configured size limit.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of inserts into the backing map managed by this StorageManager. In addition to standard inserts caused by put and invoke operations or synthetic inserts caused by get operations with read-through backing map topology, this counter is incremented when distribution transfers move resources `into` the underlying backing map and is decremented when distribution transfers move data `out`.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of filter-based listeners currently registered with the StorageManager.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of key-based listeners currently registered with the StorageManager.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The total number of listener registration requests processed by the StorageManager since the last time the statistics were reset.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of locks currently granted for the portion of the partitioned cache managed by the StorageManager.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The number of pending lock requests for the portion of the partitioned cache managed by the StorageManager.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
The threading metrics are described.
Coherence Node ID.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every Hour |
Current live thread count for a Coherence node JVM.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-70 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
Peak thread could for a Coherence node JVM.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 2-71 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 300 Seconds |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Metric Value is %value% |
For this metric you can set different warning and critical threshold values for each unique combination of "Name" and "NodeID" objects.
If warning or critical threshold values are currently set for any unique combination of "Name" and "NodeID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Name" and "NodeID" objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.