We identified and fixed a memory leak in a Nest.js application running on Kubernetes, which was caused by open handles not being properly closed during proxy requests to Grafana. Using Prometheus and Grafana for monitoring, along with custom modifications to the wtf-node dependency, we pinpointed the issue and adjusted the

8m read time From medium.com
Post cover image
Table of contents
Memory Leak Profiling and Pinpointing for Node.jsDual Role of Nest.js Server in Authorizing Access to Internal Grafana DashboardsA Wild Memory leak appearsPinpointing and isolating the memory leak cause

Sort: