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
We need a better way for people to configure retention.
Description
Retention configuration should work like this:
[db]
dbengine tier 0 retention days = 7
dbengine tier 1 retention days = 90
dbengine tier 2 retention days = 365
max disk space MB = 3072
The max disk space MB should be applied to the whole /var/cache/netdata directory, including all dbengine tiers and sqlite files.
Disk space size should be checked only when new files are created, on any tier. If the limit is hit, Netdata should rotate files to statisfy the disk size cap and raise an alert to let users know they are losing retention. When rotating files, tiers should be selected proportionally.
If max disk space MB is set to zero, this check should be disabled and Netdata should use any disk size to satisfy the retention defined.
The default settings, should be like above.
Importance
must have
Value proposition
Users should be able to configure retention in days
Users should be able to cap the disk space Netdata will ever use
Users should be informed when the disk space cap is not sufficient for the retention they need
Proposed implementation
As mentioned above.
The text was updated successfully, but these errors were encountered:
Might I suggest that we also check disk space usage on startup as well as whenever a new file needs to be created?
That would allow users to quickly reduce disk space usage of the agent if they need to, without having to wipe all of their historical data or wait for the agent to decide it needs to create a new file.
Problem
We need a better way for people to configure retention.
Description
Retention configuration should work like this:
The
max disk space MB
should be applied to the whole/var/cache/netdata
directory, including all dbengine tiers and sqlite files.Disk space size should be checked only when new files are created, on any tier. If the limit is hit, Netdata should rotate files to statisfy the disk size cap and raise an alert to let users know they are losing retention. When rotating files, tiers should be selected proportionally.
If
max disk space MB
is set to zero, this check should be disabled and Netdata should use any disk size to satisfy the retention defined.The default settings, should be like above.
Importance
must have
Value proposition
Proposed implementation
As mentioned above.
The text was updated successfully, but these errors were encountered: