Collecting application process data
Excerpt from the talk “My Node.js process is on fire”
“At 10am on Black Friday, your phone rings: the new JS application you deployed came under too much load, and the site has gone down! Your employer is losing sales opportunities... your employer is losing money! But you don’t lose your cool. You log in to your cloud provider and tweak your autoscaling settings. Now the deployment can handle the load spike but with four times the number of servers, which is four times the cost. The next day, you try to analyze what happened and begin to optimize your application to prepare for future load spikes.”
The full talk was delivered by Matteo Collina at JSConf Asia 2018 and is available at https://www.youtube.com/watch?v=G9Vkpe55Gu8.
The main reason we want to collect metrics of our running Node.js process is to be able to diagnose and debug problems hours, days, or even weeks after they happened. The flow of...
