Monitoring IBM Db2

The IBM Db2 sensor is automatically deployed and installed after you install the Instana agent.

Supported information
- Supported versions
- Supported client-side tracing
Configuring IBM Db2 sensor
Viewing metrics

Supported information

Supported versions

Currently, the supported versions for metrics and configuration data are v10.5 and above.
Monitoring of the Db2 instances with DATA_ENCRYPT authentication security mechanism is not supported.

Supported client-side tracing

For this technology, Instana supports client-side tracing for the following languages and runtimes:

Configuring IBM Db2 sensor

Instana supports both local and remote monitoring for IBM Db2 sensor.

Notes:

The local monitoring sensor design is changed to support multiple instances and databases from v1.0.24 onwards. As a result, all the local monitoring configurations needs to be now added under the local tag. However, the design is compatible with the existing configuration that you might have been using now for single database instance monitoring, and the single database configuration remains to be supported.
Db2 on Docker container that uses local monitoring is currently not supported on Windows OS.

General setup

To use a custom port, database, user, password, instance, or polling rate, you need to configure the following fields in the agent configuration file <agent_install_dir>/etc/instana/configuration.yaml:

Local

com.instana.plugin.db2:
  local: # multiple local configurations supported
    - instance: 'db2inst1'
      port: '50000'
      user: 'db2inst1'
      password: 'password'
      poll_rate: 5 # seconds
      tabschema: 'schema1,schema2'
      databases:
        - 'database1'
        - 'database2'
        - 'database3'
        - 'database4'

Notes:

On Windows OS, the instance field must be the owner of the instance, so the configuration can support multiple instances and databases.
Db2 on Docker container that uses local monitoring is currently not supported on Windows OS.

Remote

com.instana.plugin.db2:
  remote:
    - host: 'host-1'
      port: '50000'
      tabschema: 'SYSTOOLS'
      user: 'db2inst1'
      password: 'db2inst1'
      sslTrustStorePassword: 'password'
      sslTrustStoreLocation: '/path/to/clientTrustStore.jks'
      availabilityZone: 'DB2 Remote Monitoring'
      poll_rate: 5 # seconds
      databases: # multiple databases
        - 'db'
        - 'sample'

The configured remote Db2 instance will then be shown as a separate box in the specified availabilityZone.

SSL/TLS support

For the Instana agent to securely connect to your Db2 server, it needs to be configured here <agent_install_dir>/etc/instana/configuration.yaml:

Local

com.instana.plugin.db2:
  ...
  sslTrustStoreLocation: '/path/to/truststore.jks'
  sslTrustStorePassword: 'trustStorePassword'

Remote

com.instana.plugin.db2:
  remote:
    ...
    sslTrustStoreLocation: '/path/to/truststore.jks'
    sslTrustStorePassword: 'trustStorePassword'

This will enable the Instana agent to connect to Db2 server via SSL. Once it is connected, credentials (user/password) will be used to access the auth-database.

Local monitoring for IBM Db2 in Red Hat OpenShift Container Platform

Instana supports local monitoring for IBM Db2 in Red Hat OpenShift Container Platform. The IBM Db2 database instances in the container environment are created as StatefulSets. They are rendered from the same pod template by using Custom Resources (CR). A sample configuration for IBM Db2 is shown in the following example:

com.instana.plugin.db2:
  local:
    - host: 'c-db2ucluster-sample-one-db2u.openshift-operators.svc'
      instance: 'db2inst1'
      port: '50000'
      environment: 'OCP'
      tabschema: 'SYSTOOLS'
      user: 'db2inst1'
      password: 'db2inst1'
      availabilityZone: 'DB2 Monitoring'
      poll_rate: 5 # seconds
      databases:
        - 'BLUDB'
    - host: 'c-db2ucluster-sample-two-db2u.openshift-operators.svc'
      instance: 'db2inst1'
      port: '50000'
      environment: 'OCP'
      tabschema: 'SYSTOOLS'
      user: 'db2inst1'
      password: 'db2inst1'
      availabilityZone: 'DB2 Monitoring'
      poll_rate: 5 # seconds
      databases: # multiple databases are supported
        - 'database1'
        - 'database2'

If multiple IBM Db2 instances exist in the same worker node, you can add them in the same configuration file.

The host URL of the IBM Db2 services is a combination of the service name and the namespace on the OpenShift Container Platform cluster in which the database instances are created. The URL is typically in the format " . .svc". For example, if "c-db2ucluster-sample-one" is the service name and "openshift-operators" is the namespace, the host URL is "c-db2ucluster-sample-one-db2u.openshift-operators.svc".

If you recreate a pod, use the same service name to preserve the database history in Instana.

Login timeout defines the maximum time in seconds that the sensor waits for connecting to the database. You can set a login timeout in the Instana Db2 sensor by using the loginTimeout property in the configuration.yaml file. If the connection is not obtained within the specified loginTimeout interval, then a connection error is displayed. The default value for this property is 5 seconds. The property is optional and is applicable for both the local and remote configurations. The following example shows how to customize theloginTimeout property:

      port: '50000'
      tabschema: 'SYSTOOLS'
      user: 'db2inst1'
      password: 'db2inst1'
      poll_rate: 5 # seconds
      loginTimeout: 20 #value in seconds

Custom interval for counting lock waits and long running queries

You can customize the time interval to get a count of the lock waits and long running queries in the Instana Db2 sensor by using the lockAndLongQueryInterval property in the configuration.yaml file. By default, the time taken by the sensor for classifying a query or lock wait as long running is 100 seconds. This metric can be used for alert or event configurations. The lockAndLongQueryInterval property is optional and is applicable for both the local and remote configurations. The following example shows how to customize this property:

      port: '50000'
      tabschema: 'SYSTOOLS'
      user: 'db2inst1'
      password: 'db2inst1'
      poll_rate: 5 # seconds
      lockAndLongQueryInterval: 60 # value in seconds

Custom interval for collecting runstats and reorg metrics

You can now customize the time interval for collecting runstats and reorg metrics. To customize your time interval, use the customRunStatsPollRate property in the configuration.yaml file. By default, the metrics are collected every 180 minutes. The customRunStatsPollRate property is optional and is applicable for both the local and remote configurations. The following example shows how to customize this property:

      port: '50000'
      tabschema: 'SYSTOOLS'
      user: 'db2inst1'
      password: 'db2inst1'
      poll_rate: 5 # seconds
      customRunStatsPollRate: 30 # value in minutes

Custom number of rows for table size metrics

