Setting Up Monitoring Server Groups and Monitors for Databases

The Central > Monitoring Server Groups and/or Monitor wizards support four database types, as well as eight new monitoring resource types (discussed below).

How to

  1. To monitor a database, go to CloudTest and click Monitoring Server Groups under Monitoring to create a group for the database instance.
  2. Then, click Monitors to create a monitor for the monitoring server group.
  3. During either Monitor Server Group or Monitor configuration, select the database type to monitor in the Database Type and Authentication page.In the screenshot above, database type selection occurs as part of the overall definition of a new Monitor Server or Monitor using the Database(s) page. Existing Monitor Server Groups or Monitors can also be revised to include this database monitoring.
  4. Provide the necessary database connectivity credentials, minimally to include user name, password, and password confirmation.
  5. Click Test Connection to verify successful connectivity.
  6. Next, define the Database Resource Selection for the given database type by checking the relevant resources to monitor.
  7. Click Finish after performing the above steps.
  8. Ensure that you Enable Server Monitoring and check the box for the monitor(s) you wish to use in a test composition. You can also use the Central > Monitors, View Analytics link for any given, listed monitor (refer to Starting and Stopping a Monitor).

What you should see

The database resource types for monitors are shown in alphabetical order alongside the previously existing four resources types in the resource selection page (above). The new resource types are:

  • Buffer Cache Size – The size of the database buffer cache, in bytes
  • Commits – The number of transactions committed.
  • Deletes – The number of DELETE statements issued to the database (MySQL, Oracle, SQL Server), or the number of rows deleted from the current catalog (PostgreSQL).
  • Disk Sorts – The number of sorts that required creating a temporary table on the disk. This metric is not supported when monitoring PostgreSQL.
  • Full Table Scans – The number of full table scans across all queries.
  • Index Scans – The number of index scans across all queries.
  • Inserts – The number of INSERT statements issued to the database (MySQL, Oracle, SQL Server), or the number of rows inserted into the current catalog (PostgreSQL).
  • Per Catalog Connections – The number of active connections to the specified catalog.
  • Rollbacks – The number of transactions rolled back.
  • Selects – The number of SELECT statements issued to the database (MySQL, Oracle, SQL Server), or to the current catalog (PostgreSQL).
  • Total Connections – The total number of active connections, across all catalogs.
  • Updates – The number of UPDATE statements issued to the database (MySQL, Oracle, SQL Server), or the number of rows updated in the current catalog (PostgreSQL).