Performance data in Amazon Redshift
Using CloudWatch metrics for Amazon Redshift, you can get information about your cluster's health and performance and see information at the node level. When working with these metrics, keep in mind that each metric has one or more dimensions associated with it. These dimensions tell you what the metric is applicable to, that is the scope of the metric. Amazon Redshift has the following two dimensions:
-
Metrics that have a
NodeIDdimension are metrics that provide performance data for nodes of a cluster. This set of metrics includes leader and compute nodes. Examples of these metrics includeCPUUtilization,ReadIOPS,WriteIOPS. -
Metrics that have only a
ClusterIdentifierdimension are metrics that provide performance data for clusters. Examples of these metrics includeHealthStatusandMaintenanceMode.Note
In some metric cases, a cluster-specific metric represents an aggregation of node behavior. In these cases, take care in the interpretation of the metric value because the leader node's behavior is aggregated with the compute node.
For general information about CloudWatch metrics and dimensions, see CloudWatch concepts in the Amazon CloudWatch User Guide.
For a further description of CloudWatch metrics for Amazon Redshift, see the following sections.
Topics
Amazon Redshift metrics
The AWS/Redshift namespace includes the following metrics. Unless
stated otherwise, metrics are collected at 1-minute intervals.
| Metric | Description |
|---|---|
CommitQueueLength |
The number of transactions waiting to commit at a given point in time. Units: Count Dimensions: |
ConcurrencyScalingActiveClusters |
The number of concurrency scaling clusters that are actively processing queries at any given time. Units: Count Dimensions: |
ConcurrencyScalingSeconds |
The number of seconds used by concurrency scaling clusters that have active query processing activity. Units: Count Dimensions: |
CPUUtilization |
The percentage of CPU utilization. For clusters, this metric represents an aggregation of all nodes (leader and compute) CPU utilization values. Units: Percent Dimensions: Dimensions: |
DatabaseConnections |
The number of database connections to a cluster. Units: Count Dimensions: |
HealthStatus |
Indicates the health of the cluster. Every minute the cluster connects to its database and performs a simple query. If it is able to perform this operation successfully, the cluster is considered healthy. Otherwise, the cluster is unhealthy. An unhealthy status can occur when the cluster database is under extremely heavy load or if there is a configuration problem with a database on the cluster. NoteIn Amazon CloudWatch, this metric is reported as 1 or 0 whereas in
the Amazon Redshift console, this metric is displayed with the
words Units: Count (1/0)
( Dimensions: |
MaintenanceMode |
Indicates whether the cluster is in maintenance mode. NoteIn Amazon CloudWatch, this metric is reported as 1 or 0 whereas in
the Amazon Redshift console, this metric is displayed with the
words Units: Count (1/0) ( Dimensions: |
MaxConfiguredConcurrencyScalingClusters |
Maximum number of concurrency scaling clusters configured from the parameter group. For more information, see Amazon Redshift parameter groups. Units: Count Dimensions: |
NetworkReceiveThroughput |
The rate at which the node or cluster receives data. Units: Bytes/Second (MB/s in the Amazon Redshift console) Dimensions: Dimensions: |
NetworkTransmitThroughput |
The rate at which the node or cluster writes data. Units: Bytes/Second (MB/s in the Amazon Redshift console) Dimensions: Dimensions: |
PercentageDiskSpaceUsed |
The percent of disk space used. Units: Percent Dimensions: Dimensions: |
QueriesCompletedPerSecond |
The average number of queries completed per second. Reported in 5-minute intervals. This metric isn't supported on single-node clusters. Units: Count/Second Dimensions: Dimensions: |
QueryDuration |
The average amount of time to complete a query. Reported in 5-minute intervals. This metric isn't supported on single-node clusters. Units: Microseconds Dimensions: Dimensions: Dimensions: |
QueryRuntimeBreakdown |
The total time queries spent running by query stage. Reported in 5-minute intervals. Units: Milliseconds Dimensions: ClusterIdentifier, NodeID, stage Dimensions: ClusterIdentifier, stage |
ReadIOPS |
The average number of disk read operations per second. Units: Count/Second Dimensions: Dimensions: |
ReadLatency |
The average amount of time taken for disk read I/O operations. Units: Seconds Dimensions: Dimensions: |
ReadThroughput |
The average number of bytes read from disk per second. Units: Bytes (GB/s in the Amazon Redshift console) Dimensions: Dimensions: |
RedshiftManagedStorageTotalCapacity |
Total managed storage capacity. Units: Megabytes Dimensions:
|
TotalTableCount |
The number of user tables open at a particular point in time. This total doesn't include Amazon Redshift Spectrum tables. Units: Count Dimensions: |
WLMQueueLength |
The number of queries waiting to enter a workload management (WLM) queue. Units: Count Dimensions: Dimensions: |
WLMQueueWaitTime |
The total time queries spent waiting in the workload management (WLM) queue. Reported in 5-minute intervals. Units: Milliseconds. Dimensions: Dimensions: Dimensions: |
WLMQueriesCompletedPerSecond |
The average number of queries completed per second for a workload management (WLM) queue. Reported in 5-minute intervals. This metric isn't supported on single-node clusters. Units: Count/Second Dimensions: Dimensions: |
WLMQueryDuration |
The average length of time to complete a query for a workload management (WLM) queue. Reported in 5-minute intervals. This metric isn't supported on single-node clusters. Units: Microseconds Dimensions: Dimensions: |
WLMRunningQueries |
The number of queries running from both the main cluster and concurrency scaling cluster per WLM queue. Units: Count Dimensions: Dimensions: |
WriteIOPS |
The average number of write operations per second. Units: Count/Second Dimensions: Dimensions: |
WriteLatency |
The average amount of time taken for disk write I/O operations. Units: Seconds Dimensions: Dimensions: |
WriteThroughput |
The average number of bytes written to disk per second. Units: Bytes (GB/s in the Amazon Redshift console) Dimensions: Dimensions: |
SchemaQuota |
The configured quota for a schema. Units: Megabytes Dimensions: Periodic/Push: Frequency: Stop criteria: Schema dropped or quota removed |
NumExceededSchemaQuotas |
The number of schemas with exceeded quotas. Units: Count Dimensions: Periodic/Push: Frequency: Stop criteria: N/A |
StorageUsed |
The disk or storage space used by a schema. Units: Megabytes Dimensions: Periodic/Push: Frequency: Stop criteria: Schema dropped or quota removed |
PercentageQuotaUsed |
The percentage of disk or storage space used relative to the configured schema quota. Units: Percent Dimensions: Periodic/Push: Frequency: Stop criteria: Schema dropped or quota removed |
UsageLimitAvailable |
Depending on the FeatureType, UsageLimitAvailable returns the following:
Units: Minutes or TBs Dimensions: |
UsageLimitConsumed |
Depending on the FeatureType, UsageLimitConsumed returns the following:
Units: Minutes or TBs Dimensions: |
Dimensions for Amazon Redshift metrics
Amazon Redshift data can be filtered along any of the dimensions in the table following.
| Dimension | Description |
|---|---|
latency
|
Possible values are as follows:
|
NodeID
|
Filters requested data that is specific to the nodes of a
cluster. Metrics are reported for the leader node and compute nodes
only for |
ClusterIdentifier
|
Filters requested data that is specific to the cluster.
Metrics that are specific to clusters include
|
service class
|
The identifier for a |
stage
|
The execution stages for a query. The possible values are as follows:
|
wlmid
|
The identifier for a workload management queue. |
QueryPriority
|
The priority of the query. Possible values are
|
QueueName
|
The name of the workload management queue. |
FeatureType
|
The feature that is limited by a usage limit. Possible values
are |
UsageLimitId
|
The identifier for a usage limit. |
Amazon Redshift query and load performance data
In addition to the CloudWatch metrics, Amazon Redshift provides query and load performance data. Query and load performance data can be used to help you understand the relation between database performance and cluster metrics. For example, if you notice that a cluster's CPU spiked, you can find the spike on the cluster CPU graph and see the queries that were running at that time. Conversely, if you are reviewing a specific query, metric data (like CPU) is displayed in context so that you can understand the query's impact on cluster metrics.
Query and load performance data are not published as CloudWatch metrics and can only be viewed in the Amazon Redshift console. Query and load performance data are generated from querying with your database's system tables (for more information, see System tables reference in the Amazon Redshift Developer Guide). You can also generate your own custom database performance queries, but we recommend starting with the query and load performance data presented in the console. For more information about measuring and monitoring your database performance yourself, see Managing performance in the Amazon Redshift Developer Guide.
The following table describes different aspects of query and load data you can access in the Amazon Redshift console.
| Query/Load data | Description |
|---|---|
| Query summary |
A list of queries in a specified time period. The list can be sorted on values such as query ID, query runtime, and status. View this data in the Query monitoring tab of the cluster detail page. |
| Query detail |
Provides details on a particular query including:
|
| Load summary |
Lists all the loads in a specified time period. The list can be sorted on values such as query ID, query runtime, and status. View this data in the Query monitoring tab of the cluster detail page. |
| Load detail |
Provides details on a particular load operation including:
|
