17.1.2 Cost for Using CloudWatch Monitoring
There are no surcharges for using CloudWatch monitoring in HeatWave on AWS. However, enabling CloudWatch monitoring will incur charges on your AWS account. Metrics are emitted using CloudWatch logs in the embedded metric format (EMF), for which costs are incurred. Users should consult the Amazon CloudWatch Pricing for details on CloudWatch-related charges. Here is a breakdown of the charges to your AWS account incurred by enabling CloudWatch monitoring on HeatWave on AWS:
- Log ingestion costs: Metrics are sent to your AWS CloudWatch account as log events
in EMF format, under the
/OracleHeatWave/metrics
log group. - Log archival costs: By default, the retention period on the
/OracleHeatWave/metrics
log group is 30 days. You can change the retention period for this log group in your AWS account. -
Metric costs: Each metric incurs charges in Amazon CloudWatch. Metric charges are prorated by the hour and metered only when metrics are sent to CloudWatch.
Note:
For metrics with multiple dimensions, CloudWatch counts each unique combination of dimensions as a separate metric and charged it as so. For example if you enable monitoring on a DB System with an attached HeatWave cluster and choosesystem.memory.usage
as a metric, you will be paying for HeatWave Cluster size + 1 metrics in CloudWatch, because the chosen metric will monitor the memory usage on the associated DB System as well as all HeatWave nodes in your cluster.
Parent topic: CloudWatch Monitoring