This section describes the required configurations as well as the optional configurations available for the Solution Package for MySql Database in the RTView Configuration Application. You must define the classpath to the MySQL JDBC jar file and you must also define data source connections for each connection that you want to monitor. 

Configuring Data Connection

Use the RTView Configuration Application to configure your data collection.

...

• On the CONNECTIONS tab, provide the correct full path to the directory containing the MySQL JDBC jar files in the Classpath field.
• In the Connections region, click the  icon.

...

The newly created connection displays in the Connections section.

• You can optionally modify the Poll Rates (query interval, in seconds) that will be used to collect the metric data for the Poll Rate (MysqlServerPropertiesForDisplay cache) and the  Poll Rate Large (MysqlAborted, MysqlBytes, MysqlCRUD, MysqlUptime, MysqlThreads, MysqlQcache, MysqlQueries, MysqlSummaryTable, MysqlCreatedTemp, MysqlOpenedMetrics, MysqlTableLockMetrics, MysqlBinlogMetrics, MysqlConnection, MysqlSelectMetrics and MysqlTableStats caches) caches by clicking on the DATA COLLECTION tab and entering the desired polling rate for each cache.

Configuring Historical Data Collection (Optional)

This section describes the additional optional MySQL Database Monitor configurations. 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.

Defining the Storage of In-Memory History

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 MysqlAborted, MysqlBytes, MysqlCRUD, MysqlQueries, MysqlTableLockMetrics, MysqlBinlogMetrics and MysqlConnections caches. The default settings for History Rows is 50,000. To update the default setting:

• Navigate to the RTView Configuration Application > RTView DataServer for Infra > Solution Package Configuration > MySQL Database > DATA STORAGE tab.
• In the Size region, click the History Rows field and specify the desired number of rows.

Defining Compaction Rules

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:

...

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.

Defining Expiration and Deletion Duration for MySQL Database Metrics

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 following caches are impacted by settings in the Expire Time field: MysqlAborted, MysqlBytes, MysqlCRUD, MysqlQueries, MysqlTableLockMetrics, MysqlBinlogMetrics and MysqlConnection. To modify these defaults:

...

• Navigate to the RTView Configuration Application > RTView DataServer for Infra > Solution Package Configuration > MySQL Database > DATA STORAGE tab.
• In the History Storage region, deselect the toggles for the metrics that you do want to collect. Blue is enabled, gray is disabled.

Defining a Prefix for All History Table Names for MySQL Database Metrics

The History Table Name Prefix field allows you to define a prefix that will be added to the database table names so that RTView Enterprise 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:

...