Monitoring for IBM Db2 SaaS

Get insight into your IBM Db2 SaaS instance. These metrics can help you find bottlenecks or predict possible production problems.

You can use the IBM Cloud® Monitoring service to monitor your IBM Db2 SaaS instance. IBM Db2 SaaS forwards selected information about your instance to Monitoring so that you can monitor specific metrics such as cpu and memory utilization.

For additional details on platform metrics, please see Platform Metrics Introduction.

Monitoring metrics are currently available for only Enterprise and Standard plans. Lite plans are currently not supported.

Set up your IBM Db2 SaaS service instance

To set up Monitoring for IBM Db2 SaaS, you must create a service instance and then enable Platform Metrics in the same region as the IBM Db2 SaaS instance that you want to monitor. If you have deployments in more than one region, you must provision Monitoring and enable platform metrics for each region.

To set up Monitoring,

From the IBM Cloud navigation menu, select Observability.
Select Monitoring.
Either use an existing Monitoring service instance or create a new one.
After the instance is ready, enable platform metrics by clicking Configure platform metrics.
Select a region and then a Monitoring instance from that region. If you have deployments in more than one region, you must provision Monitoring and enable platform metrics for each region.

Accessing your IBM Cloud Monitoring metrics

To see your IBM Db2 SaaS customer metrics dashboards in Monitoring:

From the IBM Cloud navigation menu, select Observability.
Select Monitoring.
Select View IBM Cloud Monitoring to open the dashboard.

For more information, see Monitoring Getting started tutorial.

Metrics available by Service Plan

Metric Name
Database Availability Check
Database commits time
Database rollbacks
Disaster recovery Log Gap
High Availability Disaster Recovery Log Gap
Is disaster recovery connected?
Is disaster recovery configured?
Last backup duration in minutes
Log Disk wait
Number of Unique ID statements
Number of rows deleted
Number of rows updated
Numbers of rows inserted
Time since last backup in hours
Total Activities Aborted
Total Activities Completed
Total Activities Rejected
Total Connections
Total number of commits

Database Availability Check

Table 1. Database availability check metric
Metadata	Description
`Metric Name`	`ibm_db2_db_availability_check`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`The current status of the database.`

Database commits time

Table 2. Database commits time metric
Metadata	Description
`Metric Name`	`ibm_db2_db_commits_time`
`Metric Type`	`counter`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`Indicates the number of applications that are currently connected to the database.`

Database rollbacks

Table 3. Database rollback metric
Metadata	Description
`Metric Name`	`ibm_db2_db_rollbacks`
`Metric Type`	`counter`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`Total number of rollback statements issued by the client application and total number of rollbacks initiated internally by the database manager.`

Disaster recovery Log Gap

Table 4. Disaster recovery Log Gap metric
Metadata	Description
`Metric Name`	`ibm_db2_dr_log_gap`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`Disaster Recovery Log Gap.`

High Availability Disaster Recovery Log Gap

Table 5. High Availability disaster recovery log gap metric
Metadata	Description
`Metric Name`	`ibm_db2_hadr_log_gap`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`HADR Log Gap monitor element This element shows the recent average of the gap between the PRIMARY_LOG_POS value and STANDBY_LOG_POS value. The gap is measured in number ofbytes.`

Is disaster recovery connected?

Table 6. Disaster recovery status metric
Metadata	Description
`Metric Name`	`ibm_db2_is_dr_connected`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`Availability disaster recovery connection status of the database.`

Is disaster recovery configured?

Table 7: Metric metadata
Metadata	Description
`Metric Name`	`ibm_db2_is_dr_configured`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`Is this formation configured with DR.`

Last backup duration in minutes

Table 8. Last backup time mteric
Metadata	Description
`Metric Name`	`ibm_db2_last_backup_duration_minutes`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`The duration of the last successful backup.`

Log Disk wait

Table 9. Log Disk wait metric
Metadata	Description
`Metric Name`	`ibm_db2_log_disk_wait`
`Metric Type`	`counter`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`The number of times agents have to wait for log data to write to disk.`

Number of Unique ID statements

Table 10. Number of unique ID statements metric
Metadata	Description
`Metric Name`	`ibm_db2_uid_stmts`
`Metric Type`	`counter`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`The number of UPDATE, INSERT, MERGE and DELETE statements that were executed.`

Number of rows deleted

Table 11. Number of rows deleted metric
Metadata	Description
`Metric Name`	`ibm_db2_rows_deleted`
`Metric Type`	`counter`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`Total of number of row deletions attempted and total number of rows deleted from the database as a result of internal activity.`

Number of rows updated

Table 12. Number of rows updated metric
Metadata	Description
`Metric Name`	`ibm_db2_rows_updated`
`Metric Type`	`counter`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`Total number of row updates attempted and total number of rows updated from the database as a result of internal activity.`

Numbers of rows inserted

Table 13. Number of rows inserted metric
Metadata	Description
`Metric Name`	`ibm_db2_rows_inserted`
`Metric Type`	`counter`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`Total number of row insertions attempted and total number of rows inserted from the database as a result of internal activity.`

Time since last backup in hours

Table 14. Time since last backup in hours metric
Metadata	Description
`Metric Name`	`ibm_db2_since_last_backup_hours`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`The number of hours since there was a last successful backup.`

Total Activities Aborted

Table 15. Total activities aborted metric
Metadata	Description
`Metric Name`	`ibm_db2_db_act_aborted`
`Metric Type`	`counter`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`The total number of coordinator activities at any nesting level that completed with errors.`

Total Activities Completed

Table 16. Total activities completed metric
Metadata	Description
`Metric Name`	`ibm_db2_db_act_completed`
`Metric Type`	`counter`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`The total number of coordinator activities at any nesting level that completed successfully.`

Total Activities Rejected

Table 17. Total activities rejected metric
Metadata	Description
`Metric Name`	`ibm_db2_db_act_rejected`
`Metric Type`	`counter`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`The total number of coordinator activities at any nesting level that were rejected instead of being allowed to execute.`

Total Connections

Table 18. Total connections metric
Metadata	Description
`Metric Name`	`ibm_db2_total_conn`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`, `Resource`
`Metric Description`	`Indicates the number of applications that are currently connected to the database.`

Total number of commits

Table 19. Total number of commits metric
Metadata	Description
`Metric Name`	`ibm_db2_db_num_commits`
`Metric Type`	`counter`
`Value Type`	`none`
`Segment By`	`Service instance` , `Resource`
`Metric Description`	`Total number of commit statements issued by the client application and the total number of commits initiated internally by the database manager.`

Attributes for Segmentation

Global Attributes

The following attributes are available for segmenting all of the metrics listed above

Attribute	Attribute Name	Attribute Description
`Cloud Type`	`ibm_ctype`	The cloud type is a value of public, dedicated or local
`Location`	`ibm_location`	The location of the monitored resource - this may be a region, data center or global
`Resource`	`ibm_resource`	The database member resource being measured by the service
`Scope`	`ibm_scope`	The scope is the account, organization or space GUID associated with this metric
`Service name`	`ibm_service_name`	Name of the service generating this metric

Additional Attributes

The following attributes are available for segmenting one or more attributes as described in the reference above. Please see the individual metrics for segmentation options.

Attribute	Attribute Name	Attribute Description
`Service instance`	`ibm_service_instance`	The service instance segment identifies the instance the metric is associated with