You can now customize the number of rows that are displayed for table sizes per schema. To customize the number of rows, use the tableSizeRowsLimit property in the configuration.yaml file. By default, only the first 50 tables by size per schema are displayed. The tableSizeRowsLimit property is optional and is applicable for both the local and remote configurations. The following example shows how to customize this property:

      port: '50000'
      tabschema: 'SYSTOOLS'
      user: 'db2inst1'
      password: 'db2inst1'
      poll_rate: 5 # seconds
      tableSizeRowsLimit: 100 # number of rows to fetch

By configuring the tableSizeRowsLimit property, you can customize the number of rows displayed in the Table Sizes, Runtime Statistics, and REORG tables.

Token Authentication support

JSON Web Tokens (JWT) is a mechanism supported by Db2 for authentication, and is now supported by Db2 sensors from 1.0.27 version onwards. To make the Instana agent to support JWT connection to your Db2 server, you need to configure the <agent_install_dir>/etc/instana/configuration.yaml file as follows:

Local

Instana supports two types of monitoring for Db2 LUW Sensor - Local monitoring and Remote monitoring. For Local monitoring, see the following configuration:

com.instana.plugin.db2:
  local: # multiple local configurations supported
    - instance: 'db2inst1'
      port: '50000'
      user: 'db2inst1'
      password: 'accessTokenHere'
      accessTokenType: 'JWT'
      sslTrustStoreLocation: '/path/to/truststore.jks'
      sslTrustStorePassword: 'trustStorePassword'
      poll_rate: 5 # seconds
      tabschema: 'schema1,schema2'
      databases: # multiple databases
        - 'db'
        - 'sample'

Remote

Instana supports two types of monitoring for Db2 LUW Sensor - Local monitoring and Remote monitoring. For Remote monitoring, see the following configuration:

com.instana.plugin.db2:
  remote:
    - host: 'host-1'
      port: '50000'
      tabschema: 'SYSTOOLS'
      user: 'db2inst1'
      password: 'accessTokenHere'
      accessTokenType: 'JWT'
      sslTrustStoreLocation: '/path/to/truststore.jks'
      sslTrustStorePassword: 'trustStorePassword'
      availabilityZone: 'DB2 Remote Monitoring'
      poll_rate: 5 # seconds
      databases: # multiple databases
        - 'db'
        - 'sample'

Notes:

You must provide values for the following fields in the configuration.yaml file so that Instana agent can use these values to fetch the right configuration to create distinct Db2 sensor entities:
- For local monitoring: instance and user
- For remote monitoring: user
The access token for authentication is passed to the password entry, and it supports vault configuration just like how it supports with the plain text password.
If accessTokenType is enabled, Instana agent assumes the password entry is a token. Therefore, for all authentications other than token, make sure that you either remove or comment out the accessTokenType entry in the configuration.yaml file.

Monitor multiple instances

Monitoring multiple instances is supported for both local and remote monitoring. Here is an example of how you can configure it within configuration.yaml file:

Local

com.instana.plugin.db2:
  local: # multiple local configurations supported
    - instance: 'db2inst1'
      port: '50000'
      user: 'db2inst1'
      password: 'password'
      sslTrustStoreLocation: '/path/to/truststore.jks'
      sslTrustStorePassword: 'trustStorePassword'
      tabschema: 'schema1,schema2'
      poll_rate: 5 # seconds
      databases:
        - 'database1'
        - 'database2'
        - 'database3'
        - 'database4'
    - instance: 'db2inst2'
      port: '55000'
      user: 'db2inst2'
      password: 'password'
      sslTrustStoreLocation: '/path/to/truststore.jks'
      sslTrustStorePassword: 'trustStorePassword'
      poll_rate: 5 # seconds
      tabschema: 'schema1,schema2'
      databases:
        - 'database1'
        - 'database2'
        - 'database3'
        - 'database4'

Notes:

Db2 on Docker container that uses local monitoring is currently not supported on Windows OS.
On Windows OS, the instance field needs to be the owner of the instance, so the configuration can support multiple instances and databases.

Remote

com.instana.plugin.db2:
  remote:
    - host: 'host-1'
      port: '50000'
      tabschema: 'SYSTOOLS'
      user: 'db2inst1'
      password: 'db2inst1'
      sslTrustStorePassword: 'password'
      sslTrustStoreLocation: '/path/to/clientTrustStore.jks'
      availabilityZone: 'DB2 Remote Monitoring'
      poll_rate: 5 # seconds
      databases:
        - 'db'
      ...
    - host: 'host-n'
      port: '50000'
      tabschema: 'SYSTOOLS'
      user: 'db2inst1'
      password: 'db2inst1'
      sslTrustStorePassword: 'password'
      sslTrustStoreLocation: '/path/to/clientTrustStore.jks'
      availabilityZone: 'DB2 Remote Monitoring'
      poll_rate: 5 # seconds
      databases:
        - 'db'
        - 'sample'
      ...

Monitoring multiple instances with process environment variables is not supported.

IBM® Db2 pureScale

You can monitor Db2 pureScale instance both locally and remotely. The following examples show how to configure local and remote monitoring for a Db2 pureScale instance in the configuration.yaml file:

Local

For local monitoring, use the following configuration:

com.instana.plugin.db2:
  local: # multiple local configurations supported
    - instance: 'db2inst1'
      port: '50000'
      user: 'db2inst1'
      password: 'password'
      sslTrustStoreLocation: '/path/to/truststore.jks'
      sslTrustStorePassword: 'trustStorePassword'
      tabschema: 'schema1,schema2'
      poll_rate: 5 # seconds
      databases:
        - 'database1'

    - instance: 'db2inst2'
      port: '55000'
      user: 'db2inst2'
      password: 'password'
      sslTrustStoreLocation: '/path/to/truststore.jks'
      sslTrustStorePassword: 'trustStorePassword'
      poll_rate: 5 # seconds
      tabschema: 'schema1,schema2'
      databases:
        - 'database2'

Remote

For remote monitoring, use the following configuration:

com.instana.plugin.db2:
  remote:
    - host: 'host-1'
      port: '50000'
      tabschema: 'SYSTOOLS'
      user: 'db2inst1'
      password: 'db2inst1'
      sslTrustStorePassword: 'password'
      sslTrustStoreLocation: '/path/to/clientTrustStore.jks'
      availabilityZone: 'DB2 Remote Monitoring'
      poll_rate: 5 # seconds
      databases:
        - 'testdb'
      ...
    - host: 'host-n'
      port: '50000'
      tabschema: 'SYSTOOLS'
      user: 'db2inst1'
      password: 'db2inst1'
      sslTrustStorePassword: 'password'
      sslTrustStoreLocation: '/path/to/clientTrustStore.jks'
      availabilityZone: 'DB2 Remote Monitoring'
      poll_rate: 5 # seconds
      databases:
        - 'sample'
      ...

