You can create monitor requests for each database that the
database server supports. What specific
values you use depends on your system's configuration and
available resources. For example, you may monitor database server
status or database status to reflect the health of your system.
The example values in Table 3-6 “Sample Database Monitor Requests” and Table 3-7 “Sample Server Monitor Requests” assume optimum system conditions
and represent sample monitor request values.
Table 3-6 Sample Database Monitor Requests
| Resources to monitor | Monitoring Parameters |
|---|
| Notify | Value | Option |
|---|
| status | when value is | = | UNAVAILABLE | INITIAL |
| allocated | when value changes | n/a | n/a |
| used | when value is | >= | some number of kilobytes less than the allocated value | INITIAL |
| usage1 | when value is | > | 80 | REPEAT |
Indicates database is approaching capacity.
Table 3-7 Sample Server Monitor Requests
| Resources to monitor | Monitoring Parameters |
|---|
| Notify | Value | Option |
|---|
| status | when value is | not equal | UP | INITIAL |
allowed_ max_ connects | when value changes | n/a | n/a |
| commits | at each interval | n/a | n/a |
commits_ per_sec | when value is | > | some number depending on your expectation of database
usage | INITIAL |
| connects | when value is | >= | some number less than the allowed_max_ connects value | INITIAL |
disk_reads | at each interval | n/a | n/a |
disk_reads_per_sec | when value is | > | some number depending on your expectation of database
usage | INITIAL |
disk_ writes | at each interval | n/a | n/a |
disk_ writes_ per_sec | when value is | > | some number depending on your expectation of database
usage | INITIAL |
logical_ reads | at each interval | n/a | n/a |
logical_ reads_per_sec | when value is | > | some number depending on your expectation of database
usage | INITIAL |
logical_ writes | at each interval | n/a | n/a |
logical_ writes_ per_sec | when value is | > | some number depending on your expectation of database
usage | INITIAL |
peak_ connects1 | at each interval | n/a | n/a |
read_cache_hit_rate | when value is | < | 80 | INITIAL |
| started | when value changes | n/a | n/a |
| uptime | at each interval | n/a | n/a |
| usage1 | when value is | > | 80 | INITIAL |
write_cache_hit_rate | when value is | < | 80 | INITIAL |
If it keeps increasing over time, this
could be an indication that a configuration parameter needs to be
increased.