RTView© Enterprise User's Guide Version 6.2

Choose a cluster for which you want to see metrics.

The total number of clusters in the table.

The name of the node.

The total number of critical and warning alerts.

When checked (true), this feature is enabled.

When checked (true), this feature is enabled.*

When checked (true), this feature is enabled.*

The approximate TIBCO BusinessEvents version, as configured by the connection property. The exact version information is not available via JMX.

A unique string that identifies the node.

The maximum amount of memory, in megabytes, that can be used by the JVM for heap space. This value is provided by standard Java MBeans.

The maximum amount of memory, in megabytes, that can be used by the process (not counting heap usage). This value is provided by standard Java MBeans.

When checked (true), the node is currently connected to the Data Server via JMX.

Choose a cluster for which you want to see metrics.

Select this check box to display the name of the node in each rectangle in the heatmap.

When checked, the values of the selected metric are auto-scaled to its highest defined value. When unchecked, the values of the selected metric display based on the threshold defined for the alert associated with the selected metric. Selecting Auto helps to visualize the range of the values currently present for the selected metric instead of the threshold of the alert that has been associated with the metric. All metrics that have not been associated in the heatmap defaults with alerts use a monochromatic color gradient bar (whites and greens). All metrics that have been associated in the heatmap defaults with alerts use a multi-chromatic color gradient bar (reds, yellows, white, and greens).

The maximum alert level in the item (index) associated with the rectangle. Values range from 0 to 2, as indicated in the color gradient bar , where 2 is the greatest Alert Severity.

2 -- Metrics that have exceeded their specified ALARMLEVEL threshold and have an Alert Severity value of 2 are shown in red. For a given rectangle, this indicates that one or more metrics have exceeded their alarm threshold.

1 -- Metrics that have exceeded their specified WARNINGLEVEL threshold and have an Alert Severity value of 1 are shown in yellow. For a given rectangle, this indicates that one or more metrics have exceeded their warning threshold.

0 -- Metrics that have not exceeded either specified threshold have an Alert Severity value of 0 and are shown in green. For a given rectangle, this indicates that no metrics have exceeded a specified alert threshold.

The total percentage of JVM CPU used in a given item (index) associated with the rectangle. The color gradient bar shows the range of the value/color mapping. By default, the numerical values in the gradient bar range from 0 to the alert threshold of JvmCpuPercentHigh. The middle value in the gradient bar indicates the middle value of the range.

Select a node for which you want to view metrics.

Fields and Data:

Note: Fields in this display with an asterisk (*) at the end of the field definition contain data that is provided by the TIBCO MBean interface. Refer to TIBCO documentation for more information regarding these fields.

The maximum rules fired per second for all inference agents from the selected node.

The maximum hit ratio across all inference agents from the selected node.

The percentage of CPU utilization on this inference node.

The agent’s ID.

The type of agent (Inference, Cache, Query, or Dashboard).*

When checked, denotes that the agent is started.*

When checked, denotes that it is a concurrent agent.*

The queue size for the agent.*

The total number of rules fired for the agent.*

The rate of rules fired for the agent.

The average amount of time taken to commit a transaction.*

The total amount of remaining space on the DB Operations queue.*

See TIBCO documentation for more information.*

The current size of the L1 cache.*

The total number of currently active event threads.*

See TIBCO documentation for more information.*

The number of transactions committed by the agent.*

When checked, performance data has not been received within the time specified (in seconds) in the Expire Time field in the Duration region in the RTView Configuration Application > (Project Name) > Solution Package Configuration > TIBCO BusinessEvents > DATA STORAGE tab. The Delete Time field (also in the Duration region) allows you to define the amount of time (in seconds) in which the row will be removed from the table if there is no response.

Utilization

Shows metrics for the selected node.

% CPU -- Traces the amount of CPU used, in percent, by the node.

Max Heap -- Traces the maximum amount of heap space, in bytes, used by the node since the agent was started.

Used Heap -- Traces the current amount of heap space, in bytes, used by the agent.

Rules/s and Threads

Shows metrics for the selected node.

Rules/s -- Traces the number of rules processed, per second, by the agent.

Thread Count-- Traces the number of threads being used by the node.

Select a time range from the drop down menu varying from 5 Minutes to Last 7 Days. By default, the time range end point is the current time.

To change the time range, deselect the now toggle, which displays some additional date fields. You can click the left and right arrow buttons to decrease the end time by one time period (the time selected in the Time range drop down) per click, or you can choose the date and time from the associated calendar and clock icons. You can also enter the date and time in the text field using the following format: MMM dd, YYYY HH:MM:ss. For example, Aug 21, 2018 12:24 PM. Click the now toggle to reset the time range end point to the current time.

The maximum number of jobs.*

The number of critical and warning alerts.

The maximum average receive time for all inference agents from the selected node.

The maximum number of threads on the selected node.

Select the node for which you want to see metrics.

The amount of CPU, in percent, used by the node. This value is provided by standard Java MBeans.

The maximum average store time, in milliseconds, across all backing stores of this storage node.

The maximum number of loads per second across all backing stores of this storage node.

Backing StoreTable

A cache node manages access to current events and concepts, buffering as necessary between local memory and a database. The Backing Store table provides a list of caches and the database select/insert/delete statistics for each cache.

Note: Row columns in this table with an asterisk (*) at the end of the column definition contain data that is provided by the TIBCO MBean interface. Refer to TIBCO documentation for more information regarding these columns.

When checked, denotes that the cache is active.*

The average amount of time taken for a “load” operation in the Backing Store for the cache.*

The total number of “delete” operations in the Backing Store for the cache.*

The total number of “store” operations in the Backing Store for the cache.*

The number of “load” operations during the last polling interval.*

The rate of “delete” operations in the node.

The rate of “store” operations in the node.

Utilization

Shows metrics for the selected cluster/node combination:

% CPU -- Traces the amount of CPU used, in percent, by the engine.

Max Heap (MB)-- Traces the maximum amount of memory, in megabytes, that can be used by the JVM for heap space.

Used Heap (MB) -- Traces the used heap space, in megabytes, in use by the JVM.

Table Sizes

Shows metrics for the selected cluster/node combination:

Table Size -- Traces the number of unique objects cached in the local index table.

Ext ID Tbl Size -- Traces the number of entries in the table of external IDs used as indexes by the backing store.

Select a time range from the drop down menu varying from 5 Minutes to Last 7 Days. By default, the time range end point is the current time.

To change the time range, deselect the now toggle, which displays some additional date fields. You can click the left and right arrow buttons to decrease the end time by one time period (the time selected in the Time range drop down) per click, or you can choose the date and time from the associated calendar and clock icons. You can also enter the date and time in the text field using the following format: MMM dd, YYYY HH:MM:ss. For example, Aug 21, 2018 12:24 PM. Click the now toggle to reset the time range end point to the current time.

When true, performance data has not been received within the time specified (in seconds) in the Expire Time field in the Duration region in the RTView Configuration Application > (Project Name) > Solution Package Configuration > TIBCO BusinessEvents > DATA STORAGE tab. The Delete Time field (also in the Duration region) allows you to define the amount of time (in seconds) in which the row will be removed from the table if there is no response.

The number of critical and warning alerts.

The approximate TIBCO BusinessEvents version, as configured by the connection property. The exact version information is not available via JMX.