User permissions

You need to grant the following authorities to the Db2 user account that Instana uses:

DATAACCESS authority
DBADM authority
SQLADM authority

or EXECUTE privilege on the following table functions/views or procedures:

MON_GET_CONTAINER
MON_GET_TRANSACTION_LOG
MON_GET_DATABASE
MON_GET_TABLESPACE
MON_GET_PKG_CACHE_STMT
MON_GET_AGENT
MON_GET_HADR
MON_GET_CONNECTION
MON_GET_PKG_CACHE_STMT
MON_GET_UTILITY
MON_GET_WORKLOAD
MON_GET_UNIT_OF_WORK
MON_GET_INSTANCE
MON_TRANSACTION_LOG_UTILIZATION
PD_GET_DIAG_HIST
PD_GET_LOG_MSGS
SYSCAT.INDEXES
SYSCAT.TABLES
SYSIBMADM.MON_CURRENT_SQL
SYSIBMADM.DB_HISTORY
SYSIBMADM.DBCFG
SYSIBMADM.MON_CONNECTION_SUMMARY
SYSIBMADM.MON_DB_SUMMARY
SYSIBMADM.MON_LOCKWAITS
SYSIBMADM.SNAP_REORG
SYSPROC.DB_GET_CFG
SYSPROC.DBM_GET_CFG
SYSPROC.ENV_GET_INST_INFO

Example:

db2 connect to db

db2 "grant dataaccess, dbadm, sqladm on database to user db2inst1"

db2 "grant execute on FUNCTION SYSPROC.MON_GET_DATABASE to USER db2inst1"

Custom polling

Notes:

A polling configuration for IBM Db2 LUW sensor is enabled. With this feature, you can set a custom configuration for fetching stats at required intervals and also disable irrelevant stats.
If you are using the custom polling configuration, this setting takes priority over the default system settings.
The poll customization is enabled only for the stats that are outlined in the table in the Configurable stats section. The stats for which poll customization is not enabled are collected less frequently and are vital for the system. For more information about the collected stats and the default poll interval, see the Configurable stats section.
You cannot set the interval configuration less than the default value. If you make an incorrect configuration, this entry is moved to the next higher poll-rate configuration bucket that is available.
If you omit any stats from the configurable items (the stats is not added to any of the poll_intervals or disabled_metrics buckets), then it is automatically added to the next higher bucket available. However, if no such bucket exists, it is moved to the disabled metrics list.
Poll intervals can be customized for both local and remote monitoring. Set all poll intervals in seconds.
The stats names and bucket names (disabled_metrics, poll_rate_1, poll_rate_2, poll_rate_3, and poll_rate_4) are fixed. You need to name them as shown in the table in the Configuration stats section or as in the following sample configuration.

To customize polling for both local and remote monitoring, configure as follows:

      poll_rate: 5 # seconds
      custom_polling:
        disabled_metrics:
          metrics: DBM_CONFIG_STATS, AGENT_STATS #Stats that you don't want to be monitored
        poll_rate_1:
          poll_interval: 30
          metrics: TOP_QUERIES_STATS, TABLE_SPACE_STATS
        poll_rate_2:
          poll_interval: 200
          metrics: ELAPSED_TIME_STATS, WORKLOAD_STATS, TOP_TOTAL_STMT_IDS_STATS
        poll_rate_3:
          poll_interval: 900
          metrics: LOG_DISK_WAIT_STATS, DB_CONFIG_STATS, UNIT_OF_WORK_STATS
        poll_rate_4:
          poll_interval: 2000
          metrics: HADR_STATS, VMON_LOCK_STATS
      databases:
        - 'database1'

Viewing metrics

To view the metrics, select Infrastructure in the sidebar of the Instana User interface, click a specific monitored host, and then you can see a host dashboard with all the collected metrics and monitored processes.

The metrics and details that are collected and displayed on the dashboard are realtime such as lock waits, top queries, top total CPU. The metrics are visible on the dashboard only when the event is active.

Configuration data

Process ID
Port
Version
Start time / Up time

Configurable stats

Stats	Description	Default granularity
`TOP_QUERIES_STATS`	Stats from the `MON_CURRENT_SQL`, `MON_LOCKWAITS`, and `MON_GET_APPLICATION_HANDLE` tables.	20 seconds
`TABLE_SPACE_STATS`	Stats from the `MON_GET_TABLESPACE` table.	20 seconds
`ELAPSED_TIME_STATS`	Stats from the `MON_CURRENT_SQL` table.	60 seconds
`AGENT_STATS`	Stats from the `MON_GET_AGENT` table.	60 seconds
`WORKLOAD_STATS`	Stats from the `MON_GET_WORKLOAD` table.	60 seconds
`TOP_TOTAL_STMT_IDS_STATS`	Stats from the `SYSIBMADM.MON_LOCKWAITS` table.	60 seconds
`LOG_DISK_WAIT_STATS`	Stats from the `MON_GET_PKG_CACHE_STMT` table.	60 seconds
`DB_CONFIG_STATS`	Stats from the `SYSPROC.DB_GET_CFG` table.	5 minutes
`UNIT_OF_WORK_STATS`	Stats from the `MON_GET_PKG_CACHE_STMT` and `MON_GET_UNIT_OF_WORK` tables.	5 minutes
`HADR_STATS`	Stats collected from the `MON_GET_HADR` table.	10 minutes
`VMON_LOCK_STATS`	Stats from the `MON_GET_DATABASE`, `MON_LOCKWAITS`, and `SYSIBMADM.DBCFG` tables.	15 minutes
`DBM_CONFIG_STATS`	Stats from the `SYSPROC.DBM_GET_CFG` and `PD_GET_LOG_MSGS` tables.	30 minutes

Performance metrics

Database

Metric	Description	Granularity
Connections	The total number of connections on the server and is collected from the `MON_GET_DATABASE`.	5 seconds
Active Connections	The sum of local and remote connections in execution that are connected to a database in the database manager instance that is monitored. The connections are collected from the `SNAP_GET_DBM` table function.	5 seconds
Status	The current status of the database from table `MON_GET_DATABASE`.	5 seconds
Rows read	The number of rows read from the table and is collected from the `MON_GET_DATABASE`.	5 seconds
Rows returned	The number of rows that have been selected and returned to the application and is collected from the `MON_GET_DATABASE`.	5 seconds
Commits	Total number of commit statements issued by the client application and is collected from the `MON_GET_DATABASE`.	5 seconds
Rollbacks	Total number of rollback statements issued by the client application and is collected from the `MON_GET_DATABASE`.	5 seconds
SELECTS	The number of SQL SELECT statements that were executed and is collected from the `MON_GET_DATABASE`.	5 seconds
MERGES	The number of MERGE statements that were executed and is collected from the `MON_GET_DATABASE`.	5 seconds
DDLS	The number of SQL Data Definition Language (DDL) statements that were executed and is collected from the `MON_GET_DATABASE`.	5 seconds
UIDS	The number of UPDATE, INSERT, MERGE and DELETE statements that were executed and is collected from the `MON_GET_DATABASE`.	5 seconds
XQUERIES	The number of XQuery statements executed for an application or database and is collected from the `MON_GET_DATABASE`.	5 seconds
Queries - Static	The number of static SQL statements that were attempted and is collected from the `MON_GET_DATABASE`.	5 seconds
Queries - Dynamic	The number of dynamic SQL statements that were attempted and is collected from the `MON_GET_DATABASE`.	5 seconds
Queries - Failed	The number of SQL statements that were attempted, but failed and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool Data Pages - Physical Writes	The number of times a buffer pool data page was physically written to disk and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool Data Pages - Physical Reads	The number of data pages read in from the table space containers (physical) for regular and large table spaces and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool Data Pages - Logical Reads	The number of data pages which have been requested from the buffer pool (logical) for regular and large table spaces and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool Data Pages - Temp Physical Reads	The number of index pages read in from the table space containers (physical) for temporary table spaces and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool Data Pages - Temp Logical Reads	The number of data pages which have been requested from the buffer pool (logical) for temporary table spaces and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool Index Pages - Physical Writes	The number of times a buffer pool index page was physically written to disk and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool Index Pages - Physical Reads	The number of index pages read in from the table space containers (physical) for regular and large table spaces and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool Index Pages - Logical Reads	The number of index pages which have been requested from the buffer pool (logical) for regular and large table spaces and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool Index Pages - Temp Physical Reads	The number of index pages read in from the table space containers (physical) for temporary table spaces and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool Index Pages - Temp Logical Reads	The number of index pages which have been requested from the buffer pool (logical) for temporary table spaces and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool XDA - Physical Writes	The number of times a buffer pool data page for an XML storage object (XDA) was physically written to disk and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool XDA - Physical Reads	The number of data pages for XML storage objects (XDAs) read in from the table space containers (physical) for regular and large table spaces and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool XDA - Logical Reads	The number of data pages for XML storage objects (XDAs) which have been requested from the buffer pool (logical) for regular and large table spaces and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool XDA - Temp Physical Reads	The number of pages for XML storage object (XDA) data read in from the table space containers (physical) for temporary table spaces and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool XDA - Temp Logical Reads	The number of pages for XML storage object (XDA) data which have been requested from the buffer pool (logical) for temporary table spaces and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool Time - Read	The total amount of time spent reading in data and index pages from the table space containers (physical) for all types of table spaces and is collected from the `MON_GET_DATABASE`.	5 seconds
Buffer Pool Time - Write	Cumulative elapsed time for each asynchronous write to complete and is collected from the `MON_GET_DATABASE`.	5 seconds
Last Backup	The elapsed days since the last full database backup was completed and is collected from the `SYSIBMADM.DB_HISTORY` table.	30 minutes
Backup Type	The type of backup. This value is fetched from the `SYSIBMADM.DB_HISTORY` table.	30 minutes
Backup Start Time	The time at which the backup operation is initiated. This value is fetched from the `SYSIBMADM.DB_HISTORY` table.	30 minutes
Backup End Time	The time at which the backup operation is completed. This value is fetched from the `SYSIBMADM.DB_HISTORY` table.	30 minutes
Backup Duration	The time taken to complete the backup operation.	30 minutes
Log Space - Available	The amount of active log space in the database that is not being used by uncommitted transactions and is collected from the `MON_GET_TRANSACTION_LOG`.	5 seconds
Log Space - Used	The total amount of active log space currently used (in bytes) in the database and is collected from the `MON_GET_TRANSACTION_LOG`.	5 seconds
Log Space - Secondary Log Used	The maximum amount of secondary log space used (in bytes) in the database and is collected from `MON_GET_TRANSACTION_LOG`.	5 seconds
Log Space - Top Log Used	The maximum amount of total log space used (in bytes) in the database from `MON_GET_TRANSACTION_LOG`.	5 seconds
Log Space - Secondary Logs allocated	The total number of secondary log files that are currently being used for the database from `MON_GET_TRANSACTION_LOG`.	5 seconds
Log Space - Logs Used Percentage	The percentage of the total log space that is used by the database and is collected from `MON_TRANSACTION_LOG_UTILIZATION` table.	5 seconds
Log IO - Reads	The number of I/O requests issued by the logger for reading log data from the disk and is collected from the `MON_GET_TRANSACTION_LOG`.	5 seconds
Log IO - Writes	The number of I/O requests issued by the logger for writing log data to the disk and is collected from the `MON_GET_TRANSACTION_LOG`.	5 seconds
Log IO - Pages	The number of I/O requests issued by the logger for writing partial log data to the disk and is collected from `MON_GET_TRANSACTION_LOG`.	5 seconds
Log IO - Read Time	The total elapsed time spent by the logger reading log data from the disk and is collected from `MON_GET_TRANSACTION_LOG`.	5 seconds
Log IO - write Time	The total elapsed time spent by the logger writing log data to the disk and is collected from `MON_GET_TRANSACTION_LOG`.	5 seconds
Log - Reads	The number of log pages read from disk by the logger and is collected from the `MON_GET_TRANSACTION_LOG`.	5 seconds
Log - Writes	The number of log pages written to disk by the logger and is collected from the `MON_GET_TRANSACTION_LOG`.	5 seconds
Log Buffer - Buffer Full	The number of times full log buffer caused agents to wait monitor element and is collected from the `MON_GET_TRANSACTION_LOG`.	5 seconds
Log Buffer - Data in Buffer	The number of Log Data Found In Buffer monitor element and is collected from the `MON_GET_TRANSACTION_LOG`.	5 seconds
Log Active - Application ID holding oldest trasaction	Application handle holding the oldest transaction and is collected from `MON_GET_TRANSACTION_LOG`.	5 seconds
Log Active - First Active Log	The file number of the first active log file and is collected from `MON_GET_TRANSACTION_LOG`.	5 seconds
Log Active - Last Active Log	The file number of the last active log file and is collected from `MON_GET_TRANSACTION_LOG`.	5 seconds
Log Active - Current Active Log	The file number of the active log file the database system is currently writing and is collected from `MON_GET_TRANSACTION_LOG`.	5 seconds
Log Commits - Committed Disk Reads	The number of times the currently committed version of a row was retrieved via a log read from disk and is collected from `MON_GET_TRANSACTION_LOG`.	5 seconds
Log Commits - Committed Total Reads	The total number of times the currently committed version of a row was retrieved from the logs and is collected from `MON_GET_TRANSACTION_LOG`.	5 seconds
Log Commits - Committed Buffer Reads	The total buffer reads and is collected from `MON_GET_TRANSACTION_LOG`.	5 seconds
Agent Status - Total Agent Status	The total number of agents under various status and is collected from the `MON_GET_AGENT`.	60 seconds
Agent Status - UOW Waiting	The number of agents with Routine status and is collected from the `MON_GET_AGENT`.	60 seconds
Agent Status - UOW Executing	The number of agents with executing status and is collected from the `MON_GET_AGENT`.	60 seconds
Agent Status - Lock Wait	The number of agents with Lock status and is collected from the `MON_GET_AGENT`.	60 seconds
Agent Status - Lock Escalation	The number of agents with Lock Escalation status is collected from the `MON_GET_AGENT`.	60 seconds
Agent Status - Other States	The number of agents in Other status and is collected from the `MON_GET_AGENT`.	60 seconds
DBM Config Usage - Total Connections	Current number of connections to database and is collected from the `MON_GET_INSTANCE`.	30 minutes
DBM Config Usage - Agents Max Number	Maximum number of agents that are registered and is collected from the `MON_GET_INSTANCE`.	30 minutes
DBM Config Usage - Coordinating Agents Max Number	Maximum number of coordinating agents that are registered and is collected from the `MON_GET_INSTANCE`.	30 minutes
DBM Config Usage - Agents Created V/S Agents Reused	Agents that are created in the empty pool versus agents from the pool and is collected from the `MON_GET_INSTANCE`.	30 minutes
Workload(SYSDEFAULTUSERWORKLOAD) - Application Commits	The total number of application commits and is collected from the `MON_GET_WORKLOAD`.	60 seconds
Workload(SYSDEFAULTUSERWORKLOAD) - Application Rollbacks	The total number of application rollbacks and is collected from the `MON_GET_WORKLOAD`.	60 seconds
Workload(SYSDEFAULTUSERWORKLOAD) - Lock Timeouts	The number of Lock timeouts and is collected from the `MON_GET_WORKLOAD`.	60 seconds
Workload(SYSDEFAULTUSERWORKLOAD) - Deadlocks	The total number of deadlocks detected and is collected from the `MON_GET_WORKLOAD`.	60 seconds
Workload(SYSDEFAULTUSERWORKLOAD) - Network Time	The sum of TCP/IP send wait time, TCP/IP receive wait time, IPC send wait time, IPC receive wait time and is collected from the `MON_GET_WORKLOAD`.	60 seconds
Workload(SYSDEFAULTUSERWORKLOAD) - Request Time	Total request time and is collected from the `MON_GET_WORKLOAD`.	60 seconds
Workload(SYSDEFAULTUSERWORKLOAD) - Wait Time	Total wait time and is collected from the `MON_GET_WORKLOAD`.	60 seconds
Workload(SYSDEFAULTUSERWORKLOAD) - IO Time	Total IO time and is collected from the `MON_GET_WORKLOAD`.	60 seconds
Top Queries - Count	The total count of queries running more than 100 seconds and is collected from the `MON_GET_APPLICATION_HANDLE`.	20 seconds
Lock Wait Queries - Count	The total count of queries running more than 100 seconds and is collected from the `MON_LOCKWAITS`.	20 seconds
HADR Log Metrics - Requested Send Buffer	Requested socket send buffer size monitor element collected from `MON_GET_HADR`.	10 minutes
HADR Log Metrics - Actual Send Buffer	Actual socket send buffer size monitor element and is collected from `MON_GET_HADR`.	10 minutes
HADR Log Metrics - Requested Receive Buffer	Requested socket receive buffer size monitor element collected from `MON_GET_HADR`.	10 minutes
HADR Log Metrics - Actual Receive Buffer	Actual socket receive buffer size monitor element and is collected from `MON_GET_HADR`.	10 minutes
HADR Log metrics - Time Since Last Receive	Time since last message received monitor element and is collected from `MON_GET_HADR`.	10 minutes
HADR Log Metrics - Current Logger wait Time	Current logger wait time monitor element and is collected from `MON_GET_HADR`.	10 minutes
Lock Statistics - Lock Escalations	The number of times the locks have been escalated from several row locks to a table lock and is collected from `MON_GET_DATABASE`.	15 minutes
Lock Statistics - Lock List In Use	The total amount of lock list memory (in bytes) that is in use and is collected from `MON_GET_DATABASE`.	15 minutes
Lock Statistics - Active Lock Waits	The count of active lock waits and is collected from `MON_LOCKWAITS`.	15 minutes
Lock Statistics - Average Lock Escalations Per Activity	The average number of times that locks have been escalated from several row locks to a table lock and is collected from `MON_DB_SUMMARY`.	15 minutes
Lock Statistics - Lock List Value	The current value of the configuration parameter stored in memory and is collected from `SYSIBMADM.DBCFG`.	15 minutes
Transaction Performance(Incremental Value) - Index Read Efficiency	Index Read Efficiency essentially shows how well indexed a database is for the workload (IREF = Rows Read/ Rows Returned)	15 minutes
Transaction Performance(Incremental Value) - Sync Read Percentage	The synchronous read percentage indicates the proportion of read I/O that is completed with synchronous reads from `MON_GET_DATABASE`.	15 minutes
Transaction Performance(Incremental Value) - Async Write Percentage	The asynchronous write percentage is the percentage of all index and data writes that were performed asynchronously by the database manager from `MON_GET_DATABASE`.	15 minutes
Transaction Performance(Incremental Value) - Sorts Per Transactions	The Sorts per transaction is the number sorts that have been executed during each transaction from `MON_GET_DATABASE`.	15 minutes
Transaction Performance(Incremental Value) - SQLs	The total number of STATIC_SQL_STMTS + DYNAMIC_SQL_STMTS from `MON_GET_DATABASE`.	15 minutes
Member Nodes	The total number of member nodes in a Db2 pureScale environment from the `SYSIBMADM.DB2_MEMBER` table.	30 minutes

Recent Backup Details

Metric	Description	Granularity
Type	Type of backup from `SYSIBMADM.DB_HISTORY`.	30 minutes
Start time	Time at which backup started from `SYSIBMADM.DB_HISTORY`.	30 minutes
End time	Time at which backup ended from `SYSIBMADM.DB_HISTORY`.	30 minutes
Backup duration	Duration of backup from `SYSIBMADM.DB_HISTORY`.	30 minutes

Top Queries

Metric	Description	Granularity
Application Handle	Application handle from `MON_CURRENT_SQL`.	20 seconds
Application Name	Application name from `MON_CURRENT_SQL`.	20 seconds
Client Application Name	Client application name from `MON_CURRENT_SQL`.	20 seconds
Activity State	The current state of activity from `MON_CURRENT_SQL`.	20 seconds
Activity Type	The type of activity from `MON_CURRENT_SQL`.	20 seconds
Session Authorization ID	Session authorization ID from `MON_CURRENT_SQL`.	20 seconds
Elapsed Time	The time elapsed since the activity started. This metric is collected from `MON_CURRENT_SQL` in seconds.	20 seconds
Statement Text	The SQL statement text from the `MON_CURRENT_SQL`.	20 seconds

Lock Waits

Metric	Description	Granularity
Requesting Application Handle	Requesting application handle from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Holding Application Handle	Holding application handle from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Elapsed Time	Lock wait time elapsed from `SYSIBMADM.MON_LOCKWAITS` in seconds.	60 seconds
Lock Mode	The mode of the lock can be: table, rows, or if the application that holds this lock cannot be found, a value of NULL is returned. The Lock mode is collected from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Lock Mode Requested	The mode in which the lock is requested by the application that is waiting to acquire the lock. The metric is collected from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Requesting Statement Text	Requesting application SQL statement text. This metric is collected from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Holding Client Accounting	Holding client accounting from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Requesting Client Accounting	Requesting client accounting from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Lock Name	Lock Name from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Table Name	Table Name from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Current Lock Mode	Current Lock Mode from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Request Application Name	Request Application Name from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Request User ID	Request User ID from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Holding Member	Holding Member from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Holding Application Name	Holding Application Name from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Holding User ID	Holding User ID from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Client User ID	Client User ID from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds
Client Process ID	Client Process ID from `SYSIBMADM.MON_LOCKWAITS`.	60 seconds

