Skip to content
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

Improve log retention #323

Open
knolleary opened this issue Mar 13, 2025 · 0 comments
Open

Improve log retention #323

knolleary opened this issue Mar 13, 2025 · 0 comments
Labels
needs-triage Needs looking at to decide what to do size:M - 3 Sizing estimation point

Comments

@knolleary
Copy link
Member

We currently retain logs in a fixed sized buffer within the launcher. This means:

  1. the duration of retained logs depends on how noisy Node-RED is
  2. the logs are only available if the launcher is running - and any history is lost if the launcher itself is restarted (eg suspend/resume).

This high level issue is to identify a plan for improving the log retention. We can make use of the fact we now have persistent file storage available to the instances.

Proposal: Write logs to the persistent file system on the instance.

  • The file should be rotated daily
  • Only retain the last N days of logs (14/30 days... could be configurable in the future)
  • Provide API in the launcher to retrieve logs for a given time period - which can be restored from the log files (this will be a separate task needed by Time-based browsing of Instance logs flowfuse#5301 which I'll raise independently of this proposal.)
  • Log files will show up under the 'assets' view of the instance - a feature not a bug, so should be under a well-defined directory
@knolleary knolleary added size:M - 3 Sizing estimation point needs-triage Needs looking at to decide what to do labels Mar 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Needs looking at to decide what to do size:M - 3 Sizing estimation point
Projects
Status: No status
Development

No branches or pull requests

1 participant