Home icon

Alerting Best Practices with Amazon Managed Service for Prometheus

AWS Cloud Operations Blog



This article provides best practices for implementing alerting with Amazon Managed Service for Prometheus (AMP), using a practical example of Example Corp monitoring their EKS workloads.

  • Recording rules precompute complex PromQL queries to optimize performance and simplify alerting
  • Alerting rules define conditions triggering notifications when thresholds are exceeded
  • AlertManager groups and deduplicates alerts to reduce notification fatigue
  • Configure AlertManager with SNS or direct PagerDuty integration for alert routing
  • Monitor rule evaluation health using CloudWatch metrics and vended logs
  • Use provided Grafana dashboard to visualize alert states and rule performance
  • CloudWatch Logs Insights helps troubleshoot misconfigured or failing rules

The guide demonstrates creating recording and alerting rules via YAML, uploading configurations using AWS CLI, and monitoring rule execution to maintain effective incident response while minimizing alert fatigue.



Go to article

The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.

Related articles

Oct 30
2025
Amazon Managed Service for Prometheus adds anomaly detection
Oct 16
2024
Amazon Managed Service for Prometheus now supports configuring a minimum firing period for alerts
Sep 18
2025
Optimizing metrics ingestion with Amazon Managed Service for Prometheus
Aug 15
2025
Amazon Managed Service for Prometheus adds support resource policies

The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.