-
Notifications
You must be signed in to change notification settings - Fork 400
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
How do I enable log rotation? #107
Comments
Right now, there's no way to set up log rotation from within the agent yourself. You can use Finally, you can try just setting the logging level to be 'info' or 'warn', if you're not already. Higher levels are really only useful for troubleshooting, and will slow down your app in production to boot. If it's logging too much at 'info' or higher, we probably need to make the module less chatty. Thanks for getting in touch! Sorry we don't have a more immediately satisfying resolution! |
Ok, not going to hack into |
That's a great idea! Let us know how that goes and maybe we'll add a note to the documentation! |
Just came across this issue and wondered if the trick to not requiring a server restart if opting for the logrotate option is to simply add the "copytruncate" parameter to the configuration? That's how Ruby application logs can be rotated without requiring a server restart, so I would assume it would work the same with the NewRelic Ruby agent. I'll give it a go and let you know! |
So, my initial tests seem to suggest that does work. Example config: /path/to/logs { |
…/messaging-app/semver-5.7.2 chore(deps): bump semver from 5.7.1 to 5.7.2 in /messaging-app
remove standalone capability and improved test coverage
…/urijs-1.19.8 Bump urijs from 1.19.7 to 1.19.8
add v3 sqs handling
add v3 sqs handling
…/json5-2.2.3 Bump json5 from 2.2.1 to 2.2.3
newrelic_agent.log is growing very fast in our set up. How I can enable log rotation?
The text was updated successfully, but these errors were encountered: