Grouping alerts by type
To simplify the display and management of alerts, IBM® Db2® Data Management Console prearranges them into two sets of default groupings, Availability and Performance.
Alert types
Types of alerts you can configure include:
| Alert Type | Alert Name | Description |
|---|---|---|
| HADR: monitor one or more HADR-specific metrics | HADR database disconnected | Generates an alert when a database within the cluster becomes disconnected |
| HADR database not ready for role switch | Generate an alert based on the role-switch readiness of your HADR databases | |
| HADR primary database blocked from writing to the log file | Generates an alert when a log shipping request from the primary cluster member logger is blocked | |
| Standby database log receive buffer full | Generates an alert when the log receive buffer on the standby database is full | |
| HADR standby database in replay-only window | Generates an alert when the standby database is in replay-only mode | |
| HADR standby log receiving falling behind log shipping from primary | Generates an alert if the standby cluster is receiving log data more slowly than the shipping rate of the primary cluster | |
| HADR standby receive replay gap | Generates an alert when the gap between the standby log receive position and the standby log replay position reaches a predefined threshold. | |
| Logging: monitor log space, degree of secondary log allocation, space used by dirty pages, and/or HADR log gap | Log space | |
| Memory: monitor use of physical and/or virtual memory, as well as package cache hit ratio | Physical memory in use | |
| Virtual memory in use | ||
| pureScale: monitor one or more pureScale metrics | pureScale member status | |
| Cluster host status | ||
| Cluster caching facility status | ||
| Recovery: monitor recovery-related metrics | Table invalid | |
| Table space drop pending | ||
| Incomplete recovery | ||
| Log archive failed | ||
| Invalid log path | ||
| Table space backup pending | ||
| Status: monitor the availability of your database(s) and/or database partitions | Database partition availability | |
| Database availability | ||
| Database write suspend state | ||
| Storage: monitor file system and table space utilization and state | Table space state | |
| Table space utilization | ||
| Table space container state | ||
| Table space quiesced | ||
| File system utilization | ||
| Table space container utilization |
| Alert Type | Alert | Description |
|---|---|---|
| Alerts that require an enterprise license and repository database: Choose to generate alerts for changes in the state or performance of one or more of the following, based on built-in analytics: | Buffer pool hit ratio degrades | Generates an alert if the ratio between physical reads and memory reads degrades significantly compared to the historical baseline. (repository data collection for Monitoring data must be enabled) |
| Connections: | Connections | |
| Logging: monitor log space, degree of secondary log allocation, space used by dirty pages, and/or HADR log gap | Degree of secondary log allocation | |
| I/O: | Buffer pool hit ratio | |
| Buffer pool hit ratio degrades | ||
| Buffer pool asynchronous write ratio | ||
| Catalog cache hit ratio | ||
| Buffer pool asynchronous read ratio | ||
| Locking: | Application connections with excessive lock waits over request time | |
| Increased table lock wait and lock timeout event hit rate. | ||
| Table deadlock occurred | ||
| Logging: | Log space used by dirty pages | |
| Memory: | Package cache hit ratio | |
| pureScale: | Group buffer pool hit ratio | |
| Total page reclaims per min | ||
| Virtual memory in use in CF system | ||
| Recovery: | Maximum log space exceeded | |
| Sorting: | Post threshold sorts | |
| Sort overflows | ||
| Statements: | Total activity time | |
| Total activity wait time | ||
| Statement performance | ||
| Rows read | ||
| Rows returned | ||
| Time waited on locks | ||
| CPU time | ||
| Workload: | Rollback transactions | |
| Rows read per fetched row |