-
Notifications
You must be signed in to change notification settings - Fork 3
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
Custom storage retention #2
Comments
For us having at least 13 months worth of storage would allow for annual comparison of data trends etc. |
@davidferdinand, what type of annual comparison were you looking to do with extended storage? Are you looking to do a long term trend over a year, or more of a week today to a week in the past comparison? |
@ampabhi-aws probably both, we would have teams who would be interested to see how data might shift with the seasons, and others who might want to do a comparison of this week against this week last year |
It'd be even better if you support downsampling for long-term data (e.g., past 90 days) as well. |
We now support the ability to change your retention period via a service limit increase: https://docs.aws.amazon.com/prometheus/latest/userguide/AMP_quotas.html. I'll create another ticket for downsampling/long-term-trending analysis. |
Currently, the maximum retention time for ingested metrics into an Amazon Managed Service for Prometheus workspace is fixed. That is, data older than 150 days is deleted from the workspace.
With custom storage retention, users would have the ability to change the metrics data retention period on a per-workspace basis. The feature would be exposed via the AWS console, API, CloudFormation, and Terraform.
The text was updated successfully, but these errors were encountered: