limiting the size of error logs and output logs files
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
I have deployed some of my nodejs applications on ec2 with pm2, after a good number of users visiting the application, the application generated 2 huge files for output and error logs, around (12 GB) which maxed out the storage, and the application delivered poor experience for a while.
i want to add a feature to prevent this, which will limit the size of the files (error and output file sizes), and prevent this issue
$ pm2 report
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named in the issue. Start by locating PM2's handling of application output and error log files, then determine how a configurable size limit should be exposed. Done means both log files are prevented from growing beyond the configured limit without exhausting storage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100