This section describes how to collect data from the EMS Servers you want to monitor. This part of the EMS Monitor configuration is required. By default, the EMS Servers that are routed to by the EMS Servers defined in the RTView Configuration Application are auto-discovered and subsequently monitored. These instructions give you the option to turn off auto-discovery, which is on by default.
Note: See Creating Secure Connections for additional information on creating secure connections for TIBCO Enterprise Message Service.
The Add Connection dialog displays.
URL: Enter the complete URL for the EMS Server. A comma-separated list of URLs is used to designate fault tolerant server pairs.
Username: The username is used when creating the connection to the EMS Server. This field is optional.
Password: This password is used when creating the connection to the EMS Server. This field is optional. By default, the password entered is hidden. Click the icon to view the password text.
Note: By default, servers that are routed to by the servers defined in this file are automatically discovered (you have the option to turn off auto-discovery in subsequent steps).
Newly added queues and topics are listed beneath the text entry field. Click the x next to the queue/topic to remove the queue/topic.
Connection, Consumer, and Producer Caches
Update the polling rates for the Connection, Producer, and Consumer fields to modify the default polling values for the EmsProducers, EmsConsumers, and EmsConnections caches:
Queues and Topics Caches
Update the polling rate for the Queue and Topic fields to modify the default polling rates for the EmsQueues and EmsTopics caches:
Server-Related Caches
Update the polling rate for the Server field to modify the default polling rate for the EmsServerInfo, EmsAdmStats, EmsBridges, EmsDurables, EmsRoutes, EmsFTServerTable, EmsListenPorts, EmsServerRouteTable, EmsServerTable, EmsUsers, and EmsDestinations caches:
Note: When modifying your update rates, you should take your system architecture and number of elements per cache into account and ensure that you are not changing your update rates to values that might negatively impact system performance.
Each metric has a default regex pattern defined preventing metrics with the defined patterns from being collected. To edit the default:
a. Click on the desired field.
The Copy default text to clipboard link displays beneath the line.
b. Click the Copy default text to clipboard link to copy the text, click on the field, and paste (Ctrl-v) the text into the line.
c. Edit the regex pattern as desired.
You can specify the number of history rows to store in memory, the compaction rules, the duration before metrics are expired and deleted, and the different types of metrics that you want the Historian to store in the DATA STORAGE tab in the RTView Configuration Application. These configurations already contain default values and modifications to these configurations are optional.
You can modify the maximum number of history rows to store in memory in the DATA STORAGE tab. The History Rows property defines the maximum number of rows to store for the EmsAdmStats, EmsQueuesExt, EmsServerInfo, EmsTopicsExt, EmsProducers, EmsConsumers, EmsRoutes, and EmsDurables caches. The History Rows Large property defines the maximum number of rows to store for the EmsQueues, EmsQueueTotalsByServer, EmsTopics, and EmsTopicTotalsByServer caches. The default setting for History Rows is 50,000 and the default setting for History Rows Large is 200,000. To update the default settings:
Data compaction, essentially, is taking large quantities of data and condensing it using a defined rule so that you store a reasonably sized sample of data instead of all of your data, thus preventing you from potentially overloading your database. The available fields are:
Condense Interval -- The time interval at which the cache history is condensed for the following caches: EmsAdmStats, EmsCompdestTotals, EmsQueues, EmsQueueTotalsByServer, EmsQueuesExt, EmsServerInfo, EmsProducers, EmsConsumers, EmsRoutes, EmsDurables, EmsConnections, EmsRouteCountsByServer, EmsServerInfoExt, EmsTopics, EmsTopicTotalsByServer, and EmsTopicsExt. The default is 60 seconds.
Condense Raw Time -- The time span of raw data kept in the cache history table for the following caches: EmsAdmStats, EmsCompdestTotals, EmsQueues, EmsQueueTotalsByServer, EmsQueuesExt, EmsServerInfo, EmsProducers, EmsConsumers, EmsRoutes, EmsDurables, EmsConnections, EmsRouteCountsByServer, EmsServerInfoExt, EmsTopics, EmsTopicTotalsByServer, and EmsTopicsExt. The default is 1200 seconds.
Compaction Rules -- This field defines the rules used to condense your historical data in the database for the following caches: EmsAdmStats, EmsCompdestTotals, EmsQueues, EmsQueueTotalsByServer, EmsQueuesExt, EmsServerInfo, EmsProducers, EmsConsumers, EmsRoutes, EmsDurables, EmsFTServerTable, EmsServerRouteTable, EmsServerTable, EmsConnections, EmsTopics, EmsTopicTotalsByServer, EmsTopicsExt, EmsRouteCountsByServer, and EmsServerInfoExt. By default, the columns kept in history will be aggregated by averaging rows with the following rule 1h -;1d 5m;2w 15m, which means the data from 1 hour will not be aggregated (1h - rule), the data over a period of 1 day will be aggregated every 5 minutes (1d 5m rule), and the data over a period of 2 weeks old will be aggregated every 15 minutes (2w 15m rule).
Note: When you click in the Compaction Rules field, the Copy default text to clipboard link appears, which allows you copy the default text (that appears in the field) and paste it into the field. This allows you to easily edit the string rather than creating the string from scratch.
The data for each metric is stored in a specific cache and, when the data is not updated in a certain period of time, that data will either be marked as expired or, if it has been an extended period of time, it will be deleted from the cache altogether. By default, metric data will be set to expired when the data in the cache has not been updated within 45 seconds. Also, by default, if the data has not been updated in the cache within 3600 seconds, it will be removed from the cache. The Expire Time field applies to the following cache: EmsCompdestTotals. The Delete Timefield applies to the following caches: EmsJmsAdminMetrics, EmsQueues, EmsQueueTotalsByServer, EmsQueueInActivityTime, EmsQueuesExt, EmsQueueOutActivityTime, EmsBridges, EmsProducers, EmsConsumers, EmsDurables, EmsDestinations, EmsUsers, EmsConnections, EmsTopics, EmsTopicTotalsByServer, EmsTopicInActivityTime, EmsTopicsExt, and EmsTopicOutActivityTime. To modify these defaults:
The History Storage section allows you to select which metrics you want the Historian to store in the history database. By default, historical EMS Connections, Producers, and Consumers data is not saved to the database. All other metrics are saved by default. To enable the collection of historical data, perform the following steps:
The History Table Name Prefix field allows you to define a prefix that will be added to the database table names so that the Monitor can differentiate history data between data servers when you have multiple data servers with corresponding Historians using the same solution package(s) and database. In this case, each Historian needs to save to a different table, otherwise the corresponding data server will load metrics from both Historians on startup. Once you have defined the History Table Name Prefix, you will need to create the corresponding tables in your database as follows:
Note: If you are using Oracle for your Historian Database, you must limit the History Table Name Prefix to 2 characters because Oracle does not allow table names greater than 30 characters (and the longest table name for the solution package is 28 characters).
To add the prefix: