Amazon Managed Service for Prometheus のアイコン

Amazon Managed Service for Prometheus Specialized2020年〜

A Prometheus-compatible managed monitoring service for collecting, querying, and alerting on container metrics

What It Does

Amazon Managed Service for Prometheus (AMP) is a fully managed Prometheus-compatible monitoring service. It collects metrics from container workloads on EKS, ECS, and EC2, and runs queries and alerts using PromQL. It supports the Prometheus remote write API, making migration from existing Prometheus environments easy.

Use Cases

Used for Kubernetes cluster metrics monitoring, container workload performance monitoring, microservices metrics collection and visualization, and scaling large Prometheus environments.

Everyday Analogy

Think of it like a health checkup center. It regularly collects vital signs (metrics) from each patient (container) and detects abnormal values (alerts). Data storage and analysis are handled by the center (AMP), and the doctor (Grafana) reviews the results.

What Is Managed Prometheus?

Amazon Managed Service for Prometheus is a managed service that provides Prometheus storage and query engine. Self-hosted Prometheus faces challenges with storage management, high availability, and long-term retention design, but AMP handles all of these. Metrics are automatically replicated across multiple AZs and retained for 150 days.

Metrics Collection and Alerting

Metrics collection uses Prometheus servers, AWS Distro for OpenTelemetry (ADOT), Grafana Agent, or similar collectors. These collectors send metrics to AMP's remote write endpoint. You can define PromQL-based alert rules in AMP's rule manager and send notifications via SNS. To deepen your practical knowledge of metrics collection and alerting, related books on Amazon are helpful.

Getting Started

Create a workspace in the AMP console. Deploy an ADOT collector or Prometheus server to your EKS cluster and configure the remote write destination to the AMP endpoint. Add AMP as a data source in Managed Grafana to query metrics with PromQL and build dashboards.

Things to Watch Out For

  • Billed based on metrics ingestion volume, storage volume, and query sample processing count
  • Deploying a collector (ADOT, Prometheus server) is required separately for metrics collection
共有するXB!