You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
π I have found these related issues/pull requests
nothing exactly like this. but the closest i could find was someone with a full db #4995
π·οΈ Feature Request Type
Settings
π Feature description
in IP:port/settings/monitor-history, can you add a total max DB size that if it reaches this size, it starts pruning the DB even if we haven't reached number of days
βοΈ Solution
ability to choose max db size, where it prunes oldest first even if max days haven't been reached yet. i'd like to have it store the max number of days worth of info in (size allocated for this container)
would also be cool if it checked the max space available if installed on a VM or bare metal. (idk of a way to do that if it's a container)
β Alternatives
just that.
π Additional Context
No response
The text was updated successfully, but these errors were encountered:
We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.
π I have found these related issues/pull requests
nothing exactly like this. but the closest i could find was someone with a full db #4995
π·οΈ Feature Request Type
Settings
π Feature description
in IP:port/settings/monitor-history, can you add a total max DB size that if it reaches this size, it starts pruning the DB even if we haven't reached number of days
βοΈ Solution
ability to choose max db size, where it prunes oldest first even if max days haven't been reached yet. i'd like to have it store the max number of days worth of info in (size allocated for this container)
would also be cool if it checked the max space available if installed on a VM or bare metal. (idk of a way to do that if it's a container)
β Alternatives
just that.
π Additional Context
No response
The text was updated successfully, but these errors were encountered: