Documentationbreadcrumb arrow Grafana Cloudbreadcrumb arrow Monitor infrastructurebreadcrumb arrow Cloud Provider Observabilitybreadcrumb arrow AWS observabilitybreadcrumb arrow CloudWatch metricsbreadcrumb arrow Preconfigured dashboards and alerts
Grafana Cloud

Preconfigured dashboards and alerts

Cloud Provider Observability provides the following preconfigured dashboards and alerts for you to install in your Grafana Cloud instance. These dashboards are embedded in and accessible in the AWS Observability section of Cloud Provider Observability in Grafana Cloud.

Preconfigured dashboards

Preconfigured dashboards are out-of-the-box visualizations available in Grafana Cloud for popular Amazon services.

Cloud Provider Observability provides preconfigured dashboards for the following AWS services. Click the links to view details on the default metrics pulled from Amazon CloudWatch metrics.

Compute Services

  • Amazon Elastic Compute Cloud metrics: AWS/EC2

    For more information on the metrics included and how to optimize your resources using them refer to AWS EC2 dashboard.

  • Amazon Elastic Container Service metrics: AWS/ECS

  • AWS Lambda metrics: AWS/Lambda

Storage Services

  • Amazon Elastic Block Store metrics: AWS/EBS
  • Amazon Simple Storage Service metrics: AWS/S3

Database Services

Networking & Content Delivery

Application Integration

  • Amazon Simple Email Service metrics: AWS/SES
  • Amazon Simple Queue Service metrics: AWS/SQS

Analytics & Streaming

  • Amazon Managed Streaming for Apache Kafka metrics: AWS/Kafka

AI/ML Services

Management & Governance

Note

The preconfigured dashboard for AWS ELB Classic Load Balancer metrics was deprecated.

Preconfigured alerts

When you configure CloudWatch metrics, the following prebuilt alerts are available.

AWS DynamoDB

  • AwsDynamoDBConditionalCheckFailedRequests: Fires if there is a high number of conditional check failed requests on the table that could indicate issues with the application logic or data inconsistency in DynamoDB.
  • AwsDynamoDBHighNumberOfThrottledRequests: Fires if there is a high number of throttle requests, meaning the specified table is receiving more traffic than what it can handle based on the provisioned read and write capacity. This issue can lead to slower performance and failures in your application. You need to increase provisioned capacity if necessary or switch to On-Demand mode.
  • AwsDynamoDBHighReadCapacityUtilization: Fires if the DynamoDB account read quota utilization is high, meaning the account-level provisioned read capacity limit is being approached in the specified region. This affects ALL provisioned DynamoDB tables in that region and prevents further table provisioning/scaling. You need to check Service Quotas for DynamoDB Read Capacity in the specified region.
  • AwsDynamoDBHighSystemErrors: Fires if there are high system errors, meaning there were internal issues with the specified table while executing the specified operation.
  • AwsDynamoDBHighWriteCapacityUtilization: Fires if the DynamoDB account write quote utilization is high, meaning the account-level provisioned write capacity limit is being approached in the specified region. This affects ALL provisioned DynamoDB tables in that region and prevents further table provisioning/scaling. You need to check Service Quotas for DynamoDB Write Capacity in the specified region.

AWS EBS

  • AwsEBSHighVolumeUtilization: Fires if there EBS volume utilization is too high. You need to increase IOPS or resize the EBS volume for better performance.
  • AwsEBSHighVolumeQueueLength: Fires if you need to investigate whether the workload exceeds the provisioned IOPS or if there are inefficiencies in the application. You need to resize or upgrade the specified volumes to handle the queue.
  • AwsEBSLowBurstBalance: Fires if EBS volume burst balance is low. You need to upgrade the EBS volume to a provisioned IOPS volume for consistent performance.
  • AwsEBSLowIdleTime: Fires if there is very low idle time. You need to investigate processes causing high disk usage on the volume.

AWS EC2

  • AwsEC2HighCpuUtilization: Fires if CPU utilization is too high for your EC2 instance indicating it is under heavy load and may become unresponsive.
  • AwsEC2StatusCheckFailed: Fires if the EC2 instance status check fails. You need to view the AWS EC2 health checks and investigate underlying issues for the specified instance.

AWS ElastiCache

  • AwsElastiCacheHasEvictions: Fires if evictions are detected for the specified cluster which could have an impact on memory.
  • AwsElastiCacheHighCpuUtilization: Fires if CPU utilization is too high for the specified cluster indicating it is under heavy load and may become unresponsive.
  • AwsElatiCacheHighReplicationLag: Fires if the specified cluster has high replication lag which indicates it may become stale.
  • AwsElastiCacheHighSwapUsage: Fires if the specified cluster has high swap usage that might lead to insufficient memory.

AWS Kafka

  • AwsKafkaActiveControllerCount: Fires if the cluster does not have exactly one active controller, meaning the specified clusters have a controller issue.
  • AwsKafkaHighRootDiskUsed: Fires if root disk used percentage is too high, meaning the specified broker’s root disk is almost at capacity and needs to have free space increased.
  • AwsKafkaHighSystemCpu: Fires if system CPU is too high, meaning the specified cluster is under heavy load and may become unresponsive.
  • AwsKafkaOfflinePartitions: Fires if offline partitions are detected in a specified cluster.
  • AwsKafkaPatitionUnderReplicated: Fires if under replicated partitions are detected in the specified cluster.

AWS Lambda

  • AwsLambdaInvocationFailures: Fires if Lambda invocation failures are detected in the specified function. This issue indicates errors in function execution that may affect application functionality.
  • AwsLambdaThrottlingEvents: Fires if Lambda function throttling is detected in the specified function due to concurrency limits. This issue may cause request failures and degraded performance.

AWS RDS

  • AwsRDSDiskIOPSBottleneck: Fires if there is a disk IOPS bottleneck detected. You need to upgrade the specified instances to Provisioned IOPS storage (gp3/io1) or investigate inefficient queries.
  • AwsRDSHighCpuLoad: Fires if sustained high CPU load is detected on your RDS instance. You need to scale up the specified instance, optimize queries, or investigate long-running queries.
  • AwsRDSHighCpuSpikes: Fires if unexpected CPU spikes are detected on your RDS instance that may be causing latency issues or throttling.
  • AwsRDSReadReplicaLag: Fires if RDS replicas are too slow.

Install AWS preconfigured dashboards and alerts

To install and view your AWS preconfigured dashboards and alerts:

  1. After configuring a CloudWatch metrics scrape or stream job, click the Configuration tab at the top of the Cloud Provider AWS page.
  2. Scroll down to the Dashboards and Alerts Installation section and click Install dashboards and alerts.
  3. Click the Services tab.
  4. Locate and click the specific service or source you want to see a dashboard for in the list. Use the Service or Source filters to help you find the source or service you want to see.

Refine dashboard data

You can use the following filters on dashboards to refine your data:

  • Data source
  • Job
  • Resource group
  • Subscription name
  • Resource name

Additionally, use the time range selector to change time period of your data.

View predictions

For the preconfigured dashboards that include drilldown information for specific instances, Cloud Provider Observability includes machine learning predictions. Predictions can help you ensure resources are available during spikes in usage, as well as help you decrease the amount of unused resources due to over provisioning. To use prediction tools, first enable LLM features for your Grafana instance.

You can view the prediction model for various metrics by clicking the Predict button in the top right corner of the panel.

Screenshot of a panel with the Predict button and time range filter highlighted

Use the time range filter to adjust the time range to show more advanced predictions. The time range you select must be at least two hours to use the prediction tool.

For more information on the terminology included and how machine learning works in the prediction graph, refer to the Query Metrics page in the AI and machine learning documentation.

Access Nodes in Kubernetes accounts

From EC2 instance pages in Cloud Provider Observability, you can navigate to Node or Cluster detail pages for AWS managed Kubernetes in Kubernetes Monitoring. The Kubernetes detail pages includes details about the Kubernetes Node or Cluster your EC2 instance is on including the following details: Cluster and Pod information, OS and kubelet version, and optimization metrics such as CPU and memory requests and capacity.

To drilldown into the AWS managed Kubernetes Node or Cluster details of an EC2 instance, complete the following steps:

  1. From the Services tab in Cloud Provider AWS, find and select AWS/EC2.

  2. Select the EC2 instance from the Service column to open the instance overview page.

  3. On the far right-side of the instance overview page, click the Kubernetes drop-down button and the Node link to open the Node overview or the Cluster link to open the Cluster overview.

    EC2 instance overview page with Kubernetes drop-down and Node and Cluster links

To return to the Cloud Provider AWS Monitoring view of the instance:

  • On the Kubernetes Node overview page, click the AWS drop-down and the EC2 instance link or click the Back to EC2 Instance button.

    Kubernetes Node overview page with AWS drop-down and EC2 instance link

  • On the Kubernetes Cluster overview page, click the Back to EC2 Instance button.

    Kubernetes Cluster instance overview page with Back to EC2 Instance link

To learn more about what information is available about the Kubernetes Cluster or Node, refer to Explore your infrastructure with Kubernetes Monitoring.

Manage alerts

To view alerts, navigate to the Alerts tab.

To see a recommendation for alert resolution, click the tooltip in the row of the Summary column.

In the Alert column, click the alert to view the dashboard for that service.