feat: log memory usage and shutdown#207
Conversation
Added memory usage logging and graceful shutdown handling.
|
Warning Review limit reached
Next review available in: 5 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Moved the formatMemoryUsage function into run.ts to consolidate memory logging functionality.
| // How often to log the process memory usage. This leaves a memory trail in the | ||
| // logs so a restart can be correlated with memory pressure (e.g. OOM) even when | ||
| // only the application logs are available. | ||
| const MEMORY_LOG_FREQUENCY_SECS = 60; |
There was a problem hiding this comment.
nitpick: I think it's actually is a period or interval then frequency
SIGTERMhandler (mirroring the SIGINT one). Next time it will log a clean shutdown on any k8s-initiated restart, so silence will then unambiguously mean SIGKILL/OOM. Right now the two cases are indistinguishable.