amazon-managed-service-for-prometheus-roadmap icon indicating copy to clipboard operation
amazon-managed-service-for-prometheus-roadmap copied to clipboard

Amazon Managed Service for Prometheus Public Roadmap

Results 23 amazon-managed-service-for-prometheus-roadmap issues
Sort by recently updated
recently updated
newest added

The current metrics and logs provide limited visibility into how queries perform in AMP. The users don't have visibility into the query duration, queries per second, failed queries, or how...

proposed

Prometheus (as deployed by the commonly used operator chart) is difficult to maintain and a resource hog; because of that AMP is very attractive. Alertmanager though works fine for our...

proposed

# Why In order to do solve capacity planning, SLI/SLO, or long term performance analysis, AMP needs to support long term trending queries beyond the 32 day limit that exists...

feature
proposed

Summary: Remove the limitation "Metric samples older than 1 hour are refused from being ingested" as stated at https://docs.aws.amazon.com/prometheus/latest/userguide/AMP_quotas.html There is at least a similar issue like this one https://github.com/aws/amazon-managed-service-for-prometheus-roadmap/issues/18...

feature
proposed

Summary: Enable [remote read api protocol ](https://prometheus.io/docs/prometheus/latest/querying/remote_read_api/) Enabling remote read api protocol allows users to take their data from AMP easily and fast, skipping the PromQL evaluation. Some of the...

feature
proposed

According to [AWS documentation](https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-alertmanager-receiver-JSON.html) we can use templates to produce JSON based output from alert manager. But in practice the output of templates get overwritten by the content of the...

feature
upstream

The Prometheus API endpoint - `api/v1/tsdb/status` exposes a bunch of metrics(see attached tsdb.txt) around label cardinality, active series per metrics, head series related metrics etc. At present, Amazon Managed Prometheus...

feature
upstream

This is along the lines of a similar [feature request](https://github.com/aws/amazon-managed-service-for-prometheus-roadmap/issues/15) but I would suggest an option to backfill data that is older than 1 hour to enable a simpler migration...

feature
proposed

It could be advantageous for some customers to have visibility into what the current service quotas are, per workspace. This would especially come in handy if there are multiple workspaces...

feature
proposed

Hey folks, please consider adding support for importing existing metrics, especially if they are already in S3.

feature
proposed