-
-
Notifications
You must be signed in to change notification settings - Fork 390
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
Increase data retention to 30 days #128
Comments
Would love this feature |
@TwiN Do you have any idea about a timeline for this improvement? |
By the way, @TwiN regarding your change of the title of this issue: I see that sometimes the data is retained for at least 30 days, sometimes a lot longer. But in some cases a lot shorter. Probably depending on the 'MaximumNumberOfResults' and 'MaximumNumberOfEvents'? (couldn't find that in the documentation, didn't search the code yet) So I assume that you meant to say "guarantee retention to 30 days; may be a lot longer if few events happen"? |
@mdraijer yeah since people can set their own interval, and these interval can be extremely short (1ms), it'd be a bad idea to save for the past 30 days. What I'll do instead is make MaximumNumberOfResults configurable. |
Agreed, would be sufficient and a neat solution to have that value configurable. |
Signed-off-by: 117503445 <t117503445@gmail.com>
Signed-off-by: 117503445 <t117503445@gmail.com>
Signed-off-by: 117503445 <t117503445@gmail.com>
Signed-off-by: 117503445 <t117503445@gmail.com>
Bringing this back from the dead. I would like to mention that this would be extremely desired from our team as well. It would be great to get 30d, 60d, 90d and 180d intervals. |
Yes, would love as well - we had a longer outage and an extended interval could have helped us to trace back the issue more swiftly! |
For the uptime badges (1h, 24h, 7d), is it possible to also support a month or 30d? Maybe even 1y?
The text was updated successfully, but these errors were encountered: