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.

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

Remove 1h backfilling limitation #27

Open
joaogbcravo opened this issue Feb 8, 2023 · 0 comments
Open

Remove 1h backfilling limitation #27

joaogbcravo opened this issue Feb 8, 2023 · 0 comments
Labels
feature New feature or improvement requested proposed Proposed by community, to be reviewed by service team

Comments

@joaogbcravo
Copy link

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 #18

However, our use case is different. I don't want to simply do a migration from one database to AMP (although that would also be important). We want to be able to send metrics at any time, despite how old they are.

We work with edge devices that, from time to time, are not connected to the internet. Those edge devices, when not connected to the internet and therefore unable to push the metrics, keep them on a local cache. As soon as they have an internet connection, they should be able to push that cache (sometimes older than 1h, 1 day, or in rare cases 1 week) to AMP.

This 1-hour limitation seems to be just a particular AMP limitation. At the moment, this is a blocker for our edge devices to use AMP, and therefore we keep using a self-managed Prometheus.

@ampabhi-aws ampabhi-aws added feature New feature or improvement requested proposed Proposed by community, to be reviewed by service team labels Feb 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or improvement requested proposed Proposed by community, to be reviewed by service team
Projects
None yet
Development

No branches or pull requests

2 participants