DB Configurations

Metric	Description	Granularity
Configuration Parameter Name	Configuration parameter name from `SYSPROC.DB_GET_CFG`.	5 minutes
Value Flags	Provides specific information for the configuration parameter current value from `SYSPROC.DB_GET_CFG`.	5 minutes
Deferred Value Flags	Provides specific information for the configuration parameter deferred value from `SYSPROC.DB_GET_CFG`.	5 minutes
Value	The current value of the configuration parameter stored in memory from `SYSPROC.DB_GET_CFG`.	5 minutes
Deferred Value	The value of the configuration parameter on disk from `SYSPROC.DB_GET_CFG`.	5 minutes

DBM Configurations

Metric	Description	Granularity
Configuration Parameter Name	Configuration parameter name from `SYSPROC.DBM_GET_CFG`.	30 minutes
Value Flags	Provides specific information for the configuration parameter current value from `SYSPROC.DBM_GET_CFG`.	30 minutes
Deferred Value Flags	Provides specific information for the configuration parameter deferred value from `SYSPROC.DBM_GET_CFG`.	30 minutes
Value	The current value of the configuration parameter stored in memory from `SYSPROC.DBM_GET_CFG`.	30 minutes
Deferred Value	The value of the configuration parameter on disk from `SYSPROC.DBM_GET_CFG`.	30 minutes

Diag Log Entry

Metric	Description	Granularity
Event Timestamp	The time when the entry was logged from `PD_GET_LOG_MSGS`.	30 minutes
Application ID	Application ID monitor element from `PD_GET_LOG_MSGS`.	30 minutes
Message Severity	Message severity: C (critical), E (error), W (warning), I (informational) or NULL (if the message severity could not be determined) from `PD_GET_LOG_MSGS`.	30 minutes
Message Number	The numeric message number for the error or event from `PD_GET_LOG_MSGS`.	30 minutes
Message	The summary of the log message from `PD_GET_LOG_MSGS`.	30 minutes

Top Total CPU

Metric	Description	Granularity
Executable ID	specifies a unique section of the database package cache from `MON_GET_PKG_CACHE_STMT`.	60 seconds
% of Total Rows Read	Percentage of Total Rows Read from `MON_GET_PKG_CACHE_STMT`.	60 seconds
% of Total CPU Time	Percentage of Total CPU time from `MON_GET_PKG_CACHE_STMT`.	60 seconds
Total CPU Time	Total CPU time from `MON_GET_PKG_CACHE_STMT`.	60 seconds
Statement Execution Time	Time taken for Execution from `MON_GET_PKG_CACHE_STMT`.	60 seconds
% of Statement Execution Time	Percentage of Statement Execution Time from `MON_GET_PKG_CACHE_STMT`.	60 seconds

Log Disk Wait

Metric	Description	Granularity
Executable ID	specifies a unique section of the database package cache from `MON_GET_PKG_CACHE_STMT`.	60 seconds
Total activity time	Total activity time from `MON_GET_PKG_CACHE_STMT`.	60 seconds
% of Total activity time	Percentage of total activity time from `MON_GET_PKG_CACHE_STMT`.	60 seconds
Total activity wait time	Total activity wait time from `MON_GET_PKG_CACHE_STMT`.	60 seconds
% of Total Activity wait time	Percentage of total activity wait time from `MON_GET_PKG_CACHE_STMT`.	60 seconds
Log disk wait time	Log disk wait time from `MON_GET_PKG_CACHE_STMT`.	60 seconds
% of Log disk wait time	Percentage of log disk wait time from `MON_GET_PKG_CACHE_STMT`.	60 seconds
Log disk waits total	Log disk waits total from `MON_GET_PKG_CACHE_STMT`.	60 seconds

Runtime Statistics

Metric	Description	Granularity
Object Name	The name of the object to which the event applies from `PD_GET_DIAG_HIST`.	3 hours
Object Name Qualifier	For statistics logging, this is the schema of the table or index from `PD_GET_DIAG_HIST`.	3 hours
Start Time	Start time from `PD_GET_DIAG_HIST`.	3 hours
End Time	End time from `PD_GET_DIAG_HIST`.	3 hours
Duration	Difference between the Start Time and End Time from `PD_GET_DIAG_HIST` in seconds.	3 hours

