Amazon Redshift will no longer support the creation of new Python UDFs starting November 1, 2025.
If you would like to use Python UDFs, create the UDFs prior to that date.
Existing Python UDFs will continue to function as normal. For more information, see the
blog post
Performance metrics in the CloudWatch console
When working with Amazon Redshift metrics in the CloudWatch console, keep a couple of things in mind:
-
Query and load performance data is only available in the Amazon Redshift console.
-
Some Metrics in the CloudWatch have different units than those used in the Amazon Redshift console. For example,
WriteThroughput
is displayed in GB/s (as compared to Bytes/s in CloudWatch), which is a more relevant unit for the typical storage space of a node.
When working with Amazon Redshift metrics in the CloudWatch console, command line tools, or an Amazon SDK, keep these concepts in mind:
-
First, specify the metric dimension to work with. A dimension is a name-value pair that helps you to uniquely identify a metric. The dimensions for Amazon Redshift are
ClusterIdentifier
andNodeID
. In the CloudWatch console, theRedshift Cluster
andRedshift Node
views are provided to easily select cluster and node-specific dimensions. For more information about dimensions, see Dimensions in the CloudWatch Developer Guide. -
Then, specify the metric name, such as
ReadIOPS
.
The following table summarizes the types of Amazon Redshift metric dimensions that are available to you. Depending on the metric, data is available in either 1-minute or 5-minute intervals at no charge. For more information, see Amazon Redshift metrics.
CloudWatch namespace | Dimension | Description |
---|---|---|
AWS/Redshift |
NodeID
|
Filters requested data that is specific to the nodes of a cluster.
|
AWS/Redshift |
ClusterIdentifier
|
Filters requested data that is specific to the cluster. Metrics
that are specific to clusters include |
Working with gateway and volume metrics is similar to working with other service metrics. Many of the common tasks are outlined in the CloudWatch documentation, including the following: