14 Metrics install automatically if you have Redgate Monitor installed.
If you are using Redgate’s SQL Server monitoring tool, Redgate Monitor, you can instantly install and run this metric on your servers.
Sustained high CPU starves every session on the instance and is a leading indicator of run-away queries or under-sized hardware. This type of monitoring can create white noise in a CPU busy system — only use if the database has been appropriately sized and CPU > 90 is an anomaly that must be addressed.
Required permissions:
GRANT SELECT ON V_$SYSMETRIC TO redgate_monitor_user CONTAINER=ALL;
These are covered by Redgate Monitor’s standard Oracle monitoring user — if it was set up as described in the product documentation, no additional grants are needed.
Metric definition
Name
Host CPU Utilisation %
Description
Reads Oracle's own Host CPU Utilization (%) system metric from V$SYSMETRIC, which is maintained continuously and is very cheap to query. GROUP_ID = 2 selects the 60-second interval metric; the MAX() aggregate and constant con_id 0 make the query portable across non-CDB, multitenant CDB, and RDS connections.
Supported database engine
- Oracle
The T-SQL query that will collect data
Instances to collect from
Select appropriately-sized instances where high CPU is anomalous
Databases to collect from
Not applicable — Oracle custom metrics collect once per instance, and values are stored per container (PDB) via the con_id column
Collection frequency
60
seconds (collected every minute)
Use collected or calculated values
Leave the Use a calculated rate of change between collections check box unchecked
Metric collection
Enabled
Alert definition
Alert name
Host CPU sustained above 90%
Description
Raise an alert when the metric value goes
Above the defined threshholds
Default threshold values
| High: | 90 |
| Medium: | |
| Low: |
Raise an alert when the threshold is passed for
3 collections
Alert is
Enabled