DB utilities

Metric	Description	Granularity
Application Name	Application name monitor element from `MON_GET_UTILITY`.	30 minutes
Application Handle	Application handle monitor element from `MON_GET_UTILITY`.	30 minutes
Utility Operation Type	Utility operation type monitor element from `MON_GET_UTILITY`.	30 minutes
Object Type	Type of object from `MON_GET_UTILITY`.	30 minutes
Utility Start Time	Utility start time from `MON_GET_UTILITY`.	30 minutes
Utility Type	Utility type from `MON_GET_UTILITY`.	30 minutes
Utility Detail	Utility detail monitor element from `MON_GET_UTILITY`.	30 minutes
Session Auth ID	The current authorization ID for the session that is used by the application from `MON_GET_UTILITY`.	30 minutes
Client Workstation Name	Client workstation name monitor element from `MON_GET_UTILITY`.	30 minutes
Client Accounting	Client accounting string monitor element from `MON_GET_UTILITY`.	30 minutes
Client User ID	Client user ID monitor element from `MON_GET_UTILITY`.	30 minutes
Object Schema	Object schema monitor element from `MON_GET_UTILITY`.	30 minutes
Client Application Name	Client application name monitor element from `MON_GET_UTILITY`.	30 minutes

Unit Of Work(UOW)

Metric	Description	Granularity
Application Name	Application name monitor element from `MON_GET_CONNECTION`.	5 minutes
Application Handle	Application handle monitor element from `MON_GET_CONNECTION`.	5 minutes
Application ID	Application ID monitor element from `MON_GET_CONNECTION`.	5 minutes
Number of Locks Held	The number of locks held monitor element from `MON_GET_UNIT_OF_WORK`.	5 minutes
Log Space Used UOW	Unit of work log space used monitor element from `MON_GET_UNIT_OF_WORK`.	5 minutes
Client Idle Time Min	Client idle wait time monitor element in minutes from `MON_GET_UNIT_OF_WORK`.	5 minutes
Client App Name	Client application name from `MON_GET_UNIT_OF_WORK`.

REORG

Metric	Description	Granularity
Table Name	Table name monitor element from `SNAP_GET_TAB_REORG`.	3 hours
Table Schema	Table schema name monitor element from `SNAP_GET_TAB_REORG`.	3 hours
Reorg Status	Table reorganize Status monitor element from `SNAP_GET_TAB_REORG`.	3 hours
Reorg Completion	Reorganization completion flag monitor element from `SNAP_GET_TAB_REORG`.	3 hours
Reorg Start	Table Reorganize start time monitor element from `SNAP_GET_TAB_REORG`.	3 hours
Reorg End	Table Reorganize end time monitor element from `SNAP_GET_TAB_REORG`.	3 hours

Table Space Utilities

Up to 200 rows per schema are displayed in the dashboard. The rows are sorted in descending order based on the table size.

Metric	Description	Granularity
Table Name	Table space name monitor element from `MON_GET_TABLESPACE`.	20 seconds
Total Size	Total size of table space from `MON_GET_TABLESPACE`.	20 seconds
Used Space	Total used size of table space from `MON_GET_TABLESPACE`.	20 seconds
Free Space	Total available size of table space from `MON_GET_TABLESPACE`.	20 seconds
Space Util percentage	Usage of the table space as percentage from `MON_GET_TABLESPACE`.	20 seconds
Table Space State	Table Space State (0 indicating NORMAL and 1 indicating ABNORMAL state) from `MON_GET_TABLESPACE`.	20 seconds

HADR General

Metric	Description	Granularity
Role	HADR Role monitor element from `MON_GET_HADR`.	10 minutes
Replay Type	HADR Replication type monitor element from `MON_GET_HADR`.	10 minutes
Sync Mode	HADR Synchronization Mode monitor element from `MON_GET_HADR`.	10 minutes
Standby ID	Standby ID monitor element from `MON_GET_HADR`.	10 minutes
State	HADR State monitor element from `MON_GET_HADR`.	10 minutes
Connect Time	HADR Connect Status Time monitor element from `MON_GET_HADR`.	10 minutes
HADR Timeout	HADR Timeout monitor element from `MON_GET_HADR`.	10 minutes
HADR Log Gap	HADR Log Gap monitor element from `MON_GET_HADR`.	10 minutes
Connect State	HADR Connection Status monitor element from `MON_GET_HADR`.	10 minutes

HADR Connection Status

Metric	Description	Granularity
Primary Host	Primary Member Host monitor element from `MON_GET_HADR`.	10 minutes
Primary Instance	Primary Instance monitor element from `MON_GET_HADR`.	10 minutes
Primary Member	Primary Member monitor element from `MON_GET_HADR`.	10 minutes
Standby Host	Standby member hostname monitor element from `MON_GET_HADR`.	10 minutes
Standby Instance	Standby Instance monitor element from `MON_GET_HADR`.	10 minutes
Standby Member	Standby member monitor element from `MON_GET_HADR`.	10 minutes
HeartBeat Interval	Heartbeat interval monitor element from `MON_GET_HADR`.	10 minutes
Peer Wait Limit	Peer wait limit monitor element from `MON_GET_HADR`.	10 minutes

HADR Primary Log Information

Metric	Description	Granularity
Primary Log	Primary log file monitor element from `MON_GET_HADR`.	10 minutes
Primary Log Page	Primary log page monitor element `MON_GET_HADR`.	10 minutes
Primary Log Position	Primary log position monitor element from `MON_GET_HADR`.	10 minutes
Primary Log Time	Primary log time monitor element from `MON_GET_HADR`.	10 minutes
Log Stream ID	Log stream ID monitor element from `MON_GET_HADR`.	10 minutes
HADR Waits Total	Total logger wait time monitor element from `MON_GET_HADR`.	10 minutes

HADR Secondary Log Information

Metric	Description	Granularity
Secondary Log	Secondary log file monitor element from `MON_GET_HADR`.	10 minutes
Secondary Log Page	Secondary log page monitor element `MON_GET_HADR`.	10 minutes
Secondary Log Position	Secondary log position monitor element from `MON_GET_HADR`.	10 minutes
Secondary Log Time	Secondary log time monitor element from `MON_GET_HADR`.	10 minutes

Index Catalog View

Up to 50 rows per schema are displayed in the dashboard.

