HeatWave Release Notes
The following monitoring practices are recommended:
For MySQL HeatWave on OCI, you can monitor operating system memory usage by setting an alarm to notify you when memory usage on HeatWave nodes remains above 450GB for an extended period of time. If memory usage exceeds this threshold, either reduce the size of your data or add nodes to the HeatWave Cluster. For information about using metrics, alarms, and notifications, refer to MySQL HeatWave Service Metrics, in the MySQL HeatWave on OCI Service Guide.
For MySQL HeatWave on AWS, you can monitor memory usage on the Performance tab of the MySQL HeatWave Console. See Performance Monitoring.
For HeatWave in Oracle Database Service for Azure (ODSA), select Metrics on the details page for the HeatWave Cluster to access Microsoft Azure Application Insights. See About Oracle Database Service for Azure.
Monitor change propagation status. If change propagation is interrupted and tables are not automatically reloaded for some reason, table data becomes stale. Queries that access tables with stale data are not offloaded to HeatWave for processing. For instructions, see Section 2.2.7, “Change Propagation”.