Amazon Redshift monitoring

Dynatrace ingests metrics for multiple preselected namespaces, including Amazon Redshift. You can view metrics for each service instance, split metrics into multiple dimensions, and create custom charts that you can pin to your dashboards.


To enable monitoring for this service, you need

  • ActiveGate version 1.181+, as follows:
    • For Dynatrace SaaS deployments, you need an Environment ActiveGate or a Multi-environment ActiveGate.
    • For Dynatrace Managed deployments, you can use any kind of ActiveGate. Note: For role-based access (whether in a SaaS or Managed deployment), you need an Environment ActiveGate installed on an AWS EC2 host.
  • Dynatrace version 1.182+
  • An updated AWS monitoring policy to include the additional AWS services.

To update the AWS IAM policy, use the JSON below, containing the monitoring policy (permissions) for all supporting services.

If you don't want to add permissions to all services, and just select permissions for certain services, consult the table below. The table contains a set of permissions that are required for all services (All monitored Amazon services) and, for each supporting service, a list of optional permissions specific to that service.

Example of JSON policy for one single service.

In this example, from the complete list of permissions you need to select

  • "apigateway:GET" for Amazon API Gateway
  • "cloudwatch:GetMetricData", "cloudwatch:GetMetricStatistics", "cloudwatch:ListMetrics", "sts:GetCallerIdentity", "tag:GetResources", "tag:GetTagKeys", and "ec2:DescribeAvailabilityZones" for All monitored Amazon services.

Enable monitoring

To enable monitoring for this service, you first need to integrate Dynatrace with Amazon Web Services:

Add the service to monitoring

In order to view the service metrics, you must add the service to monitoring in your Dynatrace environment.

Note: Once AWS supporting services are added to monitoring, you might have to wait 15-20 minutes before the metric values are displayed.

Cloud-service monitoring consumption

As of 2021, all cloud services consume Davis data units (DDUs). The amount of DDU consumption per service instance depends on the number of monitored metrics and their dimensions (each metric dimension results in the ingestion of 1 data point; 1 data point consumes 0.001 DDUs).

Monitor resources based on tags

You can choose to monitor resources based on existing AWS tags, as Dynatrace automatically imports them from service instances. Nevertheless, the transition from AWS to Dynatrace tagging isn't supported for all AWS services. Expand the table below to see which supporting services are filtered by tagging.

To monitor resources based on tags

  1. In the Dynatrace menu, go to Settings > Cloud and virtualization > AWS and select Edit for the desired AWS instance.
  2. For Resources to be monitored, select Monitor resources selected by tags.
  3. Enter the Key and Value.
  4. Select Save.

Configure service metrics

Once you add a service, Dynatrace starts automatically collecting a suite of metrics for this particular service. These are recommended metrics. Apart from the recommended metrics, most services have the possibility of enabling optional metrics. You can remove or edit any of the existing metrics or any of their dimensions, where there are multiple dimensions available. Metrics consisting of only one dimension can't be edited. They can only be removed or added.

Service-wide metrics are metrics for the whole service across all regions. Typically, these metrics include dimensions containing Region in their name. If selected, these metrics are displayed on a separate chart when viewing your AWS deployment in Dynatrace. Keep in mind that available dimensions differ among services.

To change a metric's statistics, you have to recreate that metric by choosing different statistics. You can choose among the following statistics: Sum, Minimum, Maximum, Average, and Sample count. The Average + Minimum + Maximum statistics enable you to collect all three statistics as one metric instead of one statistic for three metrics separately. This can reduce your expenses for retrieving metrics from your AWS deployment.

To be able to save a newly added metric, you need to select at least one statistic and one dimension.

Note: Once AWS supporting services are configured, you might have to wait 15-20 minutes before the metric values are displayed.

View service metrics

You can view the service metrics in your Dynatrace environment either on the custom device overview page or on your Dashboards page.

View metrics on the custom device overview page

To access the custom device overview page

  1. In the Dynatrace menu, go to Technologies and processes.
  2. Filter by service name and select the relevant custom device group.
  3. Once you select the custom device group, you're on the custom device group overview page.
  4. The custom device group overview page lists all instances (custom devices) belonging to the group. Select an instance to view the custom device overview page.

View metrics on your dashboard

You can also view metrics in the Dynatrace web UI on dashboards. There is no preset dashboard available for this service, but you can create your own dashboard.

To check the availability of preset dashboards for each AWS service, see the list below.

Available metrics

Name Description Unit Statistics Dimensions Recommended
CPUUtilization The percentage of CPU utilization. For clusters, this metric represents an aggregation of all nodes (leader and compute) CPU utilization values. Percent Multi ClusterIdentifier ✔️
CPUUtilization Percent Multi ClusterIdentifier, NodeID ✔️
DatabaseConnections The number of database connections to a cluster Count Sum ClusterIdentifier; ClusterIdentifier, NodeID
DatabaseConnections Count Multi ClusterIdentifier; ClusterIdentifier, NodeID
HealthStatus Indicates the health of the cluster. Every minute the cluster connects to its database and performs a simple query. If it's 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's a configuration problem with a database on the cluster. Count Average ClusterIdentifier ✔️
HealthStatus Count Average ClusterIdentifier, NodeID
MaintenanceMode Indicates whether the cluster is in maintenance mode Count Multi ClusterIdentifier; ClusterIdentifier, NodeID
NetworkReceiveThroughput The rate at which the node or cluster receives data Bytes/Second Multi ClusterIdentifier ✔️
NetworkReceiveThroughput Bytes/Second Multi ClusterIdentifier, NodeID; ✔️
NetworkTransmitThroughput The rate at which the node or cluster writes data Bytes/Second Multi ClusterIdentifier; ClusterIdentifier, NodeID
PercentageDiskSpaceUsed The percent of disk space used Percent Multi ClusterIdentifier ✔️
PercentageDiskSpaceUsed Percent Multi ClusterIdentifier, NodeID