Metric	Description	Granularity
Table Name	Name of the table on which the index is defined from `SYSCAT.INDEXES`.	24 hours
Index Schema	Schema name of the table on which the index is defined from `SYSCAT.INDEXES`.	24 hours
Index Name	Name of the Index from `SYSCAT.INDEXES`.	24 hours
Status Time	Last time that any change is made to the recorded statistics for this index `SYSCAT.INDEXES`.	24 hours
Last Used	Date when the index is last used from `SYSCAT.INDEXES`.	24 hours
Owner	Authorization ID of the owner of the table from `SYSCAT.TABLES`.	24 hours
Table Space	Name of the primary table space for the table from `SYSCAT.TABLES`.	24 hours
Type	Type of object from `SYSCAT.TABLES`.	24 hours

Table Sizes

Up to 50 rows per schema are displayed in the dashboard. The rows are sorted in descending order based on the table size.

Metric	Description	Granularity
Table Name	Table name monitor element from `ADMIN_GET_TAB_INFO`.	24 hours
Card	Total number of rows in the table `SYSCAT.TABLES`.	24 hours
Table Size KB	Table Size in KB from `ADMIN_GET_TAB_INFO`.	24 hours
Table Size MB	Table Size in MB from `ADMIN_GET_TAB_INFO`.	24 hours
Average Row Size	Average length of rows from `SYSCAT.TABLES`.	24 hours

Tables Catalog View

Up to 50 rows per schema are displayed in the dashboard based on the time at which the event occured.

Metric	Description	Granularity
Table Name	Table name from `SYSCAT.TABLES`.	24 hours
Stats Time	Time at which any change was last made to recorded statistics for this object from `SYSCAT.TABLES`.	24 hours
Volatile	To check cardinality of the table from `SYSCAT.TABLES`.	24 hours
Compression	To check value and row compression `SYSCAT.TABLES`.	24 hours
Card	Total number of rows in the table from `SYSCAT.TABLES`.	24 hours

Db2 pureScale performance metrics

pureScale General

Metric	Description	Granularity
Host Name	Host name from `SYSIBMADM.DB2_CLUSTER_HOST_STATE`.	30 minutes
State	State of the instance from `SYSIBMADM.DB2_CLUSTER_HOST_STATE`.	30 minutes
Instance Stopped	Status (stopped or not) of the instance on the hosts from `SYSIBMADM.DB2_CLUSTER_HOST_STATE`.	30 minutes
Alert	Information about alerts on the hosts from `SYSIBMADM.DB2_CLUSTER_HOST_STATE`.	30 minutes

Member Details

Metric	Description	Granularity
ID	Member node identifier from `SYSIBMADM.DB2_MEMBER`.	30 minutes
HOME_HOST	Machine that is associated with the member when it is first added to the instance from `SYSIBMADM.DB2_MEMBER`.	30 minutes
CURRENT_HOST	Machine name on which the member is currently running from `SYSIBMADM.DB2_MEMBER`.	30 minutes
STATE	State of the member node from `SYSIBMADM.DB2_MEMBER`.	30 minutes
Alert	Information about alerts on the hosts from `SYSIBMADM.DB2_MEMBER`.	30 minutes

CF Details

Metric	Description	Granularity
ID	Cluster caching facility (CF) identifier from `DB2_GET_INSTANCE_INFO`.	30 minutes
HOME_HOST	Machine that is associated with the CF when it is first added to the instance from `DB2_GET_INSTANCE_INFO`.	30 minutes
CURRENT_HOST	Machine name on which the CF is currently running from `DB2_GET_INSTANCE_INFO`.	30 minutes
STATE	State of the cluster caching facility node from `DB2_GET_INSTANCE_INFO`.	30 minutes
Alert	Information about alerts on the hosts from `DB2_GET_INSTANCE_INFO`.	30 minutes

pureScale Lock Memory Table

Metric	Description	Granularity
Host ID	Host identifier from `MON_GET_CF`.	30 minutes
Host Name	Host name from `MON_GET_CF`.	30 minutes
Current CF Lock Size	Amount of lock memory currently used by the system from `MON_GET_CF`.	30 minutes
Configured CF Lock Size	Amount of lock memory that is currently configured by the database as the maximum from `MON_GET_CF`.	30 minutes
Targeted CF Lock Size	A new configured maximum value for lock memory from `MON_GET_CF`.	30 minutes

pureScale SCA Memory Table

Metric	Description	Granularity
Host ID	Member node identifier from `MON_GET_CF`.	30 minutes
Host Name	Host name from `MON_GET_CF`.	30 minutes
Current CF SCA Size	Amount of SCA memory currently used by the system from `MON_GET_CF`.	30 minutes
Configured CF SCA Size	Amount of SCA memory that is currently configured by the database as the maximum from `MON_GET_CF`.	30 minutes
Targeted CF SCA Size	A new configured maximum value for SCA memory from `MON_GET_CF`.	30 minutes

pureScale Page Access Table

Metric	Description	Granularity
Member ID	Member node identifier from `MON_GET_PAGE_ACCESS_INFO`	30 minutes
Schema	Schema name from `MON_GET_PAGE_ACCESS_INFO`	30 minutes
Table Name	Table name from `MON_GET_PAGE_ACCESS_INFO`	30 minutes
Reclaim Wait Time	Reclaim Wait Time from `MON_GET_PAGE_ACCESS_INFO`	30 minutes
Type	Type of table from `MON_GET_PAGE_ACCESS_INFO`	30 minutes

pureScale Package Cache Table

Metric	Description	Granularity
Host ID	Host node identifier from `MON_GET_PKG_CACHE_STMT`	30 minutes
Number of Excecutions	Number of excecutions `MON_GET_PKG_CACHE_STMT`	30 minutes
Reclaim Wait Time	Reclaim wait time from `MON_GET_PKG_CACHE_STMT`	30 minutes
Average Excecution Time	Average excecution time from `MON_GET_PKG_CACHE_STMT`	30 minutes

pureScale Group Buffer Pool Table

Metric	Description	Granularity
Host ID	Member node identifier from `MON_GET_CF`	30 minutes
Host Name	Host name from `MON_GET_CF`	30 minutes
Current CF GBP Size	Amount of GBP memory currently used by the system from `MON_GET_CF`	30 minutes
Configured CF GBP Size	Amount of GBP memory that is currently configured by the database as the maximum from `MON_GET_CF`	30 minutes
Targeted CF GBP Size	Newly configured maximum value for GBP memory from `MON_GET_CF`	30 minutes