Amazon Managed Service for Prometheus now supports configuring a minimum firing period for alerts

Amazon Managed Service for Prometheus now supports the ability to configure the minimum duration for which an alert remains active, after the condition that triggered the alert is no longer valid. Amazon Managed Service for Prometheus is a fully managed Prometheus-compatible monitoring service that makes it easy to monitor and alarm on operational metrics at scale. Prometheus is a popular Cloud Native Computing Foundation open-source project for monitoring and alerting on metrics from compute environments such as [Amazon Elastic Kubernetes Service](https://aws.amazon.com/eks/). Using a minimum firing period enables you to maintain alerts in active state until the problem is fully resolved, regardless of short-term data changes. It also reduces alert noise and prevents alerts from constantly switching between “firing” and “resolved” states. This feature is now available in all AWS regions where Amazon Managed Service for Prometheus is [generally available](https://docs.aws.amazon.com/prometheus/latest/userguide/what-is-Amazon-Managed-Service-Prometheus.html). Check out the [Amazon Managed Service for Prometheus user guide](https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-ruler-rulesfile.html) for detailed documentation. To learn more about Amazon Managed Service for Prometheus, visit the [product page](https://aws.amazon.com/prometheus/) and [pricing page](https://aws.amazon.com/prometheus/pricing/).