Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

📊Tracking: Amazon Managed Service for Prometheus #14353

Open
ccfife opened this issue Apr 23, 2021 · 4 comments
Open

📊Tracking: Amazon Managed Service for Prometheus #14353

ccfife opened this issue Apr 23, 2021 · 4 comments
Labels
feature-request A feature should be added or improved. management/tracking Issues that track a subject or multiple issues p1

Comments

@ccfife
Copy link
Contributor

ccfife commented Apr 23, 2021

Add your +1 👍 to help us prioritize high-level constructs for this service

Overview:

Amazon Managed Service for Prometheus (AMP) is a Prometheus-compatible monitoring service that makes it easy to monitor containerized applications at scale. The Cloud Native Computing Foundation’s Prometheus project is a popular open source monitoring and alerting solution optimized for container environments. With AMP, you can use the open source Prometheus query language (PromQL) to monitor the performance of containerized workloads without having to manage the underlying infrastructure required to manage the ingestion, storage, and querying of operational metrics. AMP automatically scales as your workloads grow or shrink, and is integrated with AWS security services to enable fast and secure access to data. You can collect Prometheus metrics from Amazon Elastic Kubernetes Service (Amazon EKS) and Amazon Elastic Container Service (Amazon ECS) environments, using AWS Distro for OpenTelemetry or Prometheus servers as collection agents.

AWS Docs

Maturity: CloudFormation resources needed

See the AWS Construct Library Module Lifecycle doc for more information about maturity levels.

Implementation:

See the CDK API Reference for more implementation details.

Issue list:

This is a 📊Tracking Issue
@ccfife ccfife added management/tracking Issues that track a subject or multiple issues needs-cfn This issue is waiting on changes to CloudFormation before it can be addressed. labels Apr 23, 2021
@kcoleman731 kcoleman731 mentioned this issue Aug 15, 2021
Closed
@dbluxo
Copy link

dbluxo commented Oct 18, 2021

I am a bit irritated, since it was officially announced here that the AMP service can already be built via CDK. What am I missing? 🤔

@Jazzepi
Copy link

Jazzepi commented May 26, 2022

@dbluxo And for anyone else coming here with the same confusion as me there is CDK support for AMP, but it's under ASP, not AMP.

https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_aps-readme.html

@peterwoodworth
Copy link
Contributor

We have some Cfn resources for this as linked above - The next step for making these L2 constructs is to go through the RFC process. We require an RFC for all new L2 constructs

@peterwoodworth peterwoodworth removed the needs-cfn This issue is waiting on changes to CloudFormation before it can be addressed. label Jun 21, 2022
@ashishdhingra ashishdhingra added p2 feature-request A feature should be added or improved. labels Jul 31, 2024
@github-actions github-actions bot added p1 and removed p2 labels Aug 4, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Aug 4, 2024

This issue has received a significant amount of attention so we are automatically upgrading its priority. A member of the community will see the re-prioritization and provide an update on the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature-request A feature should be added or improved. management/tracking Issues that track a subject or multiple issues p1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@Jazzepi @dbluxo @ccfife @peterwoodworth @ashishdhingra