-
Notifications
You must be signed in to change notification settings - Fork 5
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 log retention by expanding log storage #865
Milestone
Comments
gsanchietti
pushed a commit
that referenced
this issue
Oct 21, 2024
Set log rotation size dynamically of 10% tmpfs. Add ns-log-size script to customize the value. #865
Testing image version: 8-23.05.5-ns.1.3.0-20-g57d36c404b3 |
github-actions
bot
added
the
testing
Packages are available from testing repositories
label
Oct 21, 2024
Test case 1
Test case 2
Test case 3
|
Test case 1: config, |
gsanchietti
added
verified
All test cases were verified successfully
and removed
testing
Packages are available from testing repositories
labels
Oct 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current log retention period is approximately one day in a small to medium-sized installation, primarily due to the limited log storage space. Currently, only 50MB is allocated for non-rotated logs, significantly restricting the ability to review logs from past days, which makes it difficult to analyze system behavior or investigate security events.
Proposed solution
Increase the memory allocated for log storage by setting the default size of tmpfs to 10% of the available system memory, with a minimum size of 50MB. This adjustment would utilize the underutilized system memory, as modern installations typically have at least 4 GB of RAM leaving ample room to allocate more space to logs, allowing for longer retention and reducing the risk of losing critical information.
Additionally, users should have the option to configure a custom log storage size to fit their specific needs, while ensuring that the minimum size of 50MB is respected.
Alternative solutions
One alternative would be to maintain the current log size allocation and rely on external solutions for log storage or archiving. However, this would require additional configuration and might not address the immediate need for extended on-device log retention.
The text was updated successfully, but these errors were encountered: