Amazon Redshift integration

중요

Enable the AWS CloudWatch Metric Streams integration to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option.

New Relic infrastructure integrations include an integration for reporting your Amazon Redshift data to New Relic. This document explains how to activate the integration and describes the data reported.

Features

Amazon Redshift is a fully managed data warehouse that makes it simple and cost-effective to analyze all your data using standard SQL and your existing Amazon Business Intelligence (BI) tools. New Relic's Redshift integration gathers metric and configuration data for the relational databases associated with your Amazon Redshift account.

Reported data includes bytes received and bytes transmitted, health status, database connections, latency, and other metrics). Your Redshift data is available in pre-built and you can also create custom queries and charts.

Activate integration

To enable this integration, follow standard procedures to Connect AWS services to New Relic.

To allow New Relic to access Redshift data, your AWS account must have the ReadOnly policy associated with it, or the following permissions must be granted to your New Relic account:

describeClusters
describeClusterParameters

Configuration and polling

You can change the polling frequency and filter data using configuration options.

Default polling information for the Amazon RedShift integration:

New Relic polling interval: 5 minutes
Amazon CloudWatch data interval: 1 minute

Find and use data

To find your integration data, go to one.newrelic.com > All capabilities > Infrastructure > AWS and select one of the Redshift integration links.

You can query and explore your data using the DatastoreSample event type, with a provider value of RedshiftNode for Redshift nodes, or RedshiftCluster for Redshift clusters.

For more on how to use your data, see Understand and use integration data.

Metric data

New Relic collects the following Amazon Redshift data. For full descriptions of each metric, see Amazon's Redshift documentation.

Name	Data type	Dimension
`CPUUtilization`	percent	`NodeID, ClusterIdentifier`
`DatabaseConnections`	count	`ClusterIdentifier`
`HealthStatus`	1/0 (`HEALTHY`/`UNHEALTHY` in the Amazon CloudWatch console)	`ClusterIdentifier`
`MaintenanceMode`	1/0 (`ON`/`OFF` in the Amazon CloudWatch console)	`ClusterIdentifier`
`NetworkReceiveThroughput`	bytes/seconds (`MB/s` in the Amazon CloudWatch console)	`NodeID`, `ClusterIdentifier`
`NetworkTransmitThroughput`	bytes/seconds (`MB/s` in the Amazon CloudWatch console)	`NodeID`, `ClusterIdentifier`
`PercentageDiskSpaceUsed`	percent	`NodeID`, `ClusterIdentifier`
`QueriesCompletedPerSecond`	count/second (for multi-node clusters)	`latency`, `ClusterIdentifier`
`QueryDuration`	microseconds (for multi-node clusters)	`latency`, `ClusterIdentifier`
`ReadIOPS`	count/second	`NodeID`, `ClusterIdentifier`
`ReadLatency`	seconds	`NodeID`
`ReadThroughput`	bytes (`GB/s` in the Amazon CloudWatch console)	`NodeID`
`WLMQueriesCompletedPerSecond`	count/second (for multi-node clusters)	`ClusterIdentifier`
`WLMQueryDuration`	Microseconds (for multi-node clusters)	`ClusterIdentifier`
`WriteIOPS`	count/seconds	`NodeID`
`WriteLatency`	seconds	`NodeID`
`WriteThroughput`	bytes (`GB/s` in the Amazon CloudWatch console)	`NodeID`

Dimensions Amazon Redshift metrics

Amazon Redshift data can be filtered along any of the following dimensions:

Dimension	Description
`NodeID`	Filters requested data that is specific to the nodes of a cluster. `NodeID` will be either `Leader`, `Shared`, or `Compute-N`, where `N` is 0, 1, etc. for the number of nodes in the cluster. `Shared` means that the cluster has only one node. The `Leader` node and `Compute` node are combined.
`ClusterIdentifier`	Filters requested data that is specific to the cluster. Metrics that are specific to clusters include `HealthStatus`, `MaintenanceMode`, and `DatabaseConnections`. In general, metrics for this dimension (for example, `ReadIOPS`) that are also metrics of nodes represent an aggregate of the node metric data. Take care in interpreting these metrics, because they aggregate behavior of `Leader` and `Compute` nodes.

Dimension

Description

NodeID

Filters requested data that is specific to the nodes of a cluster. NodeID will be either Leader, Shared, or Compute-N, where N is 0, 1, etc. for the number of nodes in the cluster.

Shared means that the cluster has only one node. The Leader node and Compute node are combined.

ClusterIdentifier

Filters requested data that is specific to the cluster. Metrics that are specific to clusters include HealthStatus, MaintenanceMode, and DatabaseConnections.

In general, metrics for this dimension (for example, ReadIOPS) that are also metrics of nodes represent an aggregate of the node metric data. Take care in interpreting these metrics, because they aggregate behavior of Leader and Compute